vagrant box fails with private network interface

Bug #1538547 reported by Steven Van Acker
70
This bug affects 12 people
Affects Status Importance Assigned to Milestone
livecd-rootfs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hello,

I am attempting to use the Xenial vagrant box announced here:
https://lists.ubuntu.com/archives/ubuntu-devel/2016-January/039070.html

The default setup, as described in the announcement, works fine.
However, it fails if I add a private network interface in Vagrantfile:

    config.vm.network "private_network", ip: "192.168.50.100"

Output of "vagrant up":

deepstar@perdix:/tmp/example$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: example_default_1453900316714_21930
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2201 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2201
    default: SSH username: ubuntu
    default: SSH auth method: password
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Authentication failure. Retrying...
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifdown eth1 2> /dev/null

Stdout from the command:

Stderr from the command:

sudo: unable to resolve host ubuntu-xenial
mesg: ttyname failed: Inappropriate ioctl for device

The version of the vagrant box is 20160126.1
I am using Vagrant 1.8.1 on OSX 10.11.2 if that matters.
Other vagrant boxes I've tested work fine with this extra network interface in the Vagrantfile.

kr,
-- Steven

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

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

Changed in livecd-rootfs (Ubuntu):
status: New → Confirmed
Changed in livecd-rootfs (Ubuntu):
assignee: nobody → Ben Howard (utlemming)
Revision history for this message
kiorky (kiorky) wrote :

I confirm this bug

Revision history for this message
domnulnopcea (domnulnopcea) wrote :

the bug is still present in 20160409 image

Changed in livecd-rootfs (Ubuntu):
assignee: Ben Howard (utlemming) → nobody
Revision history for this message
MartinL (landa-martin) wrote :

I can confirm that this bug is still present (tested 20160517). Is there any hope that it will be fixed? Thanks! Martin

tags: added: vagrant
Revision history for this message
Ville Korhonen (ypcs) wrote :

See upstream (vagrant) bug https://github.com/mitchellh/vagrant/issues/6871 and pull request at https://github.com/mitchellh/vagrant/pull/7241 , looks like that systemd & predictable ifnames is causing this.

Revision history for this message
MartinL (landa-martin) wrote :

Updated: the vagrant fixes have been merged to master, see https://github.com/mitchellh/vagrant/issues/7288

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.