Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2nd NIC not activated until nodes rebooted #50

Open
robinbowes opened this issue Aug 3, 2016 · 0 comments
Open

2nd NIC not activated until nodes rebooted #50

robinbowes opened this issue Aug 3, 2016 · 0 comments

Comments

@robinbowes
Copy link

robinbowes commented Aug 3, 2016

I'm using oscar with VirtualBox on OSX:

# robin at mbp in ~
  vagrant --version
vaVagrant 1.8.5
# robin at mbp in ~
  vagrant plugin list
oscar (0.5.1)
vagrant-hostmanager (1.8.5)
vagrant-librarian-puppet (0.9.2)
vagrant-puppet-install (4.1.0)
vagrant-share (1.1.5, system)
vagrant-vbguest (0.12.0)

I've attached the config I'm using:
oscar-config.tar.gz

The problem I'm seeing is that the auto-selected IPs are being assigned to the 2nd NIC on the boxes (eth1) but not brought up. This causes provisioning to fail as the guests are not able to connect to the master.

As a workaround, this works:

vagrant up --no-provision
vagrant reload

When the boxes are reloaded, the 2nd network is started and provisioning (which runs on reload because it hasn't run already) completes successfully.

Any idea where the problem might lie?

R.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant