Originally published at: Infra and RelEng Update – Week 31 2024 – Fedora Community Blog
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contains updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: – 29 July – 02 August, 2024
Infrastructure & Release Engineering
The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues
Fedora Infra
- In progress:
- rhel7 EOL
- Migration of registry.fedoraproject.org to quay.io
- add monitoring for dnf countme
- Replace Nagios with Zabbix in Fedora Infrastructure
- notifications do not notify
- PDC retirement
- Move from iptables to firewalld
- Update compose hosts to get latest pungi release (4.6.0)
- Deploy new sign hardware/software
- Commits don’t end up on the scm-commits list
- Create monitoring tool for rabbitmq certificates
- Private mirror check-in with mirrormanager fails
- rhel9 adoption
- Private mirror check-in with mirrormanager fails
- EPEL minor version archive repos in MirrorManager
- Cleaning script for communishift
- Grant additional permissions to the fedimg AWS role
- fedmsg -> fedora-messaging migration tracker
- rhel7 EOL – github2fedmsg
- rhel7 EOL – Fedimg
- COPR cannot pull git repo from fedorapeople
- Searching mailing list archives does not work
- Feature / Change request: make the Fedora bugzilla more accessible
- AWS: support creating S3 buckets
- AWS: Support adding elastic IPs
- Moderating mailing list viewing message shows “This held message has been lost.”
- release-monitoring.org crawlers seem to not be running since ~June 26
- buildhw-a64 01,02,19,20,21,22,23,24 not booting
- STG Bugzilla doesn’t send messages to STG fedora-messaging
- Support allocation dedicated hosts for Testing Farm
- vmhost-x86-copr01.rdu-cc.fedoraproject.org DOWN
- Can’t login to pagure.io/src.fedoraproject.org/COPR
- OIDC request for Konflux cluster for fedora
- Add yselkowitz to list to notify when ELN builds fail
- Upcoming: Redirect flocktofedora.org to fedoraproject.org/flock
- releng Bot Unable to Process SCM Requests
- httpd 2.4.61 causing issue in fedora infrastructure
- Done:
- How do I set up FAS login for discussion.stg.fedoraproject.org?
- Please don’t periodically delete communishift-fedora-review-service
- Please don’t periodically delete communishift-log-detective
- RFR: EC2 VM with a GPU for logdetective
- fedora-users spam
- Can’t login to pagure.io/src.fedoraproject.org/COPR
- create communishift-forgejo for trying out purposes
- koji fedora-messaging plugin issues
- OIDC request for Konflux cluster for fedora
- Create communishift-gitlabce for trying out purposes
- Redirect Fedora Podcast URL to Fireside
- New site with rsync only targets cannnot be added to the mirror network
- Spam in AskFedora
- <username>.fedorapeople.org can’t be visited
- Create #metrics:fedoraproject.org address for #telemetry:gnome.org
- Spam account in AskFedora
- chromium build error on f40 (aarch64) – ninja: fatal: posix_spawn: Resource temporarily unavailable
- all chromium builds for x86_64 in wait state
- Spam on Fedora Users list
- make tflink sponsor for pytorch-sig group
CentOS Infra including CentOS CI
- In progress:
- Done:
Release Engineering
- In progress:
- Packages that fail to build SRPM are not reported during the mass rebuild bugzillas
- i686 builders need to use 32-bit inode numbers
- When orphaning packages, keep the original owner as co-maintainer
- Use an automated script to control checksums of compose images
- Create an ansible playbook to do the mass-branching
- Package retirements are broken in rawhide
- Implement checks on package retirements
- Update bootloader components assignee to “Bootloader Engineering Team”for Improved collaboration
- Cleaning old stuff from koji composes directories
- Untag containers-common-0.57.1-6.fc40
- Renaming distribution media for Fedora Server
- Remove PDC from package retirement process
- Fix tokens for ftbfs_weekly_reminder. Script
- Fedora-34-Beta .composeinfo file
- Publish x86_64/aarch64 containers to the new AWS container repo
- Update block_retired.py to use bodhi api
- orphan-all-packages.py should remove bugzilla_contact entries from fedora-scm-requests as well
- unmaintained bot account: dummy-test-package-gloster gating pipeline tests broken
- Drop modularity from EPEL8.
- Some (?) retired packages not actually getting retired since ~2 days ago
- Retire golang-github-src-d-gcfg
- Investigate and untag packages that failed gating but were merged in via mass rebuild
- a few mass rebuild bumps failed to git push – script should retry or error
- Investigate and untag packages that failed gating but were merged in via mass rebuild
- Done:
- [F41 Release Process] FTBFS Bug filing for rawhide
- create EPEL 10.0 release in bodhi
- python-hiredis acci
- dentally had tar ball added to git on new import package
- Missing i686 package
- Accidentally created packit branch for rpms/mkosi
- Grant yselkowitz edit-tag permission for eln-build
- Fedora 41 Mass Rebuild Tracker
- Stalled EPEL package: python-anyjson
- Retirement of python-pynose not fully processed
- F41 Self-Contained Change: LXQt 2.0
- Stalled EPEL Package: physfs
- Revert changes to rpms/stgit epel9 branch
- Unretire python-googleapis-common-protos
- Unretire aquamarine
- Unorphan buildstream
- Unretire rust-average
- Package rust-web-time not in list for tag f41-updates-candidate
- lorax-templates-rhel is blocked in ELN
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux (SL) and Oracle Linux (OL).
Updates
- Fixed packaging issue with python3-botan2
- Add instructions for requesting EPEL branches to the Fedora Package Maintenance Guide
- Add EPEL 10 key to bodhi’s pungi template
- Create EPEL 10.0 release in bodhi
- Bootstrapped initial fedpkg-minimal for EPEL 10.0
- Add expected branch SLAs for EPEL 10 branches
- Update owner-sync-pagure.j2 to work with EPEL 10
- Update owner-sync-pagure.j2 to work with EPEL 10, second attempt
Community Design
CPE has few members that are working as part of Community Design Team. This team is working on anything related to design in Fedora Community.
Updates
- Emma @ Flock and Madeline on PTO next week 🙂
- Flock:
- A/V template for stream
- Badges for Flock and Mentor Summit
- Podman Desktop:
- Working on UI documentation
- More light mode theme refinement
ARC Investigations
The ARC (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.
- Progress Overview:
- Akashdeep Dhar has completed the GitLab side of the comparison; the findings are now available on the spreadsheet for review.
- Testing of the Forgejo instance is planned.
- Due to the termination of an internship, availability has been reduced. It is recommended to replace the Enterprise Edition of GitLab with the Community Edition and open an SSH port for Git LFS.
- Documentation from the QA team is not expected before Flock To Fedora, where it will be discussed.
- David Kirwan has set up a managed GitLab instance with a free tier available through the OpenShift operator.
- Previous issues with Fedora’s enterprise licensing make it unlikely we’ll pursue this route. We need to confirm if the community operator can deploy the Community Edition.
- Configuration notes for GitLab Runner are available.
- Tomas suggests seeding the deployed GitLab instance from dist-git.
- Upcoming Actions:
- David Kirwan will deploy the Community Edition of GitLab and explore pre-seeding options.
- Lenka Segura will investigate setting up a GitLab Runner.
- Akashdeep Dhar will review user stories on Forgejo.
- Tomas Hrcka will engage with the QA team at Flock To Fedora and update the community on progress.
- Tomas Hrcka will also review the QA documentation.
- Timeline:
- No definitive deadline for the investigation, but a tentative deadline is the F41 Release (End of October).
- A migration plan is expected by F42, with updates to be provided at the F41 Release Party in early November.
If you have any questions or feedback, please respond to this report or contact us on the #redhat-cpe channel on matrix.