[Bug 276720] AMIs fail to boot in AWS EC2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276720

--- Comment #2 from mgrooms@shrew.net ---
Hi Colin. Thanks for the response. I'm running a bunch of FreeBSD in AWS, so
thanks for all your hard work.

I left some of these new instances up for several minutes knowing that the
initial boot ( growfs ) can take some time to complete. After opening this bug
report, I left one up and running overnight and the boot completed at some
point. Here is the AMI used ...

ami-0059170a80e36d30f

When I look at the boot log, I see this in the output right after the console
messages ...

Jan 29 20:56:27 freebsd freebsd-update[870]: src component not installed,
skipped
Jan 29 20:56:27 freebsd freebsd-update[870]: Looking up aws.update.FreeBSD.org
mirrors... 1 mirrors found.
Jan 29 21:00:57 freebsd freebsd-update[870]: Fetching public key from
dualstack.aws.update.freebsd.org... failed.
Jan 29 21:00:57 freebsd freebsd-update[870]: No mirrors remaining, giving up.
Jan 29 21:00:57 freebsd freebsd-update[870]: 
Jan 29 21:00:57 freebsd freebsd-update[870]: This may be because upgrading from
this platform (amd64)
Jan 29 21:00:57 freebsd freebsd-update[870]: or release (13.2-RELEASE) is
unsupported by freebsd-update. Only
Jan 29 21:00:57 freebsd freebsd-update[870]: platforms with Tier 1 support can
be upgraded by freebsd-update.
Jan 29 21:00:57 freebsd freebsd-update[870]: See
https://www.freebsd.org/platforms/ for more info.
Jan 29 21:00:57 freebsd freebsd-update[870]: 
Jan 29 21:00:57 freebsd freebsd-update[870]: If unsupported, FreeBSD must be
upgraded by source.

I think this caused a 4.5 minute delay because I booted the AMI with a security
group that didn't allow access to aws.update.FreeBSD.org. That doesn't seem
ideal :/

In any case, I'm pretty sure that solves the mystery. Sorry for the noise.

-- 
You are receiving this mail because:
You are the assignee for the bug.