Comment 2 for bug 2036848

I work with Wesley, and we got a bit more information. These are example log lines we got:

Sep 26, 2023 @ 10:53:02.109 storehelpers.go:773: cannot refresh snap "aws-cli": snap has no updates available
Sep 26, 2023 @ 10:52:59.295 storehelpers.go:773: cannot refresh: snap has no updates available: "amazon-ssm-agent", "core18", "core20", "core22", "kubectl-eks", "kubelet-eks", "snapd"
Sep 26, 2023 @ 10:52:58.524 handlers.go:677: Reported install problem for "aws-cli" as Crash report successfully submitted.
Sep 26, 2023 @ 10:52:58.089 taskrunner.go:299: [change 3 "Make current revision for snap \"aws-cli\" unavailable" task] failed: snap "aws-cli" has running apps (aws), pids: 1216
Sep 26, 2023 @ 10:52:47.992 storehelpers.go:773: cannot refresh: snap has no updates available: "amazon-ssm-agent", "core18", "core20", "core22", "kubectl-eks", "kubelet-eks", "snapd"
Sep 26, 2023 @ 10:52:46.821 backends.go:58: AppArmor status: apparmor is enabled and all features are available (using snapd provided apparmor_parser)
=Sep 26, 2023 @ 10:52:46.029 daemon.go:340: adjusting startup timeout by 1m10s (pessimistic estimate of 30s plus 5s per snap)
Sep 26, 2023 @ 10:52:45.961 daemon.go:247: started snapd/2.60.3 (series 16; classic) ubuntu/20.04 (amd64) linux/5.15.0-1045-aws.
Sep 26, 2023 @ 10:52:45.857 overlord.go:272: Acquiring state lock file
Sep 26, 2023 @ 10:52:45.857 overlord.go:277: Acquired state lock file
Sep 26, 2023 @ 10:52:27.445 main.go:124: Loading profiles [/var/lib/snapd/apparmor/profiles/snap-confine.snapd.20092 /var/lib/snapd/apparmor/profiles/snap-update-ns.amazon-ssm-agent /var/lib/snapd/apparmor/profiles/snap-update-ns.aws-cli /var/lib/snapd/apparmor/profiles/snap-update-ns.kubectl-eks /var/lib/snapd/apparmor/profiles/snap-update-ns.kubelet-eks /var/lib/snapd/apparmor/profiles/snap.amazon-ssm-agent.amazon-ssm-agent /var/lib/snapd/apparmor/profiles/snap.amazon-ssm-agent.ssm-cli /var/lib/snapd/apparmor/profiles/snap.aws-cli.aws /var/lib/snapd/apparmor/profiles/snap.kubectl-eks.kubectl /var/lib/snapd/apparmor/profiles/snap.kubelet-eks.daemon /var/lib/snapd/apparmor/profiles/snap.kubelet-eks.hook.configure /var/lib/snapd/apparmor/profiles/snap.kubelet-eks.kubelet]

My guess is we're trying to update aws-cli during boot while `aws` is running.

IMO, we shouldn't try to update `aws-cli` on boot. Should we disable this update in the AMI?

Thanks!