Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#54785 - [cloud-init] dependency cycle in systemd
Attached to Project:
Community Packages
Opened by Jon Gjengset (Jonhoo) - Wednesday, 12 July 2017, 20:38 GMT
Last edited by Balló György (City-busz) - Sunday, 07 January 2018, 21:51 GMT
Opened by Jon Gjengset (Jonhoo) - Wednesday, 12 July 2017, 20:38 GMT
Last edited by Balló György (City-busz) - Sunday, 07 January 2018, 21:51 GMT
|
DetailsDescription:
The Fedora developers have found that cloud-init 0.7.9 introduces a dependency cycle for the systemd units which cause cloud-init init not to be run (see https://bugzilla.redhat.com/show_bug.cgi?id=1430511) in some cases, and have a patch outstanding for this at https://github.com/larsks/cloud-init/compare/0.7.9...0.7.9-patches#diff-a7f940ad724dde4f9e80c7cec7a17b71. This may be worth adopting as it means Arch cloud images are pretty difficult to get right. |
This task depends upon
Is this not something upstream should care about? Or is it Fedora-specific somehow?
https://aur.archlinux.org/packages/cloud-init/