[Bug 1574963] Re: juju2 lxd launch hostname reverse lookup inconsistent

[Scott Moser]

This is solvable in cloud-init, and it would not be terribly invasive
for the lxc datasource (nocloud) as that is "local".  For other
datasources that use the network, its more complex at least for now as
getting the hostname would mean dhcp on the network interface and thus
advertising 'ubuntu'.  The azure datasource actually bounces the network
interface after it comes up.

So, 2 simple-ish solutions for this
a.) cloud-init for nocloud datasource tries to apply the hostname found in the datasource when it applies networking configuration (before networking comes up).  That seems quite reasonable.
b.) the lxd templates could write /etc/hostname . I thought at one point they did.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1574963

Title:
  juju2 lxd launch hostname reverse lookup inconsistent

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1574963/+subscriptions