I'm not able to launch or even see any images in non us-east-1 regions for our AMIs. I'm sure this is related to the recent fedimg release and related deployment.
Let's get this fixed.
some more information.. here is an example of how i can see us-east-1 image and not others:
+[dustymabe@media cheatsheets]$ cat /tmp/amis.txt | head -n 25 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (us-west-2) ami-83c6d3fa hvm standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (sa-east-1) ami-9985eef5 hvm standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (us-west-1) ami-b0af82d0 hvm standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (eu-west-1) ami-65c5dd03 hvm standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (eu-central-1) ami-8c3f98e3 hvm standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-southeast-2) ami-ca0515a9 hvm standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-southeast-1) ami-f9fe729a hvm standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-northeast-1) ami-80ebfee7 hvm standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (us-west-2) ami-26c7d25f paravirtual standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (sa-east-1) ami-b484efd8 paravirtual standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (us-west-1) ami-42ad8022 paravirtual standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (eu-west-1) ami-adfae2cb paravirtual standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (eu-central-1) ami-ab3e99c4 paravirtual standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-southeast-1) ami-ecff738f paravirtual standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-southeast-2) ami-960414f5 paravirtual standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-northeast-1) ami-c0e8fda7 paravirtual standard Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (us-west-1) ami-41ad8021 paravirtual gp2 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (us-west-2) ami-03c6d37a paravirtual gp2 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (sa-east-1) ami-0386ed6f paravirtual gp2 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (eu-west-1) ami-d3c7dfb5 paravirtual gp2 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (eu-central-1) ami-a93e99c6 paravirtual gp2 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-southeast-2) ami-1e06167d paravirtual gp2 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-southeast-1) ami-f5fd7196 paravirtual gp2 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (ap-northeast-1) ami-c1e8fda6 paravirtual gp2 Fedora-Cloud-Base-25-20170621.0.x86_64 EC2 (us-east-1) ami-47654c51 hvm standard +[dustymabe@media cheatsheets]$ +[dustymabe@media cheatsheets]$ +[dustymabe@media cheatsheets]$ +[dustymabe@media cheatsheets]$ export AWS_DEFAULT_REGION=us-west-2 +[dustymabe@media cheatsheets]$ aws ec2 describe-images --image-ids ami-83c6d3fa +[dustymabe@media cheatsheets]$ +[dustymabe@media cheatsheets]$ export AWS_DEFAULT_REGION=us-east-1 +[dustymabe@media cheatsheets]$ aws ec2 describe-images --image-ids ami-47654c51 IMAGES x86_64 2017-06-21T07:33:37.000Z Created from build Fedora-Cloud-Base-25-20170621.0.x86_64 xen ami-47654c51 125523088429/Fedora-Cloud-Base-25-20170621.0.x86_64-us-east-1-HVM-standard-0 machine Fedora-Cloud-Base-25-20170621.0.x86_64-us-east-1-HVM-standard-0 125523088429 True /dev/sda1 ebs available hvm BLOCKDEVICEMAPPINGS /dev/sda1 EBS True False snap-0cafe68332581ea66 6 standard
also, just to show the AMI i queried does exist, you can see the response I got was different than what you get if you query an AMI that doesn't exist:
+[dustymabe@media cheatsheets]$ export AWS_DEFAULT_REGION=us-west-2 +[dustymabe@media cheatsheets]$ aws ec2 describe-images --image-ids ami-11111111 An error occurred (InvalidAMIID.NotFound) when calling the DescribeImages operation: The image id '[ami-11111111]' does not exist
@sayanchowdhury Can you take a look? perhaps fedimg is doing something wrong here...
@kevin: yes, I have been already looking into this issue. @dustymabe updated the issue with the findings during the discussion
I'm going to ask about this issue every day until we get it fixed. we cannot ship f26 without accessible cloud images. @sayanchowdhury feel free to make as much noise as you need in order to unblock anything that may block you from making this happen. Copy me on any communications and I'll help you in any way I can.
I have pushed & deployed fedimg=0.7.4. That should fix the issue. I'll wait for tomorrow AMI creation to see how things turn out.
If this is working now, can we go ahead and close this?
yep - this introduced another regression, but this issue is fixed.
Metadata Update from @dustymabe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.