[Yahoo-eng-team] [Bug 1741277] Re: Not all platforms running cloud-init end up with the system hostname resolveable by default

Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3092 ** Bug watch added: github.com/canonical/cloud-init/issues #3092 https://github.com/canonical/cloud-init/issues/3092 ** Changed in: cloud-init Status: Confirmed => Expired -- You received this bug notific

[Yahoo-eng-team] [Bug 1741277] Re: Not all platforms running cloud-init end up with the system hostname resolveable by default

** 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. https://bugs.launchpad.net/bugs/1741277 Title: Not all platforms running cloud-init end up with the system hos

[Yahoo-eng-team] [Bug 1741277] Re: Not all platforms running cloud-init end up with the system hostname resolveable by default

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