FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
In this step I plan to keep the associated snapshots. So if I break something we can still restore the AMI.
BTW - quick summary where we are with the cleanup stuff:
* all VM, volumes have tag FedoraGroup
* all gp2 volumes are migrated to gp3
* All AMIs with name 'Fedora-AtomicHost-*' are deleted. Including associated snapshots
* all Fedora GA AMIs and snapshots are tagged with FedoraGroup.
* all old (2021-) snapshots with no associated AMIs are deleted.
On Thu, Mar 14, 2024 at 09:58:47AM +0100, Miroslav Suchý wrote:
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
Sure, but note that freeze is only over once we ship a beta. ;)
But I don't knot that this needs to wait on that. It seems pretty safe.
In this step I plan to keep the associated snapshots. So if I break something we can still restore the AMI.
BTW - quick summary where we are with the cleanup stuff:
all VM, volumes have tag FedoraGroup
all gp2 volumes are migrated to gp3
All AMIs with name 'Fedora-AtomicHost-*' are deleted. Including associated snapshots
all Fedora GA AMIs and snapshots are tagged with FedoraGroup.
all old (2021-) snapshots with no associated AMIs are deleted.
Thanks again for moving this forward.
kevin
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deleted all AMIs that does not have tag FedoraGroup and that were older than 2019-01-01.
For the record, the list of deleted AMIs is in attachement. And the script that I used is https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered 36996 AMIs. The associated snapshots still exists.
On Tue, Apr 02, 2024 at 07:13:56AM +0200, Miroslav Suchý wrote:
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deleted all AMIs that does not have tag FedoraGroup and that were older than 2019-01-01.
For the record, the list of deleted AMIs is in attachement. And the script that I used is https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered 36996 AMIs. The associated snapshots still exists.
Hurray!
Thanks again for doing this.
kevin
Dne 02. 04. 24 v 7:45 odp. Kevin Fenzi napsal(a):
On Tue, Apr 02, 2024 at 07:13:56AM +0200, Miroslav Suchý wrote:
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deleted all AMIs that does not have tag FedoraGroup and that were older than 2019-01-01.
For the record, the list of deleted AMIs is in attachement. And the script that I used is https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered 36996 AMIs. The associated snapshots still exists.
Hurray!
Thanks again for doing this.
You are welcome. But I have to say I am scared. I just ask myself: and centos AMIs are stored under which account?
Our account, is the answer!
So, I have just tagged all AMIs from
https://www.centos.org/download/aws-images/
with FedoraGroup=ga-archives
Any idea if I missed something else before I start deleting the more recent ones?
On Tue, Apr 02, 2024 at 09:39:46PM +0200, Miroslav Suchý wrote:
Dne 02. 04. 24 v 7:45 odp. Kevin Fenzi napsal(a):
On Tue, Apr 02, 2024 at 07:13:56AM +0200, Miroslav Suchý wrote:
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deleted all AMIs that does not have tag FedoraGroup and that were older than 2019-01-01.
For the record, the list of deleted AMIs is in attachement. And the script that I used is https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered 36996 AMIs. The associated snapshots still exists.
Hurray!
Thanks again for doing this.
You are welcome. But I have to say I am scared. I just ask myself: and centos AMIs are stored under which account?
Our account, is the answer!
Yep. ;(
It is scary, but it should be done...
So, I have just tagged all AMIs from
https://www.centos.org/download/aws-images/
with FedoraGroup=ga-archives
ok.
I suspect there's a lot fewer of them than the fedora ones?
Any idea if I missed something else before I start deleting the more recent ones?
I don't think so...
kevin
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I used script:
https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered more than 8k AMIs (now tell me what I broke)
The full log is here (well almost full as I forgot to log it at the beggining so few hundreds of lines are lost)
On Thu, Jun 20, 2024 at 01:55:29PM GMT, Miroslav Suchý wrote:
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I used script:
https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered more than 8k AMIs (now tell me what I broke)
The full log is here (well almost full as I forgot to log it at the beggining so few hundreds of lines are lost)
Thanks!
Nothing so far broken I know of.
kevin
Dne 20. 06. 24 v 1:55 odp. Miroslav Suchý napsal(a):
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I continued with all older than 2021-01-01.
1240 AMis deregistered.
The log is here: https://k00.fr/n2tx12di
Dne 26. 06. 24 v 11:43 odp. Miroslav Suchý napsal(a):
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I continued with all older than 2021-01-01.
I continued with all older than 2022-01-01.
797 AMIs deregistered.
The log is here: https://k00.fr/a5oqhiho
FYI - My next intent. Do one more run for AMIs older than 2023 in few days. Then I will pause (because PTOs. In August start deleting snapshots that were left behind AMIs. And in September continue with deleting most recent AMIs.
On Sun, Jun 30, 2024 at 06:52:53PM GMT, Miroslav Suchý wrote:
Dne 26. 06. 24 v 11:43 odp. Miroslav Suchý napsal(a):
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I continued with all older than 2021-01-01.
I continued with all older than 2022-01-01.
797 AMIs deregistered.
The log is here: https://k00.fr/a5oqhiho
FYI - My next intent. Do one more run for AMIs older than 2023 in few days. Then I will pause (because PTOs. In August start deleting snapshots that were left behind AMIs. And in September continue with deleting most recent AMIs.
ok. Sounds good!
kevin
Dne 30. 06. 24 v 6:52 odp. Miroslav Suchý napsal(a):
I continued with all older than 2022-01-01
I continued with all older than 2023-01-01.
1014 AMIs deregistered.
The log is here: https://k00.fr/opdxkbs9
4283 AMI without tag remains. I see on the list AMIs like:
* CPE RHEL 9.1 * CentOS Stream 9x86_64 20240624 * CentOS Stream 8 aarch64 20240429 * Fedora-Cloud-Base-39_Beta-1.1.aarch64-hvm-us-east-2-gp3-0 * Fedora-Cloud-Base-AmazonEC2.x86_64-40-20240622.0-hvm-us-east-2-gp3-0 * fedora-coreos-40.20240301.92.0-x86_64
Full list is here: https://k00.fr/5z8vge8p
If any of these is yours, please tag it with FedoraGroup otherwise it will be deleted at the end of summer.
On 02/07/2024 08:59, Miroslav Suchý wrote:
Dne 30. 06. 24 v 6:52 odp. Miroslav Suchý napsal(a):
I continued with all older than 2022-01-01
I continued with all older than 2023-01-01.
1014 AMIs deregistered.
The log is here: https://k00.fr/opdxkbs9
4283 AMI without tag remains. I see on the list AMIs like:
- CPE RHEL 9.1
I'll take care of these ones
- CentOS Stream 9x86_64 20240624
- CentOS Stream 8 aarch64 20240429
For CentOS Stream, it would have been a good idea to ask them to tag properly , as I don't think they read the Fedora infra list. So I just played MITM and created issue, so that they'll take action : https://issues.redhat.com/browse/CS-2315
Dne 02. 07. 24 v 8:59 dop. Miroslav Suchý napsal(a):
I continued with all older than 2023-01-01.
1014 AMIs deregistered.
I continued with all older than 2023-06-01.
I forgot to keep the full log.
And because no one objected to all these missing AMIs I deleted in past months I also deleted the snapshots. 55 749 snapshots were deleted.
The full log is
Dne 12. 10. 24 v 8:59 odp. Miroslav Suchý napsal(a):
I continued with all older than 2023-06-01.
I continued with all older than 2023-09-01.58
458 AMIs deregistered.
The log is here:
Dne 16. 10. 24 v 1:56 odp. Miroslav Suchý napsal(a):
I continued with all older than 2023-09-01.58
458 AMIs deregistered.
The log is here:
I continued with all older than 2023-10-01
38 AMIs deregistered
The log is here:
Dne 17. 10. 24 v 4:00 odp. Miroslav Suchý napsal(a):
I continued with all older than 2023-10-01
38 AMIs deregistered
I continued with all older than 2023-11-01
86 AMIs deregistered
The log is here
Dne 18. 10. 24 v 2:09 odp. Miroslav Suchý napsal(a):
I continued with all older than 2023-11-01
86 AMIs deregistered
I continued with all older than 2023-12-01
62 AMIs deregistered
The full log is here
Dne 20. 10. 24 v 8:42 odp. Miroslav Suchý napsal(a):
I continued with all older than 2023-12-01
62 AMIs deregistered
I continued with all older than 2024-01-01
55 AMIs deregistered
Full log is here:
Dne 21. 10. 24 v 8:47 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-01-01
55 AMIs deregistered
I continued with all older than 2024-02-01
13 AMIs deregistered
Full log is here https://k00.fr/b96c2y2v
Hmm, I quickly checked if Fedora 40 AMIs are tagged - so I do not accidentally delete it in next days. They were not.
I tagged them
$ ./label-ami-id.pyami-04d91473d6ab0eb84 Found AMI ami-04d91473d6ab0eb84 in ap-northeast-1 Tagged ami ami-04d91473d6ab0eb84 in ap-northeast-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0a61e303ec3d59210 for AMI ami-04d91473d6ab0eb84 in ap-northeast-1 Tagged snapshot snap-0a61e303ec3d59210 in ap-northeast-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} 🎩[msuchy@triple/~/projects/fedora-infra-scripts{main}]$ cat/tmp/ids.txt ami-0b9e37d36fa8859bb ami-07dc7a11eca06eccc ami-0e4a3a32304cedfaf ami-0bbff6b12ddeda7c3 ami-016fcb6ce04d7b7d9 ami-06aa46f98ac220143 ami-00050c079abc52c85 ami-05a5944c1a28d223d ami-08b4257b37b902e30 ami-004f552bba0e5f64f ami-097f74237291abc07 ami-0aca2ed5c7b247386 ami-089b6143ef0e57f4b 🎩[msuchy@triple/~/projects/fedora-infra-scripts{main}]$ foriin$(cat/tmp/ids.txt);do ./label-ami-id.py"$i" done
Found AMI ami-0b9e37d36fa8859bb in ap-northeast-2 Tagged ami ami-0b9e37d36fa8859bb in ap-northeast-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-041567ba05d4f6471 for AMI ami-0b9e37d36fa8859bb in ap-northeast-2 Tagged snapshot snap-041567ba05d4f6471 in ap-northeast-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-07dc7a11eca06eccc in ap-south-1 Tagged ami ami-07dc7a11eca06eccc in ap-south-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-078d8a14651133cd7 for AMI ami-07dc7a11eca06eccc in ap-south-1 Tagged snapshot snap-078d8a14651133cd7 in ap-south-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-0e4a3a32304cedfaf in ap-southeast-1 Tagged ami ami-0e4a3a32304cedfaf in ap-southeast-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0d3a1269a85394171 for AMI ami-0e4a3a32304cedfaf in ap-southeast-1 Tagged snapshot snap-0d3a1269a85394171 in ap-southeast-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-0bbff6b12ddeda7c3 in ap-southeast-2 Tagged ami ami-0bbff6b12ddeda7c3 in ap-southeast-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0a369f76070e15955 for AMI ami-0bbff6b12ddeda7c3 in ap-southeast-2 Tagged snapshot snap-0a369f76070e15955 in ap-southeast-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-016fcb6ce04d7b7d9 in ca-central-1 Tagged ami ami-016fcb6ce04d7b7d9 in ca-central-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0d1181f0a3f0947cb for AMI ami-016fcb6ce04d7b7d9 in ca-central-1 Tagged snapshot snap-0d1181f0a3f0947cb in ca-central-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-06aa46f98ac220143 in eu-central-1 Tagged ami ami-06aa46f98ac220143 in eu-central-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-044c66a670488129e for AMI ami-06aa46f98ac220143 in eu-central-1 Tagged snapshot snap-044c66a670488129e in eu-central-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-00050c079abc52c85 in eu-west-1 Tagged ami ami-00050c079abc52c85 in eu-west-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0cb75ac14cc2bacef for AMI ami-00050c079abc52c85 in eu-west-1 Tagged snapshot snap-0cb75ac14cc2bacef in eu-west-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-05a5944c1a28d223d in eu-west-2 Tagged ami ami-05a5944c1a28d223d in eu-west-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0391a2048b8c80ea2 for AMI ami-05a5944c1a28d223d in eu-west-2 Tagged snapshot snap-0391a2048b8c80ea2 in eu-west-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-08b4257b37b902e30 in sa-east-1 Tagged ami ami-08b4257b37b902e30 in sa-east-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-05103d108c17c1099 for AMI ami-08b4257b37b902e30 in sa-east-1 Tagged snapshot snap-05103d108c17c1099 in sa-east-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-004f552bba0e5f64f in us-east-1 Tagged ami ami-004f552bba0e5f64f in us-east-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0c32b1bd7d1bb2c89 for AMI ami-004f552bba0e5f64f in us-east-1 Tagged snapshot snap-0c32b1bd7d1bb2c89 in us-east-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-097f74237291abc07 in us-east-2 Tagged ami ami-097f74237291abc07 in us-east-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-03ff1b292a3329900 for AMI ami-097f74237291abc07 in us-east-2 Tagged snapshot snap-03ff1b292a3329900 in us-east-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-0aca2ed5c7b247386 in us-west-1 Tagged ami ami-0aca2ed5c7b247386 in us-west-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0b0424ffed195b731 for AMI ami-0aca2ed5c7b247386 in us-west-1 Tagged snapshot snap-0b0424ffed195b731 in us-west-1 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found AMI ami-089b6143ef0e57f4b in us-west-2 Tagged ami ami-089b6143ef0e57f4b in us-west-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'} Found Snapshot snap-0d4d7720a28535f5a for AMI ami-089b6143ef0e57f4b in us-west-2 Tagged snapshot snap-0d4d7720a28535f5a in us-west-2 with {'Key': 'FedoraGroup', 'Value': 'ga-archives'}
Dne 22. 10. 24 v 10:31 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-02-01
13 AMIs deregistered
I continued with all older than 2024-03-01
48 AMIs deregistered.
Full log is here https://k00.fr/st0dloqb
Dne 23. 10. 24 v 9:33 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-03-01
48 AMIs deregistered.
I continued with all older than 2024-04-01
118 AMIs deregistered.
Full log is here:https://k00.fr/rzk0krtj
Dne 24. 10. 24 v 9:12 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-04-01
118 AMIs deregistered.
I continued with all older than 2024-05-01
156 AMIs deregistered.
Full log is here https://k00.fr/l05angtz
Dne 28. 10. 24 v 9:10 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-05-01
156 AMIs deregistered.
Full log is here https://k00.fr/l05angtz
I continued with all older than 2024-06-01
377 AMIs deregistered
Full log is here https://k00.fr/8o9naz8p
On Tue, 29 Oct 2024 at 03:09, Miroslav Suchý via infrastructure < infrastructure@lists.fedoraproject.org> wrote:
Dne 28. 10. 24 v 9:10 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-05-01
156 AMIs deregistered.
Full log is here https://k00.fr/l05angtz
I continued with all older than 2024-06-01
377 AMIs deregistered
Full log is here https://k00.fr/8o9naz8p
What does that bring the numbers to?
Dne 29. 10. 24 v 12:24 odp. Stephen Smoogen napsal(a):
> I continued with all older than 2024-06-01 377 AMIs deregistered Full log is here https://k00.fr/8o9naz8pWhat does that bring the numbers to?
It brings us down to (me checks the records, and ... what? ...doublecheck...) to 12109 remaining AMIs without FedoraGroup tag.
Full list is here:
https://miroslav.suchy.cz/fedora/untagged-aws-2024-10-29.txt
Dne 29. 10. 24 v 8:09 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-06-01
377 AMIs deregistered
I continued with all older than 2024-07-01
190 AMIs deregistered
Full log is here (now with AMI's name too).
Dne 30. 10. 24 v 10:14 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-07-01
190 AMIs deregistered
I continued with all older than 2024-08-01
100 AMIs deregistered
Full log is here https://k00.fr/0cgxzmar
Dne 31. 10. 24 v 9:17 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-08-01
100 AMIs deregistered
I continued with all older than 2024-09-01
2269 AMIs deregistered.
Full log is here: https://k00.fr/rmcwjq3f
My plan is to continue on Monday with older 2024-10-01 and stop there. And every month delete any AMIs older than one month that does not have tag.
I will wait few weeks to see if I broke someting. If there will be no objection I will then delete the snapshots that were associated with this AMIs. AMI itself cost $0, but the snapshot has a cost.
Dne 01. 11. 24 v 11:49 dop. Miroslav Suchý napsal(a):
I continued with all older than 2024-09-01
2269 AMIs deregistered.
Full log is here: https://k00.fr/rmcwjq3f
My plan is to continue on Monday with older 2024-10-01 and stop there. And every month delete any AMIs older than one month that does not have tag.
I continued with all older than 2024-10-01
6646 AMIs deregistered
Full log is here https://k00.fr/i0qy7784
Remaining AMIs without tag https://miroslav.suchy.cz/fedora/aws-without-tag.txt%C2%A0 About 3k of them.
Now I am really curious what stopped working :)
Dne 04. 11. 24 v 3:50 odp. Miroslav Suchý napsal(a):
I continued with all older than 2024-10-01
6646 AMIs deregistered
Full log is here https://k00.fr/i0qy7784
Remaining AMIs without tag https://miroslav.suchy.cz/fedora/aws-without-tag.txt About 3k of them.
I shorten the time window even more and now I continued with AMIs older than 2025-01-01
2912 AMIs deregistered
Full log is here https://miroslav.suchy.cz/fedora/delete-snapshots-before-2025-01-01.log
There is log of Fedora Cloud AMIs so I opened https://pagure.io/cloud-sig/issue/434
Then there is lines like:
Deregistering AMI ami-0961005d99df284ce CentOS Stream 8 aarch64 in region us-east-2 as it does not have a 'FedoraGroup' tag Deregistering AMI ami-07ee0ec5b0b8c1e43 Fedora-40-image-mode-x86_64 in region us-east-2 as it does not have a 'FedoraGroup' tag
Not sure who is responsible for these.
On Thu, Jan 09, 2025 at 10:23:23AM +0100, Miroslav Suchý via infrastructure wrote:
Dne 04. 11. 24 v 3:50 odp. Miroslav Suchý napsal(a):
I continued with all older than 2024-10-01
6646 AMIs deregistered
Full log is here https://k00.fr/i0qy7784
Remaining AMIs without tag https://miroslav.suchy.cz/fedora/aws-without-tag.txt About 3k of them.
I shorten the time window even more and now I continued with AMIs older than 2025-01-01
2912 AMIs deregistered
Full log is here https://miroslav.suchy.cz/fedora/delete-snapshots-before-2025-01-01.log
There is log of Fedora Cloud AMIs so I opened https://pagure.io/cloud-sig/issue/434
Then there is lines like:
Deregistering AMI ami-0961005d99df284ce CentOS Stream 8 aarch64 in region us-east-2 as it does not have a 'FedoraGroup' tag Deregistering AMI ami-07ee0ec5b0b8c1e43 Fedora-40-image-mode-x86_64 in region us-east-2 as it does not have a 'FedoraGroup' tag
Not sure who is responsible for these.
I would guess CentOS Stream is the centos-stream team. :) Of course stream 8 is EOL now, so it's likely that they are fine with removal.
On image-mode I am not sure. Can you see what user/role created it?
kevin
Howdy,
we reuploaded them again, while EOL, until we can do RHEL8 in public with a developer subscription, our users need it. They should have now the FedoraGroup tag.
Best regards, /M
On Thu, Jan 9, 2025 at 10:43 PM Kevin Fenzi via infrastructure < infrastructure@lists.fedoraproject.org> wrote:
On Thu, Jan 09, 2025 at 10:23:23AM +0100, Miroslav Suchý via infrastructure wrote:
Dne 04. 11. 24 v 3:50 odp. Miroslav Suchý napsal(a):
I continued with all older than 2024-10-01
6646 AMIs deregistered
Full log is here https://k00.fr/i0qy7784
Remaining AMIs without tag
https://miroslav.suchy.cz/fedora/aws-without-tag.txt About 3k of them.
I shorten the time window even more and now I continued with AMIs older
than 2025-01-01
2912 AMIs deregistered
Full log is here
https://miroslav.suchy.cz/fedora/delete-snapshots-before-2025-01-01.log
There is log of Fedora Cloud AMIs so I opened
https://pagure.io/cloud-sig/issue/434
Then there is lines like:
Deregistering AMI ami-0961005d99df284ce CentOS Stream 8 aarch64 in
region us-east-2 as it does not have a 'FedoraGroup' tag
Deregistering AMI ami-07ee0ec5b0b8c1e43 Fedora-40-image-mode-x86_64 in
region us-east-2 as it does not have a 'FedoraGroup' tag
Not sure who is responsible for these.
I would guess CentOS Stream is the centos-stream team. :) Of course stream 8 is EOL now, so it's likely that they are fine with removal.
On image-mode I am not sure. Can you see what user/role created it?
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org 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@lists.fedorapro... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
And we will do the same with image mode, all those were from us :)
Thanks, /M
On Fri, Jan 10, 2025 at 12:15 AM Miroslav Vadkerti mvadkert@redhat.com wrote:
Howdy,
we reuploaded them again, while EOL, until we can do RHEL8 in public with a developer subscription, our users need it. They should have now the FedoraGroup tag.
Best regards, /M
On Thu, Jan 9, 2025 at 10:43 PM Kevin Fenzi via infrastructure < infrastructure@lists.fedoraproject.org> wrote:
On Thu, Jan 09, 2025 at 10:23:23AM +0100, Miroslav Suchý via infrastructure wrote:
Dne 04. 11. 24 v 3:50 odp. Miroslav Suchý napsal(a):
I continued with all older than 2024-10-01
6646 AMIs deregistered
Full log is here https://k00.fr/i0qy7784
Remaining AMIs without tag
https://miroslav.suchy.cz/fedora/aws-without-tag.txt About 3k of them.
I shorten the time window even more and now I continued with AMIs older
than 2025-01-01
2912 AMIs deregistered
Full log is here
https://miroslav.suchy.cz/fedora/delete-snapshots-before-2025-01-01.log
There is log of Fedora Cloud AMIs so I opened
https://pagure.io/cloud-sig/issue/434
Then there is lines like:
Deregistering AMI ami-0961005d99df284ce CentOS Stream 8 aarch64 in
region us-east-2 as it does not have a 'FedoraGroup' tag
Deregistering AMI ami-07ee0ec5b0b8c1e43 Fedora-40-image-mode-x86_64 in
region us-east-2 as it does not have a 'FedoraGroup' tag
Not sure who is responsible for these.
I would guess CentOS Stream is the centos-stream team. :) Of course stream 8 is EOL now, so it's likely that they are fine with removal.
On image-mode I am not sure. Can you see what user/role created it?
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org 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@lists.fedorapro... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- 🧑🔧 Miroslav Vadkerti :: Senior Principal QE :: Testing Farm / Linux QE 🎩 Red Hat Slack :: mvadkert :: #testing-farm #tmt 📱 Fedora Matrix :: mvadkert :: #Fedora CI 🌍️ Remote Czech Republic :: Red Hat Czech s.r.o
infrastructure@lists.fedoraproject.org