Ubuntu
cloud-init package

  1. Bug #1991261
  2. Comment #3

Comment 3 for bug 1991261

Revision history for this message
Chad Smith (chad.smith) wrote :

Thanks for this bug Dave and making cloud-init better.
If possible please attach the tar.gz from `sudo cloud-init collect-logs` for better triage about this regression.

There are two changes that landed in cloud-init that could potentially affect hostname setting in this release:
- [1] one change altered the frequency of cc_hostname module setting behavior to PER_INSTANCE from PER_ALWAYS, so if the install process on a RaspPi involves multiple boots and instance-id in metadata doesn't change indicating a metadata change, cloud-init won't apply that hostname correctly
- [2] one change altered certain scenarios when hostname updates are ignored

References:
- [1] https://github.com/canonical/cloud-init/pull/1651
- [2] https://github.com/canonical/cloud-init/pull/1453