Not all platforms running cloud-init end up with the system hostname resolveable by default
Bug #1741277 reported by
Robie Basak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Invalid
|
Undecided
|
Unassigned | ||
cloud-init |
Expired
|
Undecided
|
Unassigned | ||
cloud-init (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
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?
Changed in cloud-images: | |
status: | New → Invalid |
To post a comment you must log in.
15:25 <rbasak> I suppose the real intention of my bug is "not all platforms running cloud-init make the system hostname resolveable by default"
15:26 <rbasak> I'd consider it resolved as soon as that is true.