Closed orebmann closed 1 year ago
@orebmann did you mark the image as cloud init capable?
Hi Oliver, thanks for reaching out. As discussed, feel free to join our Operate First office hours (Mon to Thu, 11am New York UTC-5 / 5pm Europe/Berlin UTC +1)
Hi we did mark the image as Cloud Init compatible but somehow cloud-init is not triggered.
@durandom I am a little out of ideas. Do you have another "trick" in mind?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/close what is the current status? feel free to open again, if needed
@orebmann
Hi,
we are trying to get the RHEL8 / RH CoreOS Standard qcow2 images to run in IONOS DCD but somehow we did not get cloud-init to run... instead the image always came up with uid/pw prompt but did not take the cloud-init config provided in the IONOS DCD.
A workaround was to baking in the uid/pw into the image using virt-customize, but the target config (providing ssh keys via cloud-init) somehow does not work with IONOS DCD... any ideas?
Thanks a lot in advance for your help.