infrastructure February 2024

infrastructure@lists.fedoraproject.org

6 participants
10 discussions

Fedora 40 beta freeze now in effect
by Kevin Fenzi 06 Apr '24

06 Apr '24

Greetings. We are now in the infrastructure freeze leading up to the Fedora 40 Beta release. This is a pre release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 40 Beta when it's available. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone https://pagure.io/fedora-infra/ansible.git ansible/scripts/freezelist -i inventory Any hosts listed as freezes is frozen until 2024-03-12 (or later if release slips). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list or a pull request for review. Thanks, Kevin

3 8

Planned Outage - koji upgrade - 2024-02-21 21:00 UTC
by Kevin Fenzi 20 Feb '24

20 Feb '24

Planned Outage - koji upgrade - 2024-02-21 21:00 UTC There will be an outage starting at 2024-02-21 21:00 UTC, which will last approximately 3 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-21 21:00UTC' Reason for outage: koji will be upgraded to 1.34.0, which requires a schema update that touches many rows. We estimate this will take about 45minutes to complete and during that time, koji will be completely offline. Package maintainers are advised to not start any long term builds before the outage. Affected Services: koji bodhi Ticket Link: https://pagure.io/fedora-infrastructure/issue/11778 Please join #fedora-admin or #fedora-noc on irc.libera.chat or #admin:fedoraproject.org / #noc:fedoraproject.org on matrix. Please add comments to the ticket for this outage above. Updated status for this outage may be available at https://www.fedorastatus.org/

1 0

Where can I find "Packages Restricting Arches" script.
by Sandro 14 Feb '24

14 Feb '24

Hi, Some script running on pkgs01.iad2.fedoraproject.org sends a report titled "Packages Restricting Arches" to arch-excludes(a)lists.fp.o every night (between 04:00 and 05:00 UTC)[1]. I was wondering where I could find that script. The report appears to be for ExclusiveArch only. It would help me if I could generate a similar report for ExcludeArch. [1] https://lists.fedoraproject.org/archives/list/arch-excludes@lists.fedorapro… Cheers, -- Sandro FAS: gui1ty Matrix: Penguinpee Elsewhere: [Pp]enguinpee

2 3

AWS cleanup - what to delete next?
by Miroslav Suchý 12 Feb '24

12 Feb '24

Yesterday I finally deleted all Fedora-AtomicHost AMIs and associated snapshots (it took whole night to finish). This time, I know we have to start with AMIs first (and only then delete snapshots). Where I can continue witht the cleanup? There is several dozen thousand of AMIs. At the end of this email I will give random sample from the list. I am very afraid of deleting something that is still currently in use and that is somewhere listed as golden image. Or we do not care about anything but images of stable Fedoras and everything that matches 'Fedora.*-X-.*' where X is number bellow < 38? Miroslav * ami-26c3b846 Fedora-Cloud-Base-24-20160601.n.0.x86_64-us-west-1-HVM-standard-0 * ami-05fd9470f34e60fdc Fedora-Cloud-Base-39-1.1.aarch64-hvm-us-west-1-gp3-0 * ami-062b2a2f58fdaf72f fedora-coreos-36.20220820.2.0-aarch64 * ami-f4bbff94 Fedora-Cloud-Atomic-23-20160626.x86_64-us-west-1-HVM-standard-0 * ami-31da9d51 Fedora-Atomic-24-20160706.0.x86_64-us-west-1-HVM-gp2-0 * ami-0bd20e7557d7bdbb6 Fedora-Cloud-Base-29-20190726.0.aarch64-hvm-us-west-1-standard-0 * ami-20a3a640 Fedora-Atomic-27-20171211.0.x86_64-us-west-1-HVM-gp2-0 * ami-fab2c59a Fedora-Cloud-Base-23-20160127.2.x86_64-us-west-1-PV-standard-0 * ami-981812f8 Fedora-Cloud-Base-27-20180303.0.x86_64-us-west-1-HVM-gp2-0 * ami-2134cb65 Fedora-Cloud-Base-23_Alpha-20150806.2.x86_64-us-west-1-HVM-gp2-0 * ami-0b8037b9dcf49e74e fedora-coreos-39.20231101.1.0-x86_64 * ami-312c0f51 Fedora-Atomic-25-20170601.0.x86_64-us-west-1-HVM-gp2-0 * ami-bacaccda Fedora-Atomic-26-20171226.0.x86_64-us-west-1-HVM-gp2-0 * ami-0b363a6b Fedora-Cloud-Base-26-20180129.0.x86_64-us-west-1-HVM-gp2-0 * ami-b2909cd2 Fedora-Atomic-Rawhide-20180131.n.0.x86_64-us-west-1-HVM-standard-0 * ami-04165988107e37bff Fedora-Cloud-Base-28-20190510.0.x86_64-hvm-us-west-1-standard-0 * ami-0b4577fc26dfa0a41 fedora-coreos-38.20230722.1.0-aarch64 * ami-0f46b6ee06ec9518a fedora-coreos-36.20220505.2.0-x86_64 * ami-3a30315a Fedora-Cloud-Base-26-20180101.0.x86_64-us-west-1-HVM-standard-0 * ami-089d45c0dde166fe0 Fedora-Cloud-Base-30-20190728.0.aarch64-hvm-us-west-1-gp2-0 * ami-eb84ba8b Fedora-Atomic-Rawhide-20171112.n.0.x86_64-us-west-1-HVM-standard-0 * ami-05254bd86175b9023 fedora-coreos-35.20220424.3.0-x86_64 * ami-f5ecdc95 Fedora-Atomic-26-20171001.0.x86_64-us-west-1-HVM-gp2-0 * ami-c2ab83a2 Fedora-Cloud-Base-25-20170802.0.x86_64-us-west-1-HVM-standard-0 * ami-df3367bf Fedora-Atomic-25-20161121.0.x86_64-us-west-1-HVM-standard-0 * ami-0419c7c8be07bf733 Fedora-Cloud-Base-30-20190419.n.0.x86_64-hvm-us-west-1-standard-0 * ami-c20612a2 Fedora-Atomic-27-20180314.0.x86_64-us-west-1-HVM-standard-0 * ami-a4192ec4 Fedora-Atomic-26-20170908.0.x86_64-us-west-1-HVM-gp2-0 * ami-9dc1f1fd Fedora-Cloud-Base-27-20171001.n.2.x86_64-us-west-1-HVM-gp2-0 * ami-d90255b9 Fedora-Cloud-Base-25-20161130.1.x86_64-us-west-1-PV-gp2-0 * ami-72747712 Fedora-Cloud-Base-Rawhide-20180110.n.0.x86_64-us-west-1-HVM-gp2-0 * ami-885052e8 Fedora-Cloud-Base-Rawhide-20180115.n.0.x86_64-us-west-1-HVM-gp2-0 * ami-5f5c643f Fedora-Cloud-Base-Rawhide-20171118.n.1.x86_64-us-west-1-HVM-gp2-0 * ami-4b115a2b Fedora-Cloud-Base-24-20161021.0.x86_64-us-west-1-PV-standard-0 * ami-fa40379a Fedora-Cloud-Base-23-20160127.1.x86_64-us-west-1-HVM-standard-0 * ami-04aacbcff5e34df3b Fedora-Cloud-Base-32-20200605.0.x86_64-hvm-us-west-1-gp2-0 * ami-04f2a5462112fc48f fedora-coreos-36.20220820.3.0-x86_64 * ami-9c5a20fc Fedora-Cloud-Base-23-20160605.x86_64-us-west-1-HVM-gp2-0 * ami-50c5f530 Fedora-Cloud-Base-25-20171002.0.x86_64-us-west-1-PV-standard-0 * ami-db6f6fbb Fedora-Atomic-Rawhide-20180105.n.0.x86_64-us-west-1-HVM-gp2-0 * ami-06ce8f3b14afca272 Fedora-Cloud-Base-30-20190323.n.0.aarch64-hvm-us-west-1-standard-0 * ami-0fc1ba6f Fedora-Atomic-24-20160601.n.0.x86_64-us-west-1-HVM-gp2-0 * ami-6c54550c Fedora-Atomic-Rawhide-20171228.n.0.x86_64-us-west-1-HVM-standard-0 * ami-a2591ac2 Fedora-Cloud-Base-24-20160809.0.x86_64-us-west-1-PV-standard-0 * ami-b31743d3 Fedora-Cloud-Base-25-20161119.3.x86_64-us-west-1-PV-standard-0 * ami-df4f6cbf Fedora-Atomic-26_Beta-1.3.x86_64-us-west-1-HVM-standard-0 * ami-e790d387 Fedora-Cloud-Base-24-20160811.0.x86_64-us-west-1-PV-standard-0 * ami-b3ddc9d3 Fedora-Cloud-Base-27-20180315.0.x86_64-us-west-1-HVM-gp2-0 * ami-273c7947 Fedora-Cloud-Base-23-20160613.x86_64-us-west-1-PV-gp2-0 * ami-594c1b39 Fedora-Cloud-Base-24-20161203.0.x86_64-us-west-1-PV-standard-0 * ami-203a3e40 Fedora-Cloud-Base-27-20171214.0.x86_64-us-west-1-HVM-gp2-0 * ami-b3b388d3 Fedora-Atomic-27-20171129.0.x86_64-us-west-1-HVM-standard-0 * ami-d1e1f0b1 Fedora-Cloud-Base-28-20180331.n.1.x86_64-us-west-1-HVM-gp2-0 * ami-063bd28aeead1fb4e Fedora-Cloud-Base-30-20190509.0.x86_64-hvm-us-west-1-gp2-0 * ami-43464723 Fedora-Atomic-26-20171229.0.x86_64-us-west-1-HVM-standard-0 * ami-6b38160b Fedora-Cloud-Base-24-20170713.0.x86_64-us-west-1-PV-gp2-0 * ami-012a0519ada69f3f9 Fedora-Cloud-Base-39-1.1.x86_64-hvm-us-west-1-gp3-0 * ami-04ee6790c93aa9851 Fedora-Cloud-Base-Rawhide-20190506.n.1.x86_64-hvm-us-west-1-gp2-0 * ami-0417e1efaaf6a4fa0 Fedora-Cloud-Base-29-20190703.0.x86_64-hvm-us-west-1-gp2-0 * ami-1e665f7e Fedora-Atomic-Rawhide-20171113.n.0.x86_64-us-west-1-HVM-gp2-0 * ami-5b5b1c3b Fedora-Cloud-Base-24-20160701.0.x86_64-us-west-1-PV-standard-0 * ami-0310f1a5d2854c18d fedora-coreos-37.20230218.2.0-x86_64 * ami-7cba961c Fedora-Cloud-Base-25-20170630.0.x86_64-us-west-1-HVM-gp2-0 * ami-b20204d2 Fedora-Cloud-Base-26-20171224.0.x86_64-us-west-1-HVM-gp2-0 * ami-01f5acf38212d009a fedora-coreos-38.20230430.1.0-aarch64 * ami-8f023fef Fedora-Atomic-26-20171021.0.x86_64-us-west-1-HVM-gp2-0 * ami-e28da282 Fedora-Cloud-Base-25-20170709.0.x86_64-us-west-1-PV-gp2-0 * ami-0dd31964c3588f1be fedora-coreos-37.20220918.1.1-aarch64 * ami-5ea6e13e Fedora-Atomic-24-20160704.0.x86_64-us-west-1-HVM-gp2-0 * ami-0ea8cdcd48ebca78c fedora-coreos-38.20230430.2.1-x86_64 * ami-3c10555c Fedora-Cloud-Base-24-1.1.x86_64-us-west-1-HVM-standard-0 * ami-7f71661f Fedora-Cloud-Base-26-20180318.0.x86_64-us-west-1-HVM-standard-0 * ami-c37b46a3 Fedora-Cloud-Base-25-20171018.0.x86_64-us-west-1-PV-gp2-0 * ami-bf7343df Fedora-Atomic-26-20170927.0.x86_64-us-west-1-HVM-gp2-0 * ami-dc9da0bc Fedora-Cloud-Base-26-20171024.0.x86_64-us-west-1-HVM-gp2-0 * ami-02fb010ee671c467d fedora-coreos-35.20220103.2.0-x86_64 * ami-38291258 Fedora-Cloud-Base-Rawhide-20171126.n.0.x86_64-us-west-1-HVM-standard-0 * ami-847f30e4 Fedora-Cloud-Base-24-20160916.0.x86_64-us-west-1-HVM-standard-0 * ami-dc180fbc Fedora-Cloud-Base-26-20180319.0.x86_64-us-west-1-HVM-standard-0 * ami-07b653d82033f9681 fedora-coreos-39.20231002.1.1-x86_64 * ami-4c64312c Fedora-Cloud-Base-24-20161114.0.x86_64-us-west-1-PV-gp2-0 * ami-0920ba29d7e90437f Fedora-Cloud-Base-31-20191112.0.aarch64-hvm-us-west-1-standard-0 * ami-0bb6684d9f09744e3 Fedora-Cloud-Base-39-20240206.0.aarch64-hvm-us-west-1-gp3-0 * ami-c46767a4 Fedora-Cloud-Base-27-20180105.3.x86_64-us-west-1-HVM-standard-0 * ami-050ea365519bc0db0 Fedora-Cloud-Base-30-20190322.n.0.aarch64-hvm-us-west-1-standard-0 * ami-088cebf2442fc4894 fedora-coreos-38.20230609.1.0-aarch64 * ami-3993d059 Fedora-Atomic-24-20160811.0.x86_64-us-west-1-HVM-gp2-0 * ami-59226639 Fedora-Cloud-Base-23-20160621.x86_64-us-west-1-PV-standard-0 * ami-f8246298 Fedora-Atomic-24-20160708.0.x86_64-us-west-1-HVM-standard-0 * ami-e4c9b384 Fedora-Atomic-24-20160610.n.0.x86_64-us-west-1-HVM-standard-0 * ami-05a7604cc4aabbd2a Fedora-Cloud-Base-30-20190406.n.1.x86_64-hvm-us-west-1-gp2-0 * ami-0d72747c5ac532500 Fedora-Cloud-Base-Rawhide-20240205.n.0.x86_64-hvm-us-west-1-gp3-0 * ami-f6fbfb96 Fedora-Cloud-Base-Rawhide-20180108.n.0.x86_64-us-west-1-HVM-standard-0 * ami-4c152b2c Fedora-Cloud-Base-26-20171109.0.x86_64-us-west-1-HVM-gp2-0 * ami-066b5c323aff4ece7 Fedora-Cloud-Base-30-20190515.0.x86_64-hvm-us-west-1-gp2-0 * ami-0ce1ef8681128ac17 CentOS Stream 8 aarch64 20240101 * ami-68ede108 Fedora-Cloud-Base-27-20180130.0.x86_64-us-west-1-HVM-gp2-0 * ami-71f0e311 Fedora-Cloud-Base-28-20180410.n.1.x86_64-paravirtual-us-west-1-standard-0 * ami-0d23bcbbbc029d3cd fedora-coreos-34.20210418.1.0 * ami-c63c17a6 Fedora-Cloud-Base-24-20170807.0.x86_64-us-west-1-HVM-gp2-0 * ami-00fcca60 Fedora-Atomic-25-20170917.0.x86_64-us-west-1-HVM-standard-0 * ami-07d79dbf8e2b414a3 Fedora-Cloud-Base-32-20200606.0.x86_64-hvm-us-west-1-standard-0 * ami-094c894d Fedora-Cloud-Base-23_Beta-20150915.x86_64-us-west-1-HVM-standard-1 * ami-428db622 Fedora-Cloud-Base-27-20171130.0.x86_64-us-west-1-HVM-gp2-0 * ami-d797b8b7 Fedora-Cloud-Base-25-20170710.0.x86_64-us-west-1-PV-gp2-0 * ami-04426964 Fedora-Cloud-Base-24-20170805.0.x86_64-us-west-1-HVM-standard-0 -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

3 6

Different owner of some Fedora-Cloud-Base images in AWS?
by Miroslav Suchý 12 Feb '24

12 Feb '24

I was wondering why I cannot tag some images in AWS and I found that some GA images in AWS have different owner. I.e. all our images has Owner account ID 125523088429 But e.g. ami-0e4e634d022c1a3f8 in ap-southeast-4 region has owner id 569228561889. There are more such cases, but it seems quite random. To see this AMI in WebUI you have to switch from "AMIs owned by me" to "Public images". Is this expected? Is this some malicious thing? -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

3 2

Re: FYI: removal of bastion server in DNSBL spam.dnsbl.anonmails.de requested
by Stephen Smoogen 12 Feb '24

12 Feb '24

On Mon, 12 Feb 2024 at 06:12, Marius Schwarz <fedoradev(a)cloud-foo.de> wrote: > Hi, > > as die Infrastructure ML did not react ( or could not react ;) ), I > requested the removal at that antispam blacklist. > > I did not see any email to the infrastructure list about this so I am wondering if your email (and other emails) have gotten trashed? Did you open a ticket on this at https://pagure.io/fedora-infrastructure/ already? There is another email issue that was listed there earlier today but I don't know if they are related. > 2024-02-11 05:20:16 H=bastion-iad01.fedoraproject.org > (bastion.fedoraproject.org) [38.145.60.11] > X=TLS1.3:TLS_AES_256_GCM_SHA384:256 CV=no > F=<devel-bounces(a)lists.fedoraproject.org> rejected RCPT > <fedoradev(a)cloud-foo.de>: found in spam.dnsbl.anonmails.de > > I hope it gets removed soon. > > best regards, > Marius Schwarz > -- > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

2 1

HEADS UP - deletion of Fedora Atomic Hosts AMIs
by Miroslav Suchý 09 Feb '24

09 Feb '24

As mentioned in previous thread - I plan to delete from AWS all Fedora Atomic Hosts and related snapshots. Atomic Host EOLed at 2019 and we have the images stored elsewhere too. To protect Christmas calm period. I will delete is no sooner than 2024-01-09. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

2 2

Not tagged resource in AWS
by Miroslav Suchý 07 Feb '24

07 Feb '24

This is a resource from AWS that does not have propper tag: Region: eu-west-1 Volumes - [id name (attached to instance, owner)]: * vol-0e5efafe67ed944ad N/A (apps-containerization, N/A) Can the owner please tag (or delete) it? -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

2 1

AWS usage per group (Janurary)
by Miroslav Suchý 05 Feb '24

05 Feb '24

Here comes January edition of resources running in AWS. It's a snapshot of resources running today. FedoraGroup: garbage-collector Region: ap-southeast-1 Volume Type: standard - Total Size: 6 GiB FedoraGroup: min Region: eu-central-1 Instance Type: t3.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 1000 GiB FedoraGroup: respins Region: us-east-1 Volume Type: gp3 - Total Size: 500 GiB FedoraGroup: copr Region: us-east-1 Instance Type: t3a.medium - Count: 4 Instance Type: r5a.large - Count: 1 Instance Type: t3a.small - Count: 1 Instance Type: r7a.xlarge - Count: 1 Instance Type: c7a.4xlarge - Count: 1 Instance Type: m5a.4xlarge - Count: 1 Instance Type: t3a.2xlarge - Count: 1 Instance Type: c7i.xlarge - Count: 25 Instance Type: c7a.large - Count: 1 Instance Type: c7g.xlarge - Count: 36 Volume Type: st1 - Total Size: 7000 GiB Volume Type: gp3 - Total Size: 7484 GiB Volume Type: io2 - Total Size: 20 GiB Volume Type: sc1 - Total Size: 81652 GiB FedoraGroup: centos-stream-osci Region: ca-central-1 Instance Type: m5d.large - Count: 5 Instance Type: t2.micro - Count: 1 Volume Type: gp3 - Total Size: 36 GiB FedoraGroup: abrt Region: us-east-1 Instance Type: t3a.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 10 GiB FedoraGroup: centos Region: ap-south-1 Instance Type: t3.2xlarge - Count: 3 Instance Type: t3.large - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4570 GiB Region: eu-central-1 Instance Type: t2.small - Count: 1 Instance Type: t2.large - Count: 2 Instance Type: r5b.8xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Instance Type: t3.xlarge - Count: 1 Volume Type: gp3 - Total Size: 13200 GiB Region: us-west-2 Instance Type: m6i.2xlarge - Count: 2 Instance Type: t3.small - Count: 1 Instance Type: t3.xlarge - Count: 1 Volume Type: gp3 - Total Size: 13145 GiB Region: af-south-1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4050 GiB Region: eu-west-3 Instance Type: t2.large - Count: 2 Instance Type: t2.2xlarge - Count: 1 Instance Type: t3a.xlarge - Count: 1 Instance Type: t2.small - Count: 2 Instance Type: t3.xlarge - Count: 1 Instance Type: t3.large - Count: 1 Volume Type: gp3 - Total Size: 2917 GiB Region: eu-west-2 Instance Type: t2.small - Count: 1 Instance Type: t2.large - Count: 1 Instance Type: t3a.large - Count: 2 Instance Type: r5a.8xlarge - Count: 1 Instance Type: t3.large - Count: 2 Instance Type: t3.xlarge - Count: 1 Instance Type: t2.medium - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 26320 GiB Region: eu-west-1 Instance Type: t2.medium - Count: 4 Instance Type: t2.xlarge - Count: 3 Instance Type: t2.large - Count: 1 Instance Type: t2.small - Count: 2 Instance Type: t3.large - Count: 1 Instance Type: t3.medium - Count: 2 Volume Type: gp3 - Total Size: 584 GiB Region: ap-northeast-1 Instance Type: c6g.2xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 8070 GiB Region: sa-east-1 Instance Type: c6g.4xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4250 GiB Region: ap-southeast-1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4050 GiB Region: ap-southeast-2 Instance Type: m6i.2xlarge - Count: 2 Volume Type: gp3 - Total Size: 8100 GiB Region: us-east-1 Instance Type: t3.xlarge - Count: 2 Volume Type: gp3 - Total Size: 26350 GiB Region: us-east-2 Instance Type: t2.2xlarge - Count: 1 Instance Type: m5a.2xlarge - Count: 1 Instance Type: t3.xlarge - Count: 4 Instance Type: t3a.large - Count: 1 Instance Type: m6i.2xlarge - Count: 2 Instance Type: t2.large - Count: 2 Instance Type: t3.large - Count: 1 Instance Type: m4.2xlarge - Count: 1 Instance Type: t3.small - Count: 1 Instance Type: t3.medium - Count: 1 Volume Type: gp3 - Total Size: 46090 GiB FedoraGroup: ci Region: us-east-1 Instance Type: c5.2xlarge - Count: 3 Volume Type: gp3 - Total Size: 1540 GiB Region: us-east-2 Instance Type: m5a.4xlarge - Count: 1 Instance Type: r5.large - Count: 4 Instance Type: i3.2xlarge - Count: 5 Instance Type: r5.xlarge - Count: 2 Instance Type: c6g.large - Count: 5 Instance Type: c6g.xlarge - Count: 1 Instance Type: c6a.large - Count: 74 Instance Type: c6a.xlarge - Count: 1 Volume Type: gp3 - Total Size: 11598 GiB Volume Type: gp2 - Total Size: 1500 GiB FedoraGroup: centos-stream-build Region: us-east-2 Instance Type: t2.micro - Count: 1 FedoraGroup: infra Region: ap-south-1 Instance Type: c5d.xlarge - Count: 1 Volume Type: gp3 - Total Size: 8 GiB Region: eu-central-1 Instance Type: c5d.xlarge - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Instance Type: m5.xlarge - Count: 1 Instance Type: m6gd.4xlarge - Count: 1 Volume Type: gp3 - Total Size: 16223 GiB Region: us-west-1 Instance Type: t3.medium - Count: 1 Volume Type: gp3 - Total Size: 40 GiB Region: us-west-2 Instance Type: m5.large - Count: 4 Instance Type: m6g.large - Count: 1 Instance Type: t3.large - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Instance Type: c6gd.xlarge - Count: 1 Volume Type: standard - Total Size: 100 GiB Volume Type: gp3 - Total Size: 900 GiB Region: af-south-1 Instance Type: c5d.xlarge - Count: 2 Volume Type: gp3 - Total Size: 25 GiB Region: eu-west-2 Instance Type: c5d.xlarge - Count: 1 Volume Type: gp3 - Total Size: 20 GiB Region: eu-west-1 Instance Type: m4.10xlarge - Count: 1 Region: ap-northeast-2 Instance Type: c5n.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 196 GiB Region: sa-east-1 Instance Type: c5.2xlarge - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 200 GiB Region: ap-southeast-1 Instance Type: c5d.xlarge - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 108 GiB Region: us-east-1 Instance Type: t3.medium - Count: 1 Instance Type: t3.small - Count: 1 Instance Type: c5.xlarge - Count: 2 Instance Type: t2.medium - Count: 2 Instance Type: c5.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 330 GiB Region: us-east-2 Instance Type: c5d.large - Count: 1 Instance Type: t2.micro - Count: 1 Instance Type: t3.medium - Count: 1 Volume Type: gp3 - Total Size: 63 GiB -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

1 0

Planned Outage - server updates - 2024-02-07 22:00 UTC
by Kevin Fenzi 05 Feb '24

05 Feb '24

There will be an outage starting at 2024-02-07 22:00UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-07 22:00UTC' Reason for outage: We will be applying updates and rebooting servers. No one service should be down long, but may be up and down in the outage window. Additionally, as time permits we will be doing the following additional work: - resizing disks on database servers - moving some database servers to rhel9 and newer postgresql - applying some firmware updates Affected Services: Most services will be affected for a short time, but end user facing services (mirrorlists, websites) should not be affected. Ticket Link: https://pagure.io/fedora-infrastructure/issue/11752 Please join #fedora-admin or #fedora-noc on irc.libera.chat or #admin:fedoraproject.org / #noc:fedoraproject.org on matrix. Please add comments to the ticket for this outage above. Updated status for this outage may be available at https://www.fedorastatus.org/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure February 2024