VMware: Ubuntu 15.10 networking issues
rmoriz opened this issue · comments
Now with the released images on Atlas, I've the issues already mentioned in the #545.
- Vagrant 1.8.1
- test-kitchen 1.5.0
- VMware Fusion 8.1.0
Problem => No network
Reason => #545 (comment)
Possible Fix => #545 (comment)
❗ If you're affected, add a comment which VMWare product and version you're using! Thanks! ❗
kitchen setup 1510
-----> Starting Kitchen (v1.5.0)
-----> Creating <default-ubuntu-1510>...
Bringing machine 'default' up with 'vmware_fusion' provider...
==> default: Box 'opscode-ubuntu-15.10' could not be found. Attempting to find and install...
default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation
default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'opscode-ubuntu-15.10' (v0) for provider: vmware_desktop, vmware_fusion, vmware_workstation
default: Downloading: https://opscode-vm-bento.s3.amazonaws.com/vagrant/vmware/opscode_ubuntu-15.10_chef-provisionerless.box
==> default: Successfully added box 'opscode-ubuntu-15.10' (v0) for 'vmware_desktop'!
==> default: Cloning VMware VM: 'opscode-ubuntu-15.10'. This can take some time...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
==> default: Starting the VMware VM...
==> default: Waiting for machine to boot. This may take a few minutes...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #create action: [Expected process to exit with [0], but received '1'
---- Begin output of vagrant up --no-provision --provider vmware_fusion ----
STDOUT: Bringing machine 'default' up with 'vmware_fusion' provider...
==> default: Box 'opscode-ubuntu-15.10' could not be found. Attempting to find and install...
default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation
default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'opscode-ubuntu-15.10' (v0) for provider: vmware_desktop, vmware_fusion, vmware_workstation
default: Downloading: https://opscode-vm-bento.s3.amazonaws.com/vagrant/vmware/opscode_ubuntu-15.10_chef-provisionerless.box
==> default: Successfully added box 'opscode-ubuntu-15.10' (v0) for 'vmware_desktop'!
==> default: Cloning VMware VM: 'opscode-ubuntu-15.10'. This can take some time...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
==> default: Starting the VMware VM...
==> default: Waiting for machine to boot. This may take a few minutes...
STDERR: Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
---- End output of vagrant up --no-provision --provider vmware_fusion ----
Ran vagrant up --no-provision --provider vmware_fusion returned 1]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration
kitchen setup 1510 73,17s user 135,29s system 35% cpu 9:40,88 totalI guess someone needs to make a decision regarding #545 (comment) or come up with another solution?
Someone (myself included) just needs to make a PR and then run it through the pipeline/tests.
any updates on this? ETA?
Working on builds today.
Builds released and the networking issues here are resolved.