Thanks for filing this bug report and helping make cloud-init and ubuntu better.
Each time cloud-init boots, it creates semaphore files and caches the detected
datasource so subsequent boots do not take an exhorbitant amount of time. I'm
guessing it's your clone and launch that is seeing both the cached datasource
and semophore files that is allowing the cloned VM to treat the next boot as
dirty.
Generally, when cloning and creating your own AMIs, you need to run
`sudo cloud-init clean --logs` to prior to cloning the AMI to make sure
that the image is seen as "greenfield" or fresh when that image is next
launched. That clean will remove all semaphores and cached artifacts and
all full cloud-init setup and datasource detection.
If this does not resolve the problem for you. Please run 'sudo cloud-
init collect-logs' and attach them to this bug, setting it back to
"New".
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927236
Title:
cloud-init 21.1-19-gbad84ad4-0ubuntu1~18.04.2 failing to properly
detect first boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1927236/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
