[Bug 2081325] Re: Oracular: systemd override file not applied due to systemd unit rename cloud-init.service renamed to cloud-init-network.service in cloud-init v. 24.3.1

[James Falcon]

** Description changed:

- I Oracular 24.10, cloud-init 24.3.1 renamed cloud-init.service to cloud-
- init-network.service as part of the single-process mode support.  This
- is only introduced in Oracular and not applicable to any stable releases
- before Oracular.[1]
+ In Oracular 24.10, cloud-init 24.3.1 renamed cloud-init.service to
+ cloud-init-network.service as part of the single-process mode support.
+ This is only introduced in Oracular and not applicable to any stable
+ releases before Oracular.[1]
  
  livecd-rootfs provides complete override for the entire cloud-
  init.service in /etc/systemd/system/cloud-init.service to reorder the
  service After=NetworkManager.service NetworkManager-wait-online.service
  and drop # Before=sysinit.target. This overridden file is completely
  ignored in Desktop Oracular images dated 20240916 because the systemd
  unit name cloud-init.service doesn't match the new cloud-init-
  network.service name. This results in incorrect systemd ordering that
  may impact cloud-init's ability to download configuration when kernel
  commandline options provide a nocloud seed url that requires DNS
  resolution via a kernel commandline
  'ds=nocloud;s=http://myresolvablehostname/'.
  
- 
- To fix this issue, livecd-rootfs should be emitting and override file to /etc/systemd/system/cloud-init-network.service with the latest content provided by cloud-init 24.3.1 in oracular.
+ To fix this issue, livecd-rootfs should be emitting an override file to
+ /etc/systemd/system/cloud-init-network.service with the latest content
+ provided by cloud-init 24.3.1 in oracular.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2081325

Title:
  Oracular: systemd override file not applied due to systemd unit rename
  cloud-init.service renamed to cloud-init-network.service in cloud-init
  v. 24.3.1

Status in cloud-init package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in cloud-init source package in Oracular:
  New
Status in livecd-rootfs source package in Oracular:
  Confirmed

Bug description:
  In Oracular 24.10, cloud-init 24.3.1 renamed cloud-init.service to
  cloud-init-network.service as part of the single-process mode support.
  This is only introduced in Oracular and not applicable to any stable
  releases before Oracular.[1]

  livecd-rootfs provides complete override for the entire cloud-
  init.service in /etc/systemd/system/cloud-init.service to reorder the
  service After=NetworkManager.service NetworkManager-wait-
  online.service and drop # Before=sysinit.target. This overridden file
  is completely ignored in Desktop Oracular images dated 20240916
  because the systemd unit name cloud-init.service doesn't match the new
  cloud-init-network.service name. This results in incorrect systemd
  ordering that may impact cloud-init's ability to download
  configuration when kernel commandline options provide a nocloud seed
  url that requires DNS resolution via a kernel commandline
  'ds=nocloud;s=http://myresolvablehostname/'.

  To fix this issue, livecd-rootfs should be emitting an override file
  to /etc/systemd/system/cloud-init-network.service with the latest
  content provided by cloud-init 24.3.1 in oracular.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2081325/+subscriptions