Cloud-init's default behavior was to set the hostname via the system hostname each boot and then bounce the interface. In taking a look at this, the dhcp configuration was using "gethostname()" in order to determine what name to send to the fabric. By having cloud-init set the hostname in the dchpclient configuration, this can be fixed. My patch brings cloud-init's hostname handling more inline with other datasources.
Pending merge proposal.
Cloud-init's default behavior was to set the hostname via the system hostname each boot and then bounce the interface. In taking a look at this, the dhcp configuration was using "gethostname()" in order to determine what name to send to the fabric. By having cloud-init set the hostname in the dchpclient configuration, this can be fixed. My patch brings cloud-init's hostname handling more inline with other datasources.