Description of problem: I have an issue on Fedora 32 and 33 cloud base raw images. I have deployed the image on 3DS OUTSCALE (www.outscale.com) service but when I start the image, the cloud-init service is installed but is not enabled in systemd. So I don't have cloud-init support on the first startup of the instance with this image. Version-Release number of selected component (if applicable): Fedora Cloud Base Raw version 32 and 33 How reproducible: Each time Steps to Reproduce: 1. Create an image of Fedora 32 or 33 on Outscale Cloud (www.outscale.com) with dd 2. run an instance with this image Actual results: The cloud-init, cloud-config and cloud-final script did not perform Expected results: The instance are configured with value given in meta-data and user-data (SSH key, startup script, ...) Additional info: To make it work, I modify the content of the image by adding symbolic links in "/etc/systemd/system/multi-user.target.wants/" for cloud-init, cloud-config and cloud-final and adding an autorelabel for SELinux at startup.
Seems to be working fine on AWS/GCP/OpenStack. I don't think Outscale is a recognized datasource for cloud-init. If there are no recognized datasources then the generator won't enable cloud-init to start. Here is the list of datasources: https://cloudinit.readthedocs.io/en/latest/topics/datasources.html Here is the code for the generator: https://github.com/canonical/cloud-init/blob/master/systemd/cloud-init-generator.tmpl
Edouard, if I understand the feedback from Dusty correctly, Outscale should be working with upstream to make sure they are recognized as Cloud provider. Maybe you want to point them to the following document: [ Hacking on cloud-init ] https://cloudinit.readthedocs.io/en/latest/topics/hacking.html
Hello Dusty and Oliver, Thanks for your answers. Outscale is indeed not recognized as a data source by cloud-init, that's why I opened a ticket on cloud-init side : https://bugs.launchpad.net/cloud-init/+bug/1903024. Outscale provide a metadata service like AWS for instances. But what I can't understand is that if I add in the cloud-init image at startup by modifying the image as described in my first message, cloud-init works correctly. Is there a script that adds cloud-init in the startup sequence that I wouldn't have identified ? Best regards,
I linked to it in comment #1. It's the generator: https://github.com/canonical/cloud-init/blob/master/systemd/cloud-init-generator.tmpl
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.