Because this workaroudn is not defined here, this is a workaround in the
interim:
Edit /etc/cloud/cloud.cfg and set preserve_hostname to 'True' for
/etc/cloud/cloud.cfg in order for the hostname change to persist.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: subiquity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon changes and resets
** Changed in: subiquity
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon changes and resets /etc/hostname
** Changed in: subiquity
Importance: High => Critical
** Changed in: subiquity
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Everything subiquity does via cloud-init should be per-once not per-
boot. One way of doing this would be to have subiquity generate a cloud-
init late_command that disables cloud-init entirely but I don't know if
that's a very tasteful solution.
--
You received this bug notification because you
subiquity is providing configuration to cloud-init to perform
configuration on first boot already; cloud-init will happily do what
it's told.
I think there are several options on the configuration provided to
cloud-init. Subiquity can provide the hostname statically into the
image and not ask
@chad.smith Why should subiquity change the default setting of cloud-
init as opposed to just fixing the default setting in cloud-init? I feel
the bug is in cloud-init and not in subiquity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: id-5c7005ca28674083fa893f95
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon changes and resets /etc/hostname
To manage
** Changed in: subiquity
Status: New => Triaged
** Changed in: subiquity
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable
Hadmut, 'invalid' in cloud-init, still 'new' in subiquity.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon changes and resets /etc/hostname
Why is that bug set to invalid after recognizing a configuration
problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon changes and resets
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon changes and resets /etc/hostname
This feels a bit like subiquity should only provide hostname once via
cloud-init. Setting hostname in #cloud-config will result in cloud-init
setting this every boot
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Tags added: rls-cc-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon
Thanks for tracking down the cause Hadmut.
** Package changed: ubuntu => cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon
OK, I've found the problem.
Strange side observation: My power cable was loose, and when pulling the
network cable to ensure there's no DHCP response, I accidently pulled
the power cable as well, thus forcing the machine into a hard immediate
shutdown.
After booting from that hard shutdown, the
It's not caused by DHCP.
When entering recovery mode, /etc/hostname has already been replaced
with the old hostname, although network is not up yet and dhcp hasn't
happenend, while dmesg interestingly says to have set the hostname to
the new name (probably in initrd), so systemd must have some
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon changes and resets /etc/hostname
To manage notifications about this bug go
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780867
Title:
hostname unchangeable / some daemon changes and resets
20 matches
Mail list logo
