On Tue, Apr 24, 2018 at 05:50:13PM -, Jeremy Bicha wrote:
> > The only case where nss-myhostname actually makes sense is if you have
> a read-only /etc, which is not true here.
> I disagree. It is annoying that system administrators need to change
> both /etc/hostname and /etc/hosts instead
> The only case where nss-myhostname actually makes sense is if you have
a read-only /etc, which is not true here.
I disagree. It is annoying that system administrators need to change
both /etc/hostname and /etc/hosts instead of being able to change just
one place: /etc/hostname (or use
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741277
Title:
Not all platforms running cloud-init end up with the system hostname
> We could have lxd always ensure the entry in /etc/hosts. That won't
conflict with cloud-init, and will resolve my problem.
uvtool and multipass will also need to be adjusted. Currently I don't
think either do anything to the image except through cloud-init. Perhaps
the right way in this case is
On Thu, Jan 04, 2018 at 05:41:40PM -, Robie Basak wrote:
> On Thu, Jan 04, 2018 at 05:25:54PM -, Steve Langasek wrote:
> > AIUI lxd is setting /etc/hostname, but is not adding the Ubuntu-standard
> > entry (127.0.1.1 hostname.domain hostname) to /etc/hosts; so that should
> > be fixed in
I agree with Robie, yes we can fix lxd to modify file contents in the
guest more than it already does. But that is quite hacky. It would be
equivalent to having cloud-init set manage_etc_hosts to localhost on
lxd.
that does not solve the problem everywhere though.
--
You received this bug
On Thu, Jan 04, 2018 at 05:25:54PM -, Steve Langasek wrote:
> AIUI lxd is setting /etc/hostname, but is not adding the Ubuntu-standard
> entry (127.0.1.1 hostname.domain hostname) to /etc/hosts; so that should
> be fixed in lxd.
That's not currently an Ubuntu-standard on clouds, AIUI.
We have repeatedly rejected nss-myhostname as a solution in Ubuntu; it
adds additional runtime complexity for an issue that had been
serviceably addressed by configuring /etc/hosts in tandem with
/etc/hostname. The only case where nss-myhostname actually makes sense
is if you have a read-only
marked as cloud-images as that is where the change for nss-myhostname
would be made (i think).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741277
Title:
Not all platforms running cloud-init end
fwiw, its sudo that is causing the roundtrip.
you can certainly come up with reasons to pay a round trip. the infrastructure
then can make changes and each system magically picks them up. its the reason
we don't ship /etc/hosts files around anymore.
all that said, this issue can definitely be
Scott pointed out that on a "proper" cloud, the hostname is resolveable
by DNS because that's the name given to the instance by the cloud. This
isn't the case on lxd though, for example. And I'm not sure that it
makes sense to round trip local hostname lookups through the network in
the "proper"
11 matches
Mail list logo
