Public bug reported:
I have found that when I upgrade to 21.1-19-gbad84ad4-0ubuntu1~18.04.2
of cloud-init, and create an AMI, instances using that AMI fail to
detect they are in 'first boot', so they do not execute the later stages
of cloud-init.
Version 21.1-19-gbad84ad4-0ubuntu1~18.04.1 does not exhibit this
behavior; it works fine. That is, if I hold cloud-init before updating
all packages, and then create my AMI using the same process, everything
works fine. I'm running Ubuntu Pro 18.04 in FIPS mode, if that matters.
Looking through the `/var/log/cloud-init.log` and `/var/log/cloud-init-
output.log` logs, I don't see any errors, but it is possible I'm not
looking in the right place.
```
$ lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
```
Though, now I'm not sure if I understand what is happening. I see in the
output of my AMI build that cloud-init was upgraded when I upgraded all
packages. (And if I `hold` it, then this problem doesn't occur). But
here, I think I see that the package is not installed?
```
$ apt-cache policy cloud-init
cloud-init:
Installed: (none)
Candidate: 21.1-19-gbad84ad4-0ubuntu1~18.04.2
Version table:
21.1-19-gbad84ad4-0ubuntu1~18.04.2 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main
amd64 Packages
100 /var/lib/dpkg/status
18.2-14-g6d48d265-0ubuntu1 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64
Packages
```
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
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
