#11656 Freeze exception: cloud-init systemd presets
Closed: Duplicate 8 months ago by humaton. Opened 8 months ago by mhayden.

  • Describe the issue

As described in BZ 2236858, I would like to backport the systemd presets for cloud-init to ensure that any cloud instances with cloud-init installed will always have the cloud-init services running on first boot. This avoids a situation where cloud-init is installed but not preconfigured to start and the instance comes online with no configuration (and an unconfigured network adapter).

Any systems or images where cloud-init is not present would not be affected by this change.

  • When do you need this? (YYYY/MM/DD)

As soon as possible

  • When is this no longer needed or useful? (YYYY/MM/DD)

After F39 release.

  • If we cannot complete your request, what is the impact?

Users could potentially build images with cloud-init present but cloud-init would not start on the first boot-up. This would lead to an unconfigured system, downed network adapters, and missing ssh keys.


Closing since there is a blocker review ticket already.

Metadata Update from @humaton:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

8 months ago

Login to comment on this ticket.

Metadata