Here was the response from Amazon.

I launched my own test t2.large instance in us-west-2 with ami-0fd7b477 since the AMI is public. My own attempts to launch the instance were unsuccessful and resulted in the same behavior you are experiencing.

I even tried detaching the root volume and attaching it to another instance to investigate further, however the root volume from this AMI shows as unpartitioned when I run an lsblk command and contains no data. The root volume from the Fedora AMI in this example is xvdf.

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 8G 0 disk
└─xvda1 202:1 0 8G 0 part /
xvdf 202:80 0 6G 0 disk

Based on my findings, you are on the right track by contacting Fedora's AMI maintainers as the included snapshot doesn't contain any data which is causing an OS level shutdown. Please let me know if you have any further questions or need anything else.

Best regards,

Andrew H.
Amazon Web Services

Thanks @gtmanfred and @dubbb - we are looking into this!

If yall could remove the broken one for us, that would be great.

We currently have everything setup to just pull the latest, and I would prefer not to have to reconfigure them all to pull a specific ami while waiting for this to be fixed, only to have to revert that in a day or two once it is fixed.

Would be greatly appreciated.

Thanks!
Daniel

Just wanted to let you know that we have also been seeing this issue for the past several days using the Fedora-Cloud-Base-27 HVM images. Here is a screenshot of the console from EC2.

thanks @jbaird - we are looking into it. @gtmanfred - unfortunately we can't easily go in and delete those images right now. Please use images from march (before this issue starting affecting us) or start with the release day images if those can't be found.

FYI: we found the root cause: https://github.com/fedora-infra/fedimg/issues/101

We should get that fixed and hopefully have new images tomorrow or the next day.

Awesome, thanks for the update!
Daniel

Has this been fixed?

Thanks,
Daniel

hey @gtmanfred - this should be fixed now. please let us know if that is not the case for you.

They are back to working for me. This can be closed.

@dustymabe Can we close this issue?

@dustymabe Can we close this issue?

I'm +1. Can you do the honors of closing the ticket?