Public bug reported:

Summary
=====
When launching a m6g.large AWS instance with the daily groovy image I see 
messages about failing to install the seeded snaps, which prevents installing 
any snaps. This also appears to stop cloud-init from completing:

May 29 20:53:37 ip-172-31-44-36 snapd[622]: daemon.go:343: started 
snapd/2.44.3+20.04 (series 16; classic) ubuntu/20.10 (arm64) linux/5.4.>
May 29 20:53:38 ip-172-31-44-36 snapd[622]: helpers.go:105: error trying to 
compare the snap system key: system-key missing on disk
<snip>
May 29 20:18:22 ip-10-0-0-79 snapd[1160]: handlers.go:495: Reported install 
problem for "lxd" as 8b6d20b0-a1e9-11ea-a54f-fa163e6cac46 OOPSID
May 29 20:18:23 ip-10-0-0-79 snapd[1160]: handlers.go:495: Reported install 
problem for "core18" as 8b6d20b2-a1e9-11ea-a54f-fa163e6cac46 OOPSID

Expected behavior
=====
$ sudo snap install hello-world 
<installs hello-world>
$ snap list
<shows core, core18, lxd, amazon-ssm-agent>

Actual behavior
=====
$ sudo snap install hello-world 
error: too early for operation, device not yet seeded or device model not 
acknowledged
$ snap list
No snaps are installed yet. Try 'snap install hello-world'.

Logs
=====
$ journalctl --system -u snapd
https://paste.ubuntu.com/p/j5w6mJcnfw/

$ cat /var/lib/snapd/seed/seed.yaml
https://paste.ubuntu.com/p/RzRSzW8Ch4/

$ apt-cache policy snapd
snapd:
  Installed: 2.44.3+20.04
  Candidate: 2.44.3+20.04

$ lsb_release -rd
Description:    Ubuntu Groovy Gorilla (development branch)
Release:        20.10

Workaround
=====
After running the following cloud-init completes and I am able to install 
snaps. The seeded snaps however, are not installed:
 
$ sudo apt autoremove --purge snapd
$ sudo apt install snapd

Steps to reproduce
=====
Launch a m6g.large with the daily 20.10 (Groovy) image via something like:

$ aws ec2 run-instances --image-id ami-0a5082576164ab1f7 --count 1
--instance-type m6g.large --key-name $keyname --security-group-ids
$security-group --subnet-id $subnet-id

Or you can also do this via the AWS UI by searching for the following
image name where you update the ending serial as appropriate:

Failing images:
ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-arm64-server-20200529.1
ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-arm64-server-20200529
ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-arm64-server-20200528
ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-arm64-server-20200519

Working image:
ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-arm64-server-20200514

** Affects: snapd (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/1881350

Title:
  aws m6g.large: Reported install problem for "core18"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1881350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to