Hello, after upgrading Fedora 42 to 43, I've lost network connectivity due to the broken cloud-init package. First issue was with the "nc: invalid option -- 'W'" as discussed in https://bugzilla.redhat.com/show_bug.cgi?id=2411780 -- could you back-port the fix also to the Fedora 43? Second issue was broken folder "/etc/systemd/system/cloud-init.target.wants". After the upgrade it contained: lrwxrwxrwx. 1 root root 44 Aug 22 2023 cloud-config.service -> /usr/lib/systemd/system/cloud-config.service lrwxrwxrwx. 1 root root 43 Aug 22 2023 cloud-final.service -> /usr/lib/systemd/system/cloud-final.service lrwxrwxrwx. 1 root root 48 Aug 22 2023 cloud-init-local.service -> /usr/lib/systemd/system/cloud-init-local.service lrwxrwxrwx. 1 root root 42 Aug 22 2023 cloud-init.service -> /usr/lib/systemd/system/cloud-init.service where the file "/usr/lib/systemd/system/cloud-init.service" does not exist anymore. The proper content of the file looks like this: lrwxrwxrwx. 1 root root 44 Dec 13 22:23 cloud-config.service -> /usr/lib/systemd/system/cloud-config.service lrwxrwxrwx. 1 root root 43 Dec 13 22:23 cloud-final.service -> /usr/lib/systemd/system/cloud-final.service lrwxrwxrwx. 1 root root 48 Dec 13 22:23 cloud-init-local.service -> /usr/lib/systemd/system/cloud-init-local.service lrwxrwxrwx. 1 root root 47 Dec 13 22:23 cloud-init-main.service -> /usr/lib/systemd/system/cloud-init-main.service It seems like cloud-init.service was replaced by cloud-init-main.service, however the change wasn't applied during Fedora 42 -> 43 upgrade. With cloud-init-main.service missing, cloud-init is not started at all, even with correct version of nc. "dnf reinstall cloud-init" did not fix the problem, I had to uninstall it and install again. Reproducible: Always Additional Information: cloud-init-25.2-7.fc43.noarch
FEDORA-2025-40b4f63268 (cloud-init-25.2-10.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-40b4f63268
Hi Peter, Thanks for the report. It looks like this is a combination of the unit name change, the systemd presets, and RPM scriptlets. For anyone who comes across this who also hit this issue, a manual fix is: 1. systemctl preset cloud-init-main.service 2. rm -f /etc/systemd/system/cloud-init.target.wants/cloud-init.service I've filed an update that has the nc patches as well as a post-transaction scriptlet that does the above when the dead link to cloud-init.service is present: https://bodhi.fedoraproject.org/updates/FEDORA-2025-40b4f63268
Awesome, thank you Jeremy!
FEDORA-2025-40b4f63268 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-40b4f63268` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-40b4f63268 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-40b4f63268 (cloud-init-25.2-10.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.