Learn more about these different git repos.
Other Git URLs
The .0 AMI image uploads seem to have failed for gp2 AMIs for some reason. Here are the ones that succeeded:
.0
Fedora-Atomic-25-20170425.0.x86_64 EC2 (us-west-2) ami-c90f90a9 hvm standard Fedora-Atomic-25-20170425.0.x86_64 EC2 (sa-east-1) ami-ec92ff80 hvm standard Fedora-Atomic-25-20170425.0.x86_64 EC2 (us-west-1) ami-66be9a06 hvm standard Fedora-Atomic-25-20170425.0.x86_64 EC2 (eu-west-1) ami-0c88896a hvm standard Fedora-Atomic-25-20170425.0.x86_64 EC2 (eu-central-1) ami-74da061b hvm standard Fedora-Atomic-25-20170425.0.x86_64 EC2 (ap-southeast-2) ami-a01e16c3 hvm standard Fedora-Atomic-25-20170425.0.x86_64 EC2 (ap-southeast-1) ami-91db60f2 hvm standard Fedora-Atomic-25-20170425.0.x86_64 EC2 (ap-northeast-1) ami-cbb69dac hvm standard Fedora-Atomic-25-20170425.0.x86_64 EC2 (us-east-1) ami-f98318ef hvm standard
I want to see if the image uploads keep failing or if it is a flake.
We should debug in fedimg why the upload failed. and there should be some way that is less of a sledge hammer to attempt re-upload than a whole new compose
yes, I agree. The only guy who knows how to debug this is AFK for the day because of hardware failure. So I've got no ideas. I'm available for debugging if you have ideas.
If you have one good set of snapshots you can register them a second time with different settings to get the gp2 images.
% export AWS_ACCESS_KEY_ID=xxx % export AWS_SECRET_ACCESS_KEY=xxx % euca-register --region us-east-1 -n Fedora-Atomic-25-20170425.0.x86_64-us-east-1-HVM-gp2-0 --virtualization-type hvm -b /dev/sda1=snap-064a4f68184d34869:6:true:gp2 IMAGE ami-xxxxxxxx % euca-modify-image-attribute --region us-east-1 -l -a all ami-xxxxxxxx
i paid the 24 hour hit in productivity already so we should be able to close this.
@dustymabe Can we have a document on how to debug the upload process so that we dont have to go through this next time?
@mohanboddu - that is something only @sayanchowdhury can give us. I have asked him for a knowledge transfer of fedimg. Would you like to be invited?
@dustymabe sure, I dont want to have a single point of failure.
Also, closing the ticket since its not needed anymore.
Metadata Update from @mohanboddu: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.