To trigger this bug on Xenial, I did the following:
- launch a trusty instance
- Perform 'do-release-upgrade' on the trusty instance
- Reboot when complete
- Verify WARNING and Traceback present in logs
- Remove the log and reboot again
- Verify WARNING and Traceback present after second boot
To verify the bug fixed, follow the above steps, then additionally:
- Upgrade the cloud-init version to proposed
- Remove the log then reboot
- Verify no WARNING or Traceback present after boot
To trigger this bug on Xenial, I did the following:
- launch a trusty instance upgrade' on the trusty instance
- Perform 'do-release-
- Reboot when complete
- Verify WARNING and Traceback present in logs
- Remove the log and reboot again
- Verify WARNING and Traceback present after second boot
To verify the bug fixed, follow the above steps, then additionally:
- Upgrade the cloud-init version to proposed
- Remove the log then reboot
- Verify no WARNING or Traceback present after boot