Presumably the ideal solution would be for Subiquity to hand off to cloud-init in a manner that really only ran on that very first boot of the new system.
However, assuming that a true fix to that situation is too invasive to be included into Bionic at this point, it seems like it might be a good idea to at least mention the issue (and recommended workaround) in the Bionic release notes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1764172 Title: Unable to change hostname from the one specified during Bionic server installation Status in Release Notes for Ubuntu: New Status in hostname package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: New Bug description: In Bionic Beta 2 I am not able on a host or in a guest VM to change the hostname of a Bionic Beta 2 installation by changing /etc/hostname. The name in the file can be changed but it always reverts to the hostname configured during installation. In the following thread on the topic it is suggested to remove a number of cloud packages. When doing this in a VM install I could change the hostname again via /etc/hostname. https://ubuntuforums.org/showthread.php?t=2389098&page=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1764172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp