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: 09 September – 13 September 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:
- Create pagure API token with group_modify ACLs
- Need some OIDC credentials for com blog in STG
- requesting access for GitLab test instances
- RFE: fedoras container image register change
- [CommOps] MediaWiki – HitCounter Extension
- httpd 2.4.61 causing issue in fedora infrastructure
- Support allocation dedicated hosts for Testing Farm
- Feature / Change request: make the Fedora bugzilla more accessible
- Searching mailing list archives does not work
- Moderating mailing list viewing message shows “This held message has been lost.”
- EPEL minor version archive repos in MirrorManager
- vmhost-x86-copr01.rdu-cc.fedoraproject.org DOWN
- Recurring issue that Bugzilla stops sending messages to fedora-messaging
- Cleaning script for communishift
- rhel7 eol
- rhel7 EOL – github2fedmsg
- Setup RISC-V builder(s) VM in Fedora Infrastructure
- 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
- Migration of registry.fedoraproject.org to quay.io
- Commits don’t end up on the scm-commits list
- Done:
- Requesting communishift for “this week in bootc” infra
- requesting access for GitLab and Forgejo test instances
- fedora mirror zsh script breaks when trying to update files
- STG Bugzilla doesn’t send messages to STG fedora-messaging
- Request for access to rabbitmq/AMQP instance
- Out of memory on ppc64le builder
- DNSSEC delegation records should stop using SHA-1
CentOS Infra including CentOS CI
- In progress:
- Done
Release Engineering
- In progress:
- Please re tag rust-exacl-0.12.0-2.el9 to replace rust-exacl-0.12.0-1.el9
- release-candidate.sh adjustments needed
- fedpkg request-branch –all-releases Attempts to Create F42 & Releng Bot FailUnretire python-importlib-resources
- The `openh264` package fails to install because of the GPG key
- Fedora 41 Mass Branching Tracker
- 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
- Update bootloader components assignee to “Bootloader Engineering Team”for Improved collaboration
- Done:
- F41 stable push requests
- epel10 buildroot seems to be broken [Error: Unable to find a match: python3-dnf dnf-plugins-core]
- Add critpath data for ELN
- Please delete accidental “epel9” branch in rpms/btrfs-efi
- ELN Composes failing with “read-only filesystem” error
- enable bodhi composes for EPEL-10.0
- i686 builders need to use 32-bit inode numbers
- Remove PDC from package retirement process
- sidetag cleanup improvements
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
- EPEL 10 source package count: 1436
- Enabled nightly composes for EPEL 10
- Adjusted mdapi to account for EPEL 10 minor verisons
- Fixed mdapi bug where valid repos were being skipped
- Added python-websocket-client to EPEL 10 to unblock adding python-openshift
- Removed coverage build-time dependency from grpc (reduce blockers for adding to EPEL 10)
- Removed async-timeout build-time dependency from python-valkey (reduce blockers for adding to EPEL 10)
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
- Fedora:
- Podman Desktop:
- Other:
- Posted initial ideas for Ramalama logo #166
ARC Investigations
The ARC (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.
Updates
- Dist Git Move
- User stories are updated on the website – We have 79 of them now
- Work in progress – Seeding of GitLab and Forgejo for workflow testing
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
Start the discussion by commenting on the auto-created topic at discussion.fedoraproject.org