#7797 AMIs from 2 regions unavailable
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by sayanchowdhury.

@kevin manually created the 5 AMIs manually as fedimg have trouble uploading to the two regions, us-east-2 and eu-west-3.

The list of AMIs
For us-east-2: The new AMI ID is ami-08d6e766d9302926c
For eu-west-3: The new AMI ID is ami-0e37bf70f74c79410

For us-east2: The new AMI ID is ami-00b43acad6bfbc73a
For eu-west3: The new AMI ID is ami-04abc80987c29d6fb

For us-east-2: The new AMI ID is ami-0399b24cfadfc4f33

ref: https://pagure.io/fedora-infrastructure/issue/7749#comment-568276


@sayanchowdhury are you trying to say they are missing now?

I'll investigate tomorrow, there's a access issue we have to sort out first.

Metadata Update from @kevin:
- Issue assigned to kevin
- Issue priority set to: Waiting on Assignee (was: Needs Review)

3 years ago

ok, the problem was that they were not marked public. ;(

I have fixed that now... sorry for the issue.

:bee:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

thanks @kevin!

FYI @jdoss - can you try now?

@sayanchowdhury - can you make sure we don't delete these AMIs (which seem to be oneoffs) when we run out clean AMIs script ?

from @jdoss in IRC:

16:26:07      jdoss | @dustymabe looks like that AMI ID is not deregistered anymore but it has a new error. An error occurred (InvalidRequest
                    | when calling the CopyImage operation: You do not have permission to access the storage of this ami.
16:26:42      jdoss | You can click the cloud icon and launch an instance but not use a tool like Packer to copy the AMI.

@kevin - can you also update the permissions on the underlying snapshots of the AMIs to be public? For example for ami-08d6e766d9302926c the snapshot is snap-001c931513c7fd1ae but that isn't public. we need them all to be made public.

Metadata Update from @dustymabe:
- Issue status updated to: Open (was: Closed)

3 years ago

Done. Sorry about that.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

verified:

[dustymabe@media ~]$ cat ~/Downloads/test-amis.sh
#!/bin/bash

export AWS_DEFAULT_REGION='us-east-2'
ami='ami-08d6e766d9302926c'
snapshot=$(aws ec2 describe-images --image-ids $ami --output json | jq -r .Images[0].BlockDeviceMappings[0].Ebs.SnapshotId)
aws ec2 describe-snapshots --snapshot-ids $snapshot

export AWS_DEFAULT_REGION='eu-west-3'
ami='ami-0e37bf70f74c79410'
snapshot=$(aws ec2 describe-images --image-ids $ami --output json | jq -r .Images[0].BlockDeviceMappings[0].Ebs.SnapshotId)
aws ec2 describe-snapshots --snapshot-ids $snapshot

export AWS_DEFAULT_REGION='us-east-2'
ami='ami-00b43acad6bfbc73a'
snapshot=$(aws ec2 describe-images --image-ids $ami --output json | jq -r .Images[0].BlockDeviceMappings[0].Ebs.SnapshotId)
aws ec2 describe-snapshots --snapshot-ids $snapshot

export AWS_DEFAULT_REGION='eu-west-3'
ami='ami-04abc80987c29d6fb'
snapshot=$(aws ec2 describe-images --image-ids $ami --output json | jq -r .Images[0].BlockDeviceMappings[0].Ebs.SnapshotId)
aws ec2 describe-snapshots --snapshot-ids $snapshot

export AWS_DEFAULT_REGION='us-east-2'
ami='ami-0399b24cfadfc4f33'
snapshot=$(aws ec2 describe-images --image-ids $ami --output json | jq -r .Images[0].BlockDeviceMappings[0].Ebs.SnapshotId)
aws ec2 describe-snapshots --snapshot-ids $snapshot
[dustymabe@media ~]$
[dustymabe@media ~]$ bash ~/Downloads/test-amis.sh
SNAPSHOTS       Copied for DestinationAmi ami-08d6e766d9302926c from SourceAmi ami-0e11911b7b812959f for SourceSnapshot snap-07b537b36b5a6fe3a. Task created on 1,556,636,054,415.      False   125523088429    100%    snap-001c931513c7fd1ae  2019-04-30T14:54:15.855Z        completedvol-ffffffff    4                                                               
SNAPSHOTS       Copied for DestinationAmi ami-0e37bf70f74c79410 from SourceAmi ami-0e11911b7b812959f for SourceSnapshot snap-07b537b36b5a6fe3a. Task created on 1,556,636,146,580.      False   125523088429    100%    snap-02c49f55f3b8b5b50  2019-04-30T14:55:49.321Z        completedvol-ffffffff    4                                                               
SNAPSHOTS       Copied for DestinationAmi ami-00b43acad6bfbc73a from SourceAmi ami-00bbc6858140f19ed for SourceSnapshot snap-0a397fea6b2433089. Task created on 1,556,636,287,006.      False   125523088429    100%    snap-052837a76e29e0056  2019-04-30T14:58:08.260Z        completedvol-ffffffff    4                                                               
SNAPSHOTS       Copied for DestinationAmi ami-04abc80987c29d6fb from SourceAmi ami-00bbc6858140f19ed for SourceSnapshot snap-0a397fea6b2433089. Task created on 1,556,636,332,473.      False   125523088429    100%    snap-0af9f12cbcac0cb2e  2019-04-30T14:58:54.412Z        completedvol-ffffffff    4                                                               
SNAPSHOTS       Copied for DestinationAmi ami-0399b24cfadfc4f33 from SourceAmi ami-051571ec5ffe08522 for SourceSnapshot snap-0e372a46302dd8562. Task created on 1,556,636,399,671.      False   125523088429    100%    snap-075f93d49149d0d79  2019-04-30T15:00:00.751Z        completedvol-ffffffff    4        

thanks @kevin!
FYI @jdoss - can you try now?
@sayanchowdhury - can you make sure we don't delete these AMIs (which seem to be oneoffs) when we run out clean AMIs script ?

I don't think this AMIs would be picked up by the script because the script won't getting the AMI ids from datagrepper which it relies on. But still I think having prevention measure is better and I would add it to an ignore list.

Login to comment on this ticket.

Metadata