yahoo-eng-team team mailing list archive

[James Falcon <1741277@xxxxxxxxxxxxxxxxxx>]

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 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 hostname
  resolveable by default

Status in cloud-images:
  Invalid
Status in cloud-init:
  Expired
Status in cloud-init package in Ubuntu:
  Confirmed

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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1741277/+subscriptions