Issue on Fedora Cloud 32 & 33 cloud-init

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

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.

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.

Does anyone have an idea why this happens ? I think this is not the expected behaviour.

Thanks for your support,

--
Edouard
_______________________________________________
cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/cloud@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Big List of Linux Books]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux