Summary: | Bug in downstream altlinux | ||
---|---|---|---|
Product: | Branch p11 | Reporter: | Brett Holman <bpholman5> |
Component: | cloud-init | Assignee: | qa-team <qa-team> |
Status: | CLOSED FIXED | QA Contact: | qa-p11 <qa-p11> |
Severity: | normal | ||
Priority: | P5 | CC: | bpholman5, obirvalger, shaba, stepchenko.alex |
Version: | unspecified | ||
Hardware: | x86_64 | ||
OS: | Linux |
Description
Brett Holman
2024-11-12 23:09:56 MSK
I was able to reproduce the issue by undoing the change in the PR linked below. To reproduce, basically just undo the effects of the PR in a container, then `cloud-init reboot -h now` to simulate first boot, then reboot the container and see the error. Something like this: ``` $ lxc launch images:alt/p11/cloud alt-p11 [root@alt-p11 ~]# # re-introduce update_hostname to /etc/cloud/cloud.cfg [root@alt-p11 ~]# # ... [root@alt-p11 ~]# cloud-init clean --logs --reboot $ lxc shell alt-p11 [root@alt-p11 ~]# reboot -h now [root@alt-p11 ~]# # now view the errors [root@alt-p11 ~]# cloud-init status --long [root@alt-p11 ~]# # and for more detail: [root@alt-p11 ~]# vi /var/log/cloud-init.log ``` cloud-init-24.2-alt2 -> p11 * Fri Nov 22 2024 Alexander Stepchenko <geochip@altlinux.org> 24.2-alt2 - NMU: Fix update_hostname module (Closes: 52029) Fix confirmed. The workaround was removed from upstream lxd[1]. [1] https://github.com/canonical/lxd-ci/pull/369 |