I believe this bug/feature has been fixed in cloud-init as of cloud-init version 18.1 Azure specifically sets hostname during init-local timeframe based on this commit
https://github.com/canonical/cloud- init/commit/133ad2cb327ad17b7b81319fac8f9f14577c04df which addressed this related bug https://bugs.launchpad.net/cloud- init/+bug/1746455. If this still is a problem please feel free to re-open this bug or open a new bug descibing this issue in current cloud-init version 22.2. ** Changed in: cloud-init Status: Triaged => Fix Released -- 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/1643688 Title: Azure should set hostname during init-local Status in cloud-init: Fix Released Bug description: The Azure data-source currently considers itself a networked one, as at least part of the information is read via network. In consequence the hostname is only known after network is already setup and a ifdown/ifup cycle is initiated to update the network view of the hostname. This cycle leads to a massive delay in boot time, at least if ipv6 setup is requested. Please split hostname setup out of the normal networked init run. The information via the ovf file is known pretty early and without network. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1643688/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
