** No longer affects: ubuntu-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
This got fixed quite a while ago I think, apologies for the lack of
updates.
** Changed in: subiquity
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hostname in Ubuntu.
Ah oops, this one fell through the cracks. Should try to do a quick fix.
** Package changed: subiquity (Ubuntu) => subiquity
** Changed in: subiquity
Status: New => Triaged
** Changed in: subiquity
Importance: Undecided => High
--
You received this bug notification because you are a
(In addition to the one mentioned by WirelessMoves, I found several
other Ubuntu Forum threads as well as blog posts, etc. which recommend
working around this problem by editing the /etc/cloud/cloud.cfg file to
set the "preserve_hostname:" line's value to "true". However, that
approach means
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
When installing Ubuntu Server using Subiquity (i.e. using the
ubuntu-18.04-live-server-amd64.iso installer image), the user is
prompted to enter a hostname for the new installation (along with
username/password info, etc.)
At the very end of the Subquity run, it writes this info into
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
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
7 matches
Mail list logo
