cloud-init-main and ssh fail to start related to missing modules jsonpatch or configobj

[Dan Bungert]

In questing daily live-server ISO starting tomorrow - I caught this by chance with a one-off build today - when using cloud-init 25.3~1g890873f5-0ubuntu1, this message is visible in the console:

nc: /run/cloud-init/share/final.sock: No such file or directory

No cloud-init logs are present in /var/log. 3 services are in a bad state, cloud-init-main.service, ssh.{service,socket}.

`systemctl status cloud-init-main` shows a snippet of traceback where python3-jsonpatch is missing.
Installing that and restarting cloud-init-main shows another traceback, with python3-jinja2 this time.

It appears that the packages python3-{jinja2,jsonpatch} are now required but not listed in the dependency list.

Modifying the live ISO to add those two packages seems sufficient, as adding just those (plus whatever else apt pulled in) is sufficient to restore current functionality.

[Chad Smith (chad.smith)]

Upstream PR to fix this under review https://github.com/canonical/cloud-init/pull/6424/files

[Dan Bungert (dbungert)]

I was able to confirm today that the proper daily build, 20250827, does indeed show this problem. Thanks for the quick PR to resolve this.

[Chad Smith (chad.smith)]

cloud-init 25.3~2g890873f5-0ubuntu1 should resolve this issue in questing which was uploaded an hour ago.

It may have been caused by other packages in the questing image removing their dependency on jinja2/jsonpatch which cloud-init had previously not expressed in debian/control and just so happened to benefit from until recent image builds as recommended dependencies.

[Launchpad Janitor (janitor)]

This bug was fixed in the package cloud-init - 25.3~2g890873f5-0ubuntu1

---------------
cloud-init (25.3~2g890873f5-0ubuntu1) questing; urgency=medium

  * d/control: add jinja2 and jsonpatch dependencies (LP: #2121482)

 -- Brett Holman <email address hidden> Wed, 27 Aug 2025 09:01:05 -0600

[Chad Smith (chad.smith)]

Followed up with https://github.com/canonical/cloud-init/pull/6424 which also statically sets additional missing Depends due to ${python:Depends} not currently being substituted properly by dh-python in this project. The long-term fix will likely be to sort pyproject.toml settings appropriately allowing us to dynamically rely on requirements.txt instead of hard-coding all Depends: in debian/control

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2121482