While dealing with the aarch64 AWS launch it was discovered that the latest nightly Fedora 29 stable AMIs don't boot. They make it to the "grub>" prompt and go no further.
Is there a version that worked and a version that didn't? Might help if we can look at the package diffs between them.
I know F-29 worked, and one in the last few days, sorry we've lost the AMI of the failure and I don't have time to investigate further. I would try the latest upload to see what the status is and take from there.
I imagine we'll hit this with atomic host too for our next two week release
cc @sinnykumari
I quickly launched latest aarch64 F29 cloud-base AMI from nightly Fedora-Cloud-Base-29-20181129.0 and it booted fine for me.
For Atomic Host, we have some successful AMI upload from F29 updates-testing (Fedora-AtomicHost-29_Update-20181129.0) which seems to boot and work fine.
Note: I launched both instances in eu-west-1 region.
Note
It might have been transitory, I figured it best to have a ticket to get it investigated than hope for the best and not alert people
Yeah, totally makes sense
it booted fine for me.
thanks sinny!
@pbrobinson - i'm going to close out. please re-open if you hit it again.
Metadata Update from @dustymabe: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.