[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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, 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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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.launchpad.net/bugs/1621393 Title: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 (20160907.1.0) has a broken (empty) /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 the `/etc/resolv.conf` file is empty and no hosts can be resolved and thus not reached. -- 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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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, since otherwise /etc/resolv.conf is broken. LP: #1621393. -- Steve Langasek Fri, 09 Sep 2016 17:04:54 -0700 ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => 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 manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
> 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/1621393 Title: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 a broken (empty) /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
** 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.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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: verification-done -- 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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Xenial) Importance: Undecided => High ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: New => Triaged ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Triaged => Fix Committed ** Tags added: verification-needed -- 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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 (empty) /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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.0) has a broken (empty) /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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 this user now * live-build/ubuntu-core/hooks/02-add_user_to_groups.chroot - dropped [ Steve Langasek ] * 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, since otherwise /etc/resolv.conf is broken. LP: #1621393. -- Steve Langasek Fri, 09 Sep 2016 15:57:27 -0700 ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => 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 manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
** 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 resolution fails Inspecting closely reveals that this image has a 0-length /etc/resolv.conf. Replacing it with a symlink to /run/resolvconf/resolv.conf fixes things. -- 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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: 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 this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
** 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 bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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/resolvconf/resolv.conf /etc/resolv.conf", privileged: true, name: "FIX RESOLV.CONF" end end end -- 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 to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
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: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
** 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) /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
