[Bug 2022102] Re: subiquity fails to see autoinstall data conveyed by cloud-init 23.2

[James Falcon]

"2) Jammy - use the legacy method of reading autoinstall data. Requires
that compatible versions of cloud-init are in the snap and in the host
OS."

What exactly does this mean? Cloud-init recently had two new bugs pop up:
https://github.com/canonical/cloud-init/issues/4302
https://github.com/canonical/cloud-init/issues/4304

and they are both reproducable on https://cdimage.ubuntu.com/ubuntu-
server/jammy/daily-live/20230730/ . They symptom is ds-identify related,
not unpickle related, but the cause is the same: that the cloud-init
version in the snap is less than the cloud-init version on the host.

Does "compatible versions of cloud-init are in the snap and in the host
OS" mean the same version? If the answer is yes, is there a build
somewhere that can be used to test that these bugs are truly fixed? If
the answer is no, then I believe that there is still an issue here to
resolve.

** Bug watch added: github.com/canonical/cloud-init/issues #4302
   https://github.com/canonical/cloud-init/issues/4302

** Bug watch added: github.com/canonical/cloud-init/issues #4304
   https://github.com/canonical/cloud-init/issues/4304

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

Title:
  subiquity fails to see autoinstall data conveyed by cloud-init 23.2

Status in subiquity:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Invalid
Status in subiquity package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Jammy:
  Invalid
Status in subiquity source package in Jammy:
  Fix Committed
Status in cloud-init source package in Mantic:
  Invalid
Status in subiquity source package in Mantic:
  Fix Committed

Bug description:
  When attempting to send autoinstall data by way of cloud-config on
  cloud-init v23.2, subiquity fails to retrieve this data from cloud-
  init.

  In this case, the following can be seen in subiquity-server-debug.log:

  Traceback (most recent call last):
    File "/snap/subiquity/4709/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 1133, in pkl_load
      return pickle.loads(pickle_contents)
  AttributeError: Can't get attribute 'IscDhclient' on <module 'cloudinit.net.dhcp' from '/snap/subiquity/4709/usr/lib/python3/dist-packages/cloudinit/net/dhcp.py'>

  The pickle file has been written by the host system cloud-init v23.2,
  whereas the older cloud-init in the snap is failing to read the data.

  At the moment mantic ISOs are affected, future ISO builds such as
  jammy would also be affected when leading up to 22.04.3.

  A proposed workaround for subiquity is to run a python script outside
  the snap context to retrieve the data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2022102/+subscriptions