** Changed in: cloud-images
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
To ma
Yay! 5 months after 16.04 release it started to work in Vagrant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
To
Using v20160921.0.0 and it works :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
To manage notifications about th
The fix is released in livecd-rootfs 2.408.4 which is in xenial-updates.
The only thing left is to get that package updated on the cloud image
build servers. I am trying to find someone on IRC who can help with
that.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Official Ubuntu Vagrant Box image:
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-
amd64-vagrant.box
Still not working.
There is any update on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
This image was made 3 hours ago while bug fix was released only 1 hour
ago. Is there a way to trigger image build again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (
So I just tested again with the released image on Vagrant Atlas
(https://atlas.hashicorp.com/ubuntu/boxes/xenial64/versions/20160914.0.0)
and the image from Ubuntu Cloud Images (https://cloud-
images.ubuntu.com/xenial/current/xenial-server-cloudimg-
amd64-vagrant.box) and the bug still remains. So
This bug was fixed in the package livecd-rootfs - 2.408.4
---
livecd-rootfs (2.408.4) xenial; urgency=medium
* live-build/ubuntu-cpc/hooks/042-vagrant.binary: fix unmount handling
so that the teardown is done properly /before/ we try to make an
image from our filesystem, sin
I just tested the image provided by the link
(https://i284108973.restricted.launchpadlibrarian.net/284108973/livecd
.ubuntu-cpc.vagrant.box?token=K7Pp7BgzNCZ0b0BbvC3q3Vgc3LkJpwW0) and can
confirm that the described problem seems to be resolved. Thank you.
--
You received this bug notification bec
> https://i284108973.restricted.launchpadlibrarian.net/284108973/livecd.ubuntu-cpc.vagrant.box?token=K7Pp7BgzNCZ0b0BbvC3q3Vgc3LkJpwW0
Tested and it's ok
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
If anyone else could test this build by Dan Watkins and check for
regressions that would be great.
https://i284108973.restricted.launchpadlibrarian.net/284108973/livecd
.ubuntu-cpc.vagrant.box?token=K7Pp7BgzNCZ0b0BbvC3q3Vgc3LkJpwW0
--
You received this bug notification because you are a member o
I also tested a build done by Dan Watkins on the ubuntu build
infrastructure and it looks good as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.con
I tested this in the same manner as the previous SRU (LP: #1605795), and
additionally verifying that /etc/resolv.conf is a symlink to
../run/resolvconf/resolv.conf. It all looks good to me. Tested version
2.408.4 from xenial-proposed.
** Tags removed: verification-needed
** Tags added: verificat
Hello Marius, or anyone else affected,
Accepted livecd-rootfs into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.408.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
It also does not seem to work with the last few box versions. When will
the box be updated?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (e
I still have the exact same issue with the latest 64bit box version
(20160909.0.0) and vagrant version 1.8.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.
Thank you Steve Langasek!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
To manage notifications about this bug go
This bug was fixed in the package livecd-rootfs - 2.430
---
livecd-rootfs (2.430) yakkety; urgency=medium
[ Michael Vogt ]
* live-build/ubuntu-core/hooks/01-setup_user.chroot:
- do not create "ubuntu" user for ubuntu-core anymore, the
console-conf package will create thi
** Description changed:
+ [SRU Justification]
+ This is a regression introduced in the previous SRU of livecd-rootfs.
+
+ [Test case]
1. vagrant init ubuntu/xenial64
2. vagrant up
3. vagrant ssh
4. ping google.com
Expected result:
- ping succeeds
Actual result:
- name resolu
** Branch linked: lp:~ubuntu-core-dev/livecd-rootfs/xenial-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
** Branch linked: lp:livecd-rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
To manage notifications about thi
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
To manage notifications about this
Hi,
in the meanwhile you can use this Workaround in Vagrantfile
(multimachine example):
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
servers.each do |machine|
config.vm.define machine["hostname"] do |node|
node.vm.provision "shell", inline: "ln -nsf
../run
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (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/1621393
Title
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621393
Title:
xenial64 image (20160907.1.0) has a broken (empty) /e
26 matches
Mail list logo
