Fedora 40 beta freeze now in effect
by Kevin Fenzi
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
2 weeks, 6 days
Deleting old AMIs in AWS
by Miroslav Suchý
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.
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
3 weeks, 3 days
How to retreive a file from an old VM?
by Aurélien Bompard
Hey folks!
Yesterday the os-control01.stg machine was reinstalled as RHEL9.
Unfortunately there was a script on there that I forgot to backup. I
would like, if possible, to retreive it.
The old VM disk is still on the VM server as
/dev/vg_guests/os-control01.stg.iad2.fedoraproject.org-el7.
I tried to naively mount it but it's a block device, not a partition. I
tried to mount it with the offset that fdisk gives me for the root
partition:
# mount -o offset=$((512*5244928)),other,options,here
/dev/vg_guests/os-control01.stg.iad2.fedoraproject.org-el7 /mnt/tmpextract/
mount: /mnt/tmpextract: unknown filesystem type 'LVM2_member'.
But as you can see it's an LVM volume so I can't use it directly.
I don't want to risk polluting the main LVM setup on the machine, so if
know of a way to read files from old VM disks I'm interested.
The file I'd like to get is /usr/local/bin/jobs-summary. It's not a huge
loss but it's still a few hours of work.
And if we find a good way of doing this we may want to add it to our
SOPs in case it happens again in the future :-)
Thanks!
Aurélien
4 weeks
Freeze Break request: update kernel on buildhw-x86*
by Kevin Fenzi
Hey everyone.
The koji builders are currently using 6.7.6-200.fc39, which is mostly
fine, but on i386 builds there's some kind of memory issue and (some)
builds run out of memory and fail. ;(
See: https://pagure.io/fedora-infrastructure/issue/11775
I'd like to upgrade the buildhw-x86* builders to the latest 6.8.x
kernel. We tried this in staging and it let the build complete fine.
We only need to do those builders because those are the only ones in the
'heavybuilder' channel that webkitgtk builds use, and the x86 ones are
the only ones that do i386 builds. ;)
We could I suppose update all the buildvm-x86* also in case there are
other packages we don't know about that are affected, but then the
change is wider.
So, +1s? Thoughts?
kevin
1 month, 2 weeks
Freeze break request: update pungi on compose hosts
by Kevin Fenzi
We need a newer pungi version that adds support for kiwi and has changes
for osbuild arm minimal. These are both things we are trying to land for
beta.
There's a 4.6.2 release upstream that we need.
So, I'd like to build this for f39 (which our compose hosts are) and
update them.
If something goes very wrong we should be able to just downgrade back to
the previous version.
+1s?
kevin
1 month, 2 weeks