Originally published at: Infra and RelEng Update - Week 33 – 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: 12 – 16 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
Fedora Infra
- In progress:
- RFE: fedoras container image register change
- httpd 2.4.61 causing issue in fedora infrastructure
- Support allocation dedicated hosts for Testing Farm
- buildhw-a64 01,02,19,20,21,22,23,24 not booting
- Feature / Change request: make the Fedora bugzilla more accessible
- Searching mailing list archives does not work
- release-monitoring.org crawlers seem to not be running since ~June 26
- Moderating mailing list viewing message shows “This held message has been lost.”
- EPEL minor version archive repos in MirrorManager
- Private mirror check-in with mirrormanager fails
- vmhost-x86-copr01.rdu-cc.fedoraproject.org DOWN
- AWS: Support adding elastic IPs
- AWS: support creating S3 buckets
- Add yselkowitz to list to notify when ELN builds fail
- Cleaning script for communishift
- rhel7 eol
- rhel7 – PDC
- rhel7 EOL – Fedimg
- rhel7 EOL – github2fedmsg
- Move from iptables to firewalld
- Update compose hosts to get latest pungi release (4.6.0)
- notofications do not notify
- fedmsg -> fedora-messaging migration tracker
- rhel9 adoption
- Create monitoring tool for rabbitmq certificates
- Replace Nagios with Zabbix in Fedora Infrastructure
- Deploy new sign hardware/software
- Migration of registry.fedoraproject.org to quay.io
- Commits don’t end up on the scm-commits list
- Done:
- Remove DNS entry for component-registry
- Grant additional permissions to the fedimg AWS role
- Fedora Infrastructure workshop on Flock
CentOS Infra including CentOS CI
- In progress:
- Done:
Release Engineering
- In progress:
- Repo for golang-github-cloudsoda-smb2 not properly created
- Fedora 41 Mass Branching Tracker
- Unretire ttyd
- 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
- Some (?) retired packages not actually getting retired since ~2 days ago
- Drop modularity from EPEL8.
- unmaintained bot account: dummy-test-package-gloster gating pipeline tests broken
- Renaming distribution media for Fedora Server
- Package retirements are broken in rawhide
- Implement checks on package retirements
- Untag containers-common-0.57.1-6.fc40
- orphan-all-packages.py should remove bugzilla_contact entries from fedora-scm-requests as well
- Packages that fail to build SRPM are not reported during the mass rebuild bugzillas
- When orphaning packages, keep the original owner as co-maintainer
- Create an ansible playbook to do the mass-branching
- Cleaning old stuff from koji composes directories
- Fix tokens for ftbfs_weekly_reminder. script
- i686 builders need to use 32-bit inode numbers
- Remove PDC from package retirement process
- Update bootloader components assignee to “Bootloader Engineering Team”for Improved collaboration
- Done:
- Fedora Linux 41 is branched from Rawhide
- Unretire python-mkdocs-redirects
- python-hatch-nodejs-version has wrong owner
- package golang-github-linuxdeepin-x11-client not in list for tag f41-updates-candidate
- Unretire rust-inlinable_string
- rust-interprocess1 not properly tagged, blocking updates
- Create rawhide+1 (F42) keys
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
- Fix RuntimeError in owner-sync-pagure.j2
- Allow EPEL 10 bootstrap updates to go straight to stable
- Updated EOL EPEL README files to remove outdated contact information
- Updated pagure-dist-git to unblock pushing to epel10 branches
- EPEL 10 hackfest at Flock
- EPEL 10 repo is not published yet, but packagers can request branches and do builds. We’ve already passed 200 EPEL 10 builds.
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
- Podman Shirt
- F41 Wallpaper and F42 Wallpaper Process
- Ignite Logo
- CPE Swag
List of new releases of apps maintained by CPE
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.