-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Ubuntu 15.10 error when enabling network interfaces #6871
Comments
Same here with
|
Anyone had a chance to look into this? |
Take a look at this http://askubuntu.com/questions/671228/lost-network-device-on-upgrade-to-15-10-on-test-vm
In moving forward in fixing this issue. Would need more looking into. |
@RudyJessop this is a fresh vm so makes perfect sense
|
@schmunk42, I think you are experiencing a related but different issue. The |
@gMagicScott Yes, I think you're right. I just get the error |
@gMagicScott that makes sense thanks, let's hope the pr get's merged sometime |
New Relic is a solid Software Analytics & Monitoring service (Not yet apart of Corebox) To be added with v0.0.7 when this issue is resolved hashicorp/vagrant#6871
I'm seeing the same thing here for debian sid, which is using a 4.3 kernel now, and vagrant 1.8.1. Debug log in the gist https://gist.github.com/dch/0cc4735b81cf84cf3f73 along with this simply ugly hack to get things working: --- ./plugins/guests/debian/cap/configure_networks.rb.orig 2016-02-19 14:04:24.000000000 +0100
+++ ./plugins/guests/debian/cap/configure_networks.rb 2016-02-19 14:35:15.000000000 +0100
@@ -42,8 +42,8 @@
# each specifically, we avoid reconfiguring eth0 (the NAT interface) so
# SSH never dies.
interfaces.each do |interface|
- comm.sudo("/sbin/ifdown eth#{interface} 2> /dev/null")
- comm.sudo("/sbin/ip addr flush dev eth#{interface} 2> /dev/null")
+ comm.sudo("/sbin/ifdown eth#{interface} 2> /dev/null || /bin/true")
+ comm.sudo("/sbin/ip addr flush dev eth#{interface} 2> /dev/null || /bin/true")
end
comm.sudo('cat /tmp/vagrant-network-interfaces.pre /tmp/vagrant-network-entry /tmp/vagrant-network-interfaces.post > /etc/network/interfaces')
A real fix for this is sorely needed, I'm not sure if my hack above is appropriate for a PR or not. |
I'm having the same problem with Ubuntu Xenial. To work around it, I ended up forcing
|
Just for the record, i've the same problem (tried with http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box), which should be working out of the box. If i don't specify any network, it runs fine. As soon as i add an extra network, it fails with the same error. In this case, eth1 is not found. Just as an additional note, i tryed with the Atlas debian/jessie64 box, and it works fine (but i also note that the box is creating the network devices with eth0, eth1 and lo - which match the old name convention). Cheers, |
Indeed jessie is fine AFAICS but current testing is problematic. I can confirm the issue on a box based on testing (created using https://github.com/tiwilliam/vagrant-debian). |
The update of ifupdown (0.8.7) is causing this. The behaviour of ifupdown is changed if the interface doesn't exists. With 0.8.7 it returns an error. |
@sethvargo The Fix in #7159 is not complete. I still get errors after applying that patch:
And if I add the same
Confirmed that using The relevant Vagrantfile bits from my host:
|
I am having the same issues as @denisbr. This patch isn't working for me. Here is the link to my Vagrantfile. vagrant up xenial64 |
@sethvargo looks like this is still broken, can we reopen this issue? |
This definitely needs to be reopened - it's a showstopper for anyone needing more than one network interface on Xenial. It looks as though in the systemd world, the new interface naming scheme is The Way Of The Future (for better or worse). I've put together PR #7241 to adapt the interface configuration logic to handle this in both the old world and the new. This is a slightly different approach to @gMagicScott's in that it doesn't introduce a distinction between Debian and Ubuntu, and assumes that Debian will go the same way. |
Having the same problem here with ubuntu/xenial64 build running on Arch Linux and vagrant 1.8.1 |
Note that I think I've now found about 20 different forum posts, GitHub issues, etc. pointing either at this issue (closed) or at the PR mentioned earlier (#7241). AFAICT, for many (most?) uses, Vagrant configs won't work with 15.10 or 16.04 boxes. I only deal with LTS releases for my needs, so this is the first time I've run into this issue (I'm trying to build my 16.04 minimal base box with Packer, and everything works except for The network interface I get by default is |
just to add my 2p worth, none of the workarounds work for me (true's everywhere, editing /etc/default/grub and so on) on debian sid 64-bit host, ubuntu/xenial64 guest, virtualbox 5.0.19 test build is needed to even get xenial to boot, running vagrant 1.8.1 seems the only way to get it working is to make your own packer image with the grub change. is there no working PR yet? #7241 is incomplete it seems. also any idea why this wasn't picked up with e.g. centos7 guests, as they use the same naming convention....? or is there something else afoot? |
@sej7278 - Here's my fix: geerlingguy/packer-boxes#1 — of course building my own image with Packer here... no simple way I can see this being fixed on a base box that's already built without the grub/networking changes in place until Vagrant supports predictable network interface names. |
still not fixed ubuntu/xenial64 (20160610.0.0) |
ubuntu 16.04 |
-1 to my original +1 to @silesky's issue. Upgraded to 1.8.4 and ran without any issue. |
did not work in vagrant 1.8.1 but works in 1.8.4 |
@chrisbaldauf |
Just encountered this similar issue for guest
Note that the host is running Here's the tail of logs after running
|
I'm having the same error with
|
I'm having the same error with
|
I'm having the same error with ubuntu/xenial64 and Vagrant 1.9.0. ==> default: mesg: ttyname failed: Inappropriate ioctl for device |
Same for me with Vagrant 1.9.0 provisioning Ubuntu Zesty Zapus from: ==> default: Running provisioner: shell... |
SOLVED: Upgrading to Vagrant 1.9.1 (from Hashicorp's site; aptitude installs 1.8.1 by default) fixed my issue. Original Text
|
I'm seeing the following error when I try to run
I am using Vagrant 1.9.1 (downloaded from vagrantup.com) on an Ubuntu 16.04 host. |
Ah nevermind - I see that it is a separate issue: #5615 |
@jsgoller1 solution (upgrade to vagrant 1.9.1 from official site) solved my issue Original problem:
|
Same issue with
|
@khromov Are you trying to read something from stdin? Because that is not possible. |
after update to 1.9.1 still getting issue with ==> default: Running provisioner: shell... |
Updating from 1.8.3 to 1.9.3 resolved the issue for me. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Previously using a custom 15.04 all worked fine
new custom 15.10 box, virtually no changes to box just an updated ubuntu version
Similar to #6577 but I'm already on vagrant 1.8
The text was updated successfully, but these errors were encountered: