** Changed in: cloud-images
Status: New => Invalid
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
Not all platforms running cloud-init end up with the system hostname
resolveable by default
Status in cloud-images:
Status in cloud-init:
Status in cloud-init package in Ubuntu:
Except for existing setups, almost everyone will want
manage_etc_hosts: localhost by default. Without this, various things
end up broken because a system can't look up its own hostname.
Are there any use cases where a default of manage_etc_hosts: localhost
will cause problems?
To avoid stepping on people's toes, I'm not suggesting making the
change retrospectively. But if new Ubuntu releases start doing it (eg.
with Bionic) and old releases maintain existing behaviour, then we'd
get there over time. Is there any existing mechanism or process for
changing cloud-init defaults like this?
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp