[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2021-01-09 Thread Helmo
A workaround is to download and install the deb file from https://www.vagrantup.com/downloads Tested with 2.2.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: Vagrant bionic 64 with

[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2020-09-01 Thread Robert C Jennings
A backport of https://github.com/hashicorp/vagrant/pull/9338 could resolve this and allow bionic to launch Focal and later vagrant boxes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title:

[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2019-05-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vagrant (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title:

[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2018-05-22 Thread Carsten Decker
Yes, right - thank you! This is related to: https://wiki.ubuntu.com/MigratingToNetplan#Rationale https://askubuntu.com/questions/1005390/why-did-ubuntu-change-the- network-configuration https://github.com/hashicorp/vagrant/issues/9134 https://github.com/hashicorp/vagrant/issues/9428 As I can

[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2018-05-21 Thread Phillip Susi
I think those commands and files are no longer installed by default and it looks like vagrant is still trying ot use them. ** Package changed: ubiquity (Ubuntu) => vagrant (Ubuntu) ** Changed in: vagrant (Ubuntu) Status: Incomplete => New -- You received this bug notification because

[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2018-05-20 Thread Carsten Decker
I've just checked v20180518.0.0 with the same result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: Vagrant bionic 64 with virtualbox image doesn't start network correctly To

[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2018-05-05 Thread Carsten Decker
I have the same issue with 'ubuntu/bionic64' (v20180426.2.0) on MacOS 10.11 / Vagrant 1.9.8 / VirtualBox 5.1.30 --- The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! /sbin/ifdown 'enp0s8' || true /sbin/ip addr flush dev 'enp0s8'

[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2018-04-19 Thread Phillip Susi
Are you still seeing this today? ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: Vagrant bionic 64 with

[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly

2018-01-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: