** Changed in: cloud-images
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/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manag
** 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/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage
The new daily xenial build for 20160907 includes the fix.
https://cloud-images.ubuntu.com/xenial/20160907/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missi
This bug was fixed in the package livecd-rootfs - 2.408.3
---
livecd-rootfs (2.408.3) xenial-proposed; urgency=medium
[ Louis Zuckerman ]
* Fixes for vagrant box builder in ubuntu-cpc LP: #1565985
- Install virtualbox-guest-utils
- Don't disable default synced folder
-
Fix confirmed.
Here's how I tested:
- Downloaded current xenial vagrant box and started a VM from it
- Enabled xenial-proposed repository
- Installed livecd-rootfs from -proposed, version 2.408.3
- ran the following commands...
sudo -i
mkdir /build
cd /build
cp -a /usr/share/livecd-rootfs/live-b
Hello LoOoD, 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.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Xenial)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: livecd-rootfs (Ubuntu Xenial)
FWIW this code in bootstrap.sh should help mitigating the issue:
if ! grep -q $(cat /etc/hostname) /etc/hosts; then
echo >> /etc/hosts
echo 127.0.0.1 $(cat /etc/hostname) >> /etc/hosts
fi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
About libnss-myhostname. This was how it was done in the trusty box. Not
saying it should be done that way in xenial though...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vag
This bug and LP: #1565985 are fixed in yakkety. I've opened an SRU to
get the fixes into xenial (LP: #1605795). I hope to make progress on
the SRU this week.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Does not appear to be resolved in ubuntu/xenial64 20160721.0.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage noti
This bug was fixed in the package livecd-rootfs - 2.421
---
livecd-rootfs (2.421) yakkety; urgency=medium
[ Louis Zuckerman ]
* Fixes for vagrant box builder in ubuntu-cpc LP: #1565985
- Install virtualbox-guest-utils
- Don't disable default synced folder
- Don't set v
Here's the bug for discussing whether or not to include config
management packages in the vagrant box:
https://bugs.launchpad.net/cloud-images/+bug/1599531
Please add your thoughts there if you have an opinion.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bu
@dan: agree with trusty release .. but i think that discussion should be
on another changerequest :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its
On 06/07/16 11:32, GGeorg wrote:
> * libnss-myhostname will fix _this_ problem but might break things for
> other users, i would not recommend going this route as it changes an
> already released package list and image. Bad for LTS i would suggest to
> use the existing and already proven cloud-init
@Dan: Thx for your feedback i checked the diff at:
https://i267500511.restricted.launchpadlibrarian.net/267500511/3d1e0c04
-3a0e-11e6-bd2f-002481e91f22.txt?token=4gc9PKPGwls2N9trTB0D26bj1nLqDrbv
Absolutly see your point in the buildds infrastructure :)
Here is my feedback:
* libnss-myhostname w
Hi Georg,
On 06/07/16 09:55, GGeorg wrote:
> could you provide the patch so we could review it ? The box file you
> provided is in no way compareable to cloud-images.
The box file I provided is what we expect to become the cloud image; it
is directly comparable. :)
> The box file is about twice
Hi Dan,
could you provide the patch so we could review it ? The box file you
provided is in no way compareable to cloud-images.
The box file is about twice the size - so it was built in another way.
I think the only proper way to fix this (no change in filesystem or
installed packets) is changin
This change will be backported to xenial, but only once we've heard that
we've actually fixed it.
Robert, GGeorg, LoOoD, does the box I provided fix the issue?
(Also, Robert, I really do understand the frustration but this wasn't
actually as simple a fix as you seem to think; Vagrant boxes should
Hi,
in case you are stuck, here is my workaround that should bring back most
of the default features.
To be fair, this could also be fixed very easy by a way simpler approach
using cloud-inits user-data feature within vagrant. All it would need is
this line in the box user-data image in ubuntu-xe
Presumably they'll stick to the "S" in LTS and backport this change, but
I can understand their desire to test it quickly before diving in.
I also understand limited resources. However, I think a reprioritization
is in order here. This bug was not a difficult or time consuming one to
solve. Furthe
Dan, will you be building an updated xenial image from the contributed
patch or will only releases greater then 16.04 only have the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Hello all,
The Vagrant boxes are important to us, and we do want them to be a high-
quality Ubuntu experience. That said, our limited resources have been
focussed on improving that experience in the images which people use in
production. We would like to have the time to work on everything that
This bug- which literally just required a line in the hosts file- is
still not resolved months later. Does the cloud team just not want
people to upgrade to the latest LTS version? I can't imagine any other
reason to ignore this issue, especially considering it's easy fix.
--
You received this bu
Any status update?
'ubuntu/xenial64' (v20160627.0.0) for 'virtualbox' still has the
problem.
Repeating my 06/19 post:
Is there a HOWTO or link for how to build the xenial image?
Might be easier for us to help troubleshoot the problem if we could
build the xenial image, fix what's wrong, and su
Based on #13 and related comments, I noticed that on my AWS account I
wasn't getting a Public DNS assigned each time I launched ami-08490c68.
Found this link to resolve that by adding a Virtual Private Cloud (VPC)
per this link:
http://stackoverflow.com/questions/20941704/ec2-instance-has-no-pub
There is a really amazingly simple work around to this problem that
works without needing a custom box.
In your VagrantFile use the config.vm.hostname option to specify a
hostname-
config.vm.hostname = "vagrant"
That will change the hostname before the networking and provisioning
steps occur (I'
Is there a HOWTO or link for how to build the xenial image?
Might be easier for us to help troubleshoot the problem if we could
build the xenial image, fix what's wrong, and submit the patches back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I can confirm this issue is also present when running on macOS.
-
$ uname -a
Darwin 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016;
root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
$ vagrant --versi
The problem went away after upgrading to the following versions.
vagrant --version
Vagrant 1.8.4
vboxmanage --version
5.0.22r108108
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xeni
==> default: Box 'ubuntu/xenial64' (v20160615.1.0) is running the latest
version.
vagrant --version
Vagrant 1.8.1
vboxmanage --version
5.0.20r106931
(Host OS)
uname -a
15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu
3248.50.21~8/RELEASE_X86_64 x86_64
==> default: C
I am able to reproduce this as well.
Example:
---
$ vagrant --version
Vagrant 1.8.3
$ vboxmanage --version
5.0.20r106931
$ vagrant init ubuntu/xenial64
$ vagrant box list | grep xenial
ubuntu/xenial64(virtualbox, 20160
Can confirm I am also running into this. It's preventing vagrant
configurations that involve private networking from loading as this
error stops the provisioning process- basically making it impossible to
use these images for testing certain (fairly common) scenarios using
vagrant.
If there's a re
It turns out that it _isn't_ resolving, which my ISP then redirects to a
portal to try and get advertising clicks. Thanks, BT.
** Changed in: cloud-images
Status: Incomplete => Confirmed
** Changed in: livecd-rootfs (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bu
Can we unmark this as "Incomplete"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage notifications about this bug go
** Changed in: cloud-images
Milestone: y-2016-06-02 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage not
Also seeing this:
$ vboxmanage --version
5.0.10r104061
$ vagrant --version
Vagrant 1.8.1
$ vagrant box list |grep -i xenial
ubuntu/xenial64 (virtualbox, 20160420.3.0)
ubuntu/xenial64 (virtualbox, 20160509.0.0)
ubuntu/xenial64 (virtualbox, 20160531.0.0)
$ vagrant init ubuntu/xenia
Dan, is it possible that there's a resolver on your machine/network that
is resolving that hostname for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is miss
host: OS X 10.11.5
$ vboxmanage --version
5.0.20r106931
$ vagrant --version
Vagrant 1.8.1
$ vagrant init ubuntu/xenial64
$ vagrant box list|grep xenial
ubuntu/xenial64 (virtualbox, 20160531.0.0)
$ vagrant up
$ vagrant ssh -- sudo grep hosts /etc/nsswitch.conf
sudo: unable to r
Dan, could you also run these commands?? And purge all your boxes before
"vagrant up"?
vagrant ssh -- sudo grep ubuntu /etc/hosts
vagrant ssh -- sudo grep 127 /etc/hosts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
$ : vboxmanage --version
5.0.20r106931
$ : vagrant --version
Vagrant 1.8.0
$ : vagrant box list |grep -i xenial
$ : vagrant init ubuntu/xenial64
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the
$ vagrant box list | grep xenial
Odd_Bloke/xenial64 (virtualbox, 20160319.0.0)
ubuntu/xenial64 (virtualbox, 20160319.0.0)
ubuntu/xenial64 (virtualbox, 20160418.0.0)
ubuntu/xenial64 (virtualbox, 20160420.3.0)
ubuntu/xenial64 (virtualbox, 20160521.0.0)
ubuntu/xenial64 (virt
(I have tested 5.0.20; I still can't reproduce)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage notifications about
I'll be surprised if the problem is in the Virtualbox 5.0.20, what is
the xenial image you are testing against Dan? Your vagrant box list |
grep xenial?
I had the same problem with 5.0.18, but no longer have it installed.
--
You received this bug notification because you are a member of Ubuntu
B
To confirm Toni's comment, my testing yields the same result:
$ vboxmanage --version
5.0.20r106931
$ vagrant --version
Vagrant 1.8.1
$ vagrant box list | grep xenial
ubuntu/xenial64 (virtualbox, 20160531.0.0)
$ vagrant init ubuntu/xenial64
$ vagrant up
$ vagrant ssh -- sudo grep hosts /etc/nss
Dan if it helps reproduce:
I'm running a 64bit trusty host using the "virtualbox-5.0" package from the
"deb http://download.virtualbox.org/virtualbox/debian trusty contrib"
repository.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, thanks for that, Toni.
I'm on Virtualbox 5.0.18, so I'm building 5.0.20 to test that version on
my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is
Host: OS X 10.11.5, VirtualBox 5.0.20
⇒ vagrant --version
Vagrant 1.8.1
⇒ vagrant init ubuntu/xenial64
⇒ vagrant box list|grep xenial
ubuntu/xenial64 (virtualbox, 20160531.0.0)
⇒ vagrant up
⇒ vagrant ssh -- sudo grep hosts /etc/nsswitch.conf
sudo: unable to resolve host ubuntu-xenial
host
So I have just looked in to this, and I can't reproduce it. I did the
following:
$ vagrant --version
Vagrant 1.8.1
$ vagrant init ubuntu/xenial64
$ vagrant up
$ vagrant ssh -- sudo grep hosts /etc/nsswitch.conf
hosts: files dns
(I've also done some interactive sudo'ing in there, and I
Still see the problems with 'ubuntu/xenial64' (v20160527.0.0)
Switching from the user vagrant and ssh key authentication to user
ubuntu and password authentication lets things progress a little further
but run into hostname problem.
The following SSH command responded with a non-zero exit status.
** Changed in: cloud-images
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname i
** Changed in: cloud-images
Milestone: None => y-2016-06-02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage not
Actually, we now have:
hosts: files mdns4_minimal [NOTFOUND=return] dns
since libnss-myhostname is not installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is
On trusty, the hostname was not in /etc/hosts and it was working fine.
The real issue here is that sudo looks into DNS before hostname.
In /etc/nsswitch.conf, we had on trusty:
hosts: files myhostname mdns4_minimal [NOTFOUND=return] dns
We now have:
hosts: files mdns4_minimal [N
How were precise and trusty images built? They worked fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage notific
The attachment "live-build.patch" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
~brian-murra
Root Cause:
Setting the hostname to "ubuntu-${release}" in cloud-images causes the
hostname not to be resolvable using /etc/hosts. Running hostname -f will
fail due to unresolveable default hostname causing a failure when
setting up the proper hostname by vagrant.
Suggested Fix:
Set the hostname
as far as i could see the problem is within the package live-build which
is used to build the cloud-images
There is a hook for vagrant. i assume this is rather bogus, the hostname
should not be something that changes per relesase, its better to have
some solid default like "localhost" that is reso
@Nayeem I *believe* the image building process is described here:
https://help.ubuntu.com/community/UEC/Images#Building_Your_Own_Ubuntu_Cloud_Guest_images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
is there any fixes to this? If we can look at the code that creates the
vagrant-image I am happy to try to find a fix for it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagr
Just to expand on this, this issue is also present in the latest Xenial
AWS AMI, with ID ami-64140d0e. This makes running Xenial on AWS
difficult, to say the least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: 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/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage notification
** Changed in: cloud-images
Status: New => Confirmed
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/h
This also prevents changing the box's hostname, as the command `sudo
hostname -f` not only gets the sudo warning on stdout as mentioned
above, but the `hostname -f` also fails with a non-zero exit code since
resolution fails.
--
You received this bug notification because you are a member of Ubunt
Unfortunately the above-mentioned fix is not possible when your
Vagrantfile contains extra network configuration. In those cases, you
get something like this before you get a chance to update the hosts
file:
The following SSH command responded with a non-zero exit status.
Vagrant assumes t
** Also affects: cloud-images
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/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To
Adding the following line to /etc/hosts will work around this issue:
127.0.1.1 ubuntu-xenial
According to Ubuntu's profile on https://atlas.hashicorp.com/ubuntu/,
bugs should be filed on the cloud-images project
(https://bugs.launchpad.net/cloud-images).
--
You received this bug notification be
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: 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/1561250
Title:
Xenial vagra
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
69 matches
Mail list logo
