* cloud-init clean --logs --reboot to re-run upgraded cloud-init across reboot
Could you amend it to run that once with the non-proposed package, to confirm that after the clean log, it will call apt-get update again? This just to make sure that "clean" really resets things, and then we can be sure that when the proposed package is installed, it's the fix that is making "apt-get update" not being called again, and not the clean command.
Just to be sure, in the test plan, this step:
* cloud-init clean --logs --reboot to re-run upgraded cloud-init across reboot
Could you amend it to run that once with the non-proposed package, to confirm that after the clean log, it will call apt-get update again? This just to make sure that "clean" really resets things, and then we can be sure that when the proposed package is installed, it's the fix that is making "apt-get update" not being called again, and not the clean command.