Updating old versions of ubuntu Chat with irish mature sex
BTW; ubuntu16.04 is the next lts, which is coming soon ;) and cyring on users to adapt a bit their vagrantfile is a bit chilly where there is a bug on the first place. being so rude on the first comment, after a big misread of the bug can just make your users runaway ... My intent was not to be rude, so I apologize if it came off that way.
Please understand that your Vagrantfile is very complex with many variables, so I was trying to help you narrow down the cause of the issue.
In ifupdown (0.8.7) the now return an error instead to the previous behaviour.
From the changelog ( As debian/cap/configure_networks.rb: L44 always tries to ifdown an interface, even if it is not defined for the system, because first start and the fact that all interfaces except eth0 are removed from /etc/network/interfaces by debian/cap/configure_networks.rb: L16-17 this now throws an error as the command returns non-zero.
The Vagranfile you supplied is doing a lot of things including monkey-patching the ruby, defining helpers, and performing conditional execution that makes it very difficult to reason about the actual Vagrantfile that is being used and the parameters.
Are you able to reproduce this with a vanilla Vagrantfile? Could you please reduce to a vanilla Vagrantfile and see if the issue reproduces? If it doesn't, it means there is an issue in one of the items in the list above. Vagrant.configure(2) do |config| box = "ubuntu/xenial-cloud" box_url = " network "private_network", ip: "192.1" end The problem seems to be a upgrade of ifupdown package.
This behavior changed in Ubuntu 16.04 to return an error. Fixes GH-7155Vagrant.configure(2) do |config| box = "xenial64" box_url = " network "private_network", ip: "192.1", auto_config: false provision 'shell', inline: "ifconfig eth1 192.1" end [ 1.427584] e1000 00.0 eth0: (PCI:33MHz:32-bit) :4a:2c:32 [ 1.427588] e1000 00.0 eth0: Intel(R) PRO/1000 Network Connection [ 1.802749] e1000 00.0 eth1: (PCI:33MHz:32-bit) :60:5a:83 [ 1.802754] e1000 00.0 eth1: Intel(R) PRO/1000 Network Connection [ 1.803680] e1000 00.0 enp0s8: renamed from eth1 [ 1.805088] e1000 00.0 enp0s3: renamed from eth0 @ecirtap Thats another new feature with ubunut.
The chaning the devise names to pci port and slot to better find a defunct network port in real life.
@valkum was able to provide a much smaller reproduction case, which we can convert into a test case and fix the bug.
Ubuntu versions prior to 16.04 always returned a successful exit status, even if one tried to down an interface that does not exist.