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.
"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: /github. com/canonical/ cloud-init/ issues/ 4302 /github. com/canonical/ cloud-init/ issues/ 4304
https:/
https:/
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.