subiquity in 18.04.1 via cloud-init doesn't set hostname persistence

Bug #1809155 reported by Thomas Ward
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned
subiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

When installing with Subiquity, on the Live ISOs for Server, once the system is installed, cloud-init in /etc/cloud/cloud.cfg has preserve_hostname set to "False".

In essence, if you are trying to change the hostname post-install on such an installation, the changed hostname will *not* persist.

Therefore, if I installed with the hostname 'ubuntu' and want to change it to 'teward-server', the typical process is to edit /etc/hosts, /etc/hostname, and run hostnamectl to change the hostname references for the system.

Currently, however, we have to set preserve_hostname to 'True' for /etc/cloud/cloud.cfg in order for the hostname change to persist.

It should probably be done by Subiquity that after you install it you set persist_hostname to "True" in order for hostname changes post-install to still be kept and applied.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.