On Fri, Oct 11, 2024 at 11:31:43AM +0200, Fabian Arrotin via infrastructure wrote: > Hi, > > I just created ticket https://pagure.io/fedora-infrastructure/issue/12237 > (for awareness/visibility), itself a downstream ticket of > https://issues.redhat.com/browse/CS-2561) > > It seems that we reached the AWS quota wrt number of shared AMI. > I had a *very* quick look at the regions mentioned in ticket and I see > Fedora CoreOS (mainly) has very old AMI that don't seem to be > deleted/cleaned up (or just unshared at least) > > Is there a way to ensure that all team pushing AMI to AWS various regions > would also have a max of shared images, and also unshare (or better, remove > entirely as there is another quota for number of AMI images per account) > such AMIs ? Not that I know of... but the limit is somewhat artificial. > To unblock CentOS Stream deliveries (as I got confirmation it's impacting > also Stream 9 images now), I intent (if no reaction in this thread and/or > infra ticket) to just delete the very old Fedora CoreOS AMIs next Monday David Duncan is increasing our limit now on the affected regions. That should unblock you and we can talk to coreos folks about how best to lifecycle/clean up their images. kevin
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
