Skip to content

2nd NIC not activated until nodes rebooted #50

Description

@robinbowes

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions