Comment 33 for bug 1922739

For hirsute, the bug does not reproduce on upgrade from the release day image. However, it can present when upgrading between releases.

To test, I launched a groovy instance with an old cloud-init (the same image as previously for groovy validation).

I performed a `do-release-upgrade -d` (-d, as upgrades to hirsute are not yet enabled) and rebooted: I saw the Traceback from this bug, as expected.

I then launched another groovy instance, performed another release upgrade but, before rebooting, installed cloud-init from hirsute-proposed. On reboot, I then did not see the Traceback for this bug.