Bug 1381537 - Ubuntu 16.04 with a private network fails due to upstream fixed bug
Summary: Ubuntu 16.04 with a private network fails due to upstream fixed bug
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: vagrant
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Valena
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-04 12:03 UTC by Mike Goodwin
Modified: 2017-07-06 16:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-06 16:51:19 UTC
Type: Bug


Attachments (Terms of Use)

Description Mike Goodwin 2016-10-04 12:03:04 UTC
Description of problem:

https://github.com/mitchellh/vagrant/issues/7155

==> ubuntu16: Setting hostname...
==> ubuntu16: 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:

mesg: ttyname failed: Inappropriate ioctl for device


Version-Release number of selected component (if applicable):

1.8.1

How reproducible:

Always

Steps to Reproduce:

Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/xenial-cloud"
  config.vm.box_url = "http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box"
  config.vm.network "private_network", ip: "192.168.33.10"
end


Additional info:

Please consider patching this package or updating it to match current rawhide (1.8.5)

The issue: https://github.com/mitchellh/vagrant/issues/7155
The PR: https://github.com/mitchellh/vagrant/issues/7159

Comment 1 Pavel Valena 2016-10-05 15:37:14 UTC
Hi Mike,

I have reproduced your issue on Fedora 23 and I have created scratch-builds which include the patch[1] for this issue:

Scratch-builds
  Fedora 23: http://koji.fedoraproject.org/koji/taskinfo?taskID=15953505
  Fedora 24: http://koji.fedoraproject.org/koji/taskinfo?taskID=15953723


However, the patch did not fix the issue for me on Fedora 23.

Does it work for you on Fedora 24?


Pavel


[1] https://github.com/mitchellh/vagrant/commit/0505771481222b4893daa5454ff6c9c16f471fa4


Note You need to log in before you can comment on or make changes to this bug.