Get provisioning working on Xenial about packer-boxes HOT 14 CLOSED

So the networking fix looks to be a combination of:

1. Add GRUB_CMDLINE_LINUX="biosdevname=0 net.ifnames=0" to /etc/default/grub

2. Run sudo grub-mkconfig -o /boot/grub/grub.cfg and reboot

3. Edit /etc/network/interfaces and add in (replacing the existing default adapter¹):

     auto eth0
     iface eth1 inet dhcp
     auto eth1
     iface eth1 inet manual
   

4. Restart

5. vagrant up should complete successfully.

¹ The definition of a semi-complete eth1 adapter should not be required, but is currently because Ubuntu 16.04 (unlike previous releases) balks when there's an error message output during it's run of ifdown eth1. There's a commit that fixes this in vagrant master, but it's not in a stable release yet: hashicorp/vagrant@0505771

Also, the overarching problem is that Vagrant currently doesn't handle predictable network interfaces, which are now used by most of the major distros; there's a PR (hashicorp/vagrant#7241) which aims to add in support, but it could be some time before that gets in.

I'm testing adding in all the above to cleanup.sh for now.

from packer-boxes.

@geerlingguy Had followed your steps in #1 (comment), but it has a mistake. The edit to /etc/network/interfaces should be:

auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet manual

I figured it out from 6ff7948. Thanks for posting this fix.

from packer-boxes.

For future reference, having done the first two steps mentioned above:

1. Add GRUB_CMDLINE_LINUX="biosdevname=0 net.ifnames=0" to /etc/default/grub
2. Run sudo grub-mkconfig -o /boot/grub/grub.cfg and reboot

The first time I booted the VM, it hung for about 2 minutes on a message about "Started Journal Service". Then it was all fine and it fixed the problem. Future boots were normal.

Thanks for the fix.

from packer-boxes.

Upstream issue to get Ansible's official PPA working on Xenial: ansible/ansible#15524

For now, I think I can install Ansible differently, and we should be okay.

from packer-boxes.

Maybe:

# Install pip.
apt -y install python-setuptools python-dev
easy_install pip

# Install Ansible.
pip install ansible

Otherwise I think Xenial has pip via python-pip as well.

from packer-boxes.

I think I've run into: hashicorp/vagrant#6871

from packer-boxes.

Adding net.ifnames=0 biosdevname=0 to the boot command didn't seem to help; if inside the built machine, ifconfig doesn't list an eth0 interface :/

If I remove those two lines, I get an enp0s3 interface, which allows Packer to complete the build by connecting over SSH.

Tried from http://unix.stackexchange.com/a/88619/16194, but might need to do some other hackish thing, like was suggested in the original issue in bento.

from packer-boxes.

Trying ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules to turn off the naming scheme for now. Will add to cleanup.sh if it works.

from packer-boxes.

That didn't work. And neither did echo 'GRUB_CMDLINE_LINUX="net.ifnames=0"' >>/etc/default/grub (both tested after a reboot).

from packer-boxes.

So some other places to read:

• PR: Handle new 'predictable' network interface naming style
• Predictable Network Interface Names
• Ubuntu bug for livecd
• Ubuntu 15.10 error when enabling network interfaces

Trying this now:

echo 'GRUB_CMDLINE_LINUX="biosdevname=0 net.ifnames=0"' >> /etc/default/grub
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo shutdown now

from packer-boxes.

Using the above gives the same result as my testing earlier—no eth[x] interfaces are created (ifconfig just lists the lo interface).

from packer-boxes.

Er, actually there is an eth0 and eth1. Needed to use sudo ifconfig -a.

from packer-boxes.

I "fixed"/worked around this by using the networking.d folder:

echo "auto eth1" >> /etc/network/interfaces.d/eth1
echo "iface eth1 inet manual" >> /etc/network/interfaces.d/eth1

echo "auto eth2" >> /etc/network/interfaces.d/eth2
echo "iface eth2 inet manual" >> /etc/network/interfaces.d/eth2

echo "auto eth3" >> /etc/network/interfaces.d/eth3
echo "iface eth3 inet manual" >> /etc/network/interfaces.d/eth3

from packer-boxes.

@dsbaars your fix does not work for me

from packer-boxes.