Vagrant box ubuntu/wily64 cannnot connect network in default

Bug #1522287 reported by aafflus
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Undecided
Unassigned

Bug Description

I'm using Ubuntu 15.10 on vagrant with official image ubuntu/wily64.
https://vagrantcloud.com/ubuntu/boxes/wily64

But after I updated vagrant box, the VM is not connected to network.

I googled and found this gist.
https://gist.github.com/brbsix/b70413dec907906ef659

In version 20151029.0.0, "net.ifnames=0" is found in grub.cfg.
but in version 20151127.0.0, "net.ifnames=0" is not found and enp0s3 interface is not configured.

Is this a bug or something wrong?

aafflus (acbuixo)
affects: vagrant (Ubuntu) → ubuntu
Revision history for this message
aafflus (acbuixo) wrote :

version 20151203.0.0 is still same as 20151127.0.0

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Mike Miller (mtmiller) wrote :

Same problem here, thanks for reporting and pointing to the writeup about how to work around this inconsistency. I'm not sure this is the right place to report, but you certainly helped me get past this problem.

Revision history for this message
aafflus (acbuixo) wrote :

version 20151219.0.0 is same too.
Does anyone know where is better place to report this issue?

Revision history for this message
Six (brbsix) wrote :

Looks like someone submitted the bug to Vagrant's GitHub Issues page here: https://github.com/mitchellh/vagrant/issues/6683

It's good to see people talking about it. I noticed the issue 3+ months ago but I wasn't familiar enough to determine if the issue was with Vagrant itself or just the Wily box.

Revision history for this message
aafflus (acbuixo) wrote :

In version 20160105, "net.ifnames=0" is found in grub.cfg.
So eth0 is configured.

Mike Miller (mtmiller)
Changed in ubuntu:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.