Skip to content
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.

Unable to 'vagrant up' the envrionment #1

Closed
ReEll opened this issue Apr 11, 2014 · 3 comments
Closed

Unable to 'vagrant up' the envrionment #1

ReEll opened this issue Apr 11, 2014 · 3 comments

Comments

@ReEll
Copy link

ReEll commented Apr 11, 2014

I have tried with
Win 7
Virtualbox 4.3.10
vagrant_1.5.2
vagrant_1.4.3

Seems to be an issue with the answers file that gets passed during pe_bootstrap

The log from the attempted vagrant up

N:\VM\pe-razor-vagrant-stack-master>vagrant up
Bringing machine 'puppet-master' up with 'virtualbox' provider...
Bringing machine 'razor-server' up with 'virtualbox' provider...
Bringing machine 'dhcp-server' up with 'virtualbox' provider...
[puppet-master] Box 'centos-64-x64-vbox4210-nocm' was not found. Fetching box fr
om specified URL for
the provider 'virtualbox'. Note that if the URL does not have
a box for this provider, you should interrupt Vagrant now and add
the box yourself. Otherwise Vagrant will attempt to download the
full box prior to discovering this error.
Downloading box from URL: http://puppet-vagrant-boxes.puppetlabs.com/centos-64-x
64-vbox4210-nocm.box
Extracting box...ate: 6490k/s, Estimated time remaining: --:--:--)
Successfully added box 'centos-64-x64-vbox4210-nocm' with provider 'virtualbox'!

[puppet-master] Importing base box 'centos-64-x64-vbox4210-nocm'...
[puppet-master] Matching MAC address for NAT networking...
[puppet-master] Setting the name of the VM...
[puppet-master] Clearing any previously set forwarded ports...
[puppet-master] Clearing any previously set network interfaces...
[puppet-master] Preparing network interfaces based on configuration...
[puppet-master] Forwarding ports...
[puppet-master] -- 22 => 2222 (adapter 1)
[puppet-master] Running 'pre-boot' VM customizations...
[puppet-master] Booting VM...
[puppet-master] Waiting for machine to boot. This may take a few minutes...
DL is deprecated, please use Fiddle
[puppet-master] Machine booted and ready!
[puppet-master] The guest additions on this VM do not match the installed versio
n of
VirtualBox! In most cases this is fine, but in rare cases it can
prevent things such as shared folders from working properly. If you see
shared folder errors, please make sure the guest additions within the
virtual machine match the version of VirtualBox you have installed on
your host and reload your VM.

Guest Additions Version: 4.2.10
VirtualBox Version: 4.3
[puppet-master] Configuring and enabling network interfaces...
[puppet-master] Mounting shared folders...
[puppet-master] -- /vagrant
[puppet-master] -- /tmp/puppet
[puppet-master] Running provisioner: shell...
[puppet-master] Running: inline script
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
[puppet-master] Running provisioner: shell...
[puppet-master] Running: inline script
[puppet-master] Running provisioner: hosts...
[puppet-master] Running provisioner: pe_bootstrap...

[puppet-master] ================================================================

Puppet Enterprise v3.2.0 installer

Puppet Enterprise documentation can be found at http://docs.puppetlabs.com/pe/3.
2/
[puppet-master]

[puppet-master] ----------------------------------------------------------------

STEP 1: READ ANSWERS FROM FILE

Reading answers from file: /vagrant/.pe_build/answers/puppet-master.txt

[puppet-master]

STEP 2: SELECT AND CONFIGURE ROLES
[puppet-master] This installer lets you select and install the various roles
required in a Puppet Enterprise deployment: puppet master,
console, database, cloud provisioner, and puppet agent.
[puppet-master]

NOTE: when specifying hostnames during installation, use the fully-qualified dom
ain name (foo.example.com) rather than a shortened name (foo).
[puppet-master]
-> puppet master

The puppet master serves configurations to a group of puppet
agent nodes. This role also provides MCollective's message queue
and client interface. It should be installed on a robust,
dedicated server.
[puppet-master] ?? Install puppet master? [y/N]
[puppet-master] y
[puppet-master] !! ERROR: Answer must be either "y", "n" or for "n"
[puppet-master]
[puppet-master] ?? Install puppet master? [y/N]
[puppet-master]
[puppet-master] /vagrant/.pe_build/puppet-enterprise-3.2.0-el-6-x86_64/utilities
: line 540: t_ask__answered: parameter null or not set
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/vagrant/.pe_build/puppet-enterprise-3.2.0-el-6-x86_64/puppet-enterprise-install
er -a /vagrant/.pe_build/answers/puppet-master.txt

Stdout from the command:

Puppet Enterprise v3.2.0 installer

Puppet Enterprise documentation can be found at http://docs.puppetlabs.com/pe/3.
2/


STEP 1: READ ANSWERS FROM FILE

Reading answers from file: /vagrant/.pe_build/answers/puppet-master.txt


STEP 2: SELECT AND CONFIGURE ROLES

This installer lets you select and install the various roles
required in a Puppet Enterprise deployment: puppet master,
console, database, cloud provisioner, and puppet agent.

NOTE: when specifying hostnames during installation, use the fully-qualified dom
ain name (foo.example.com) rather than a shortened name (foo).

-> puppet master

The puppet master serves configurations to a group of puppet
agent nodes. This role also provides MCollective's message queue
and client interface. It should be installed on a robust,
dedicated server.

?? Install puppet master? [y/N] y
?? Install puppet master? [y/N]

Stderr from the command:

!! ERROR: Answer must be either "y", "n" or for "n"
/vagrant/.pe_build/puppet-enterprise-3.2.0-el-6-x86_64/utilities: line 540: t_as
k__answered: parameter null or not set

==================END LOGFILE====================

Please contact me with anything I can do to help resolve this/test the new version.

@ReEll
Copy link
Author

ReEll commented Apr 11, 2014

Tried again with a clean copy of the git repo and same result.

STEP 2: SELECT AND CONFIGURE ROLES

This installer lets you select and install the various roles
required in a Puppet Enterprise deployment: puppet master,
console, database, cloud provisioner, and puppet agent.

NOTE: when specifying hostnames during installation, use the fully-qualified dom
ain name (foo.example.com) rather than a shortened name (foo).

-> puppet master

The puppet master serves configurations to a group of puppet
agent nodes. This role also provides MCollective's message queue
and client interface. It should be installed on a robust,
dedicated server.

?? Install puppet master? [y/N] y
?? Install puppet master? [y/N]

Stderr from the command:

!! ERROR: Answer must be either "y", "n" or for "n"
/vagrant/.pe_build/puppet-enterprise-3.2.0-el-6-x86_64/utilities: line 540: t_as
k__answered: parameter null or not set

@npwalker
Copy link
Contributor

Hi @ReEll,

I've never tried running this from a vagrant setup on a windows machine. It appears as though this is an issue in the oscar plugin I'm using to bootstrap PE.

oscar-stack/oscar#17

All I can recommend is waiting for a fix over on that issue.

-Nick

@ReEll
Copy link
Author

ReEll commented Apr 18, 2014

Thank you for taking the time to have a look. Another work around is to let the installer fail on the initial vagrant up and then modify the answers files in a txt editor to use unix EOL.

at that point vagrant ssh to each machine and doing the manual install with answers.

npwalker pushed a commit that referenced this issue Jun 7, 2018
In Ruby, `super` implicitly passes a copy of the arguments a method received.
When raising a `DebugKitBadVersion` error, the `initialize` method has a
different signature than `super`, so we must explicitly pass the right
arguments.

Fixes GH-1.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants