Originally published at: Infra and RelEng Update – Week 29 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 an 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: July 15-19, 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
- Request for new FAS group: miracle-sig
- Private mirror check-in with mirrormanager fails
- rhel9 adoption
- How do I set up FAS login for discussion.stg.fedoraproject.org?
- Private mirror check-in with mirrormanager fails
- Still CC’ed in Chromium security bugs even though I’m not in points of contact anymore
- 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
- Need to compress logs on log01
- 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
- Done:
- COPR cannot pull git repo from fedorapeople
- Disable posts on mailman01.stg
- Planned Outage – Server updates/reboots – 2024-07-10 21:00 UTC
- developer sync broken with move to rhel9
- koji builders: Update flatpak-module-tools to fix compat with zstd metadata
- Enable markdown formatting for CoreOS CI maubot instance
- Enable Auto-Signing for f41-rebuild Mass-Rebuild Tag
- Update Fedora Planet wiki
- Spam in AskFedora
- Request for m4.10xLarge Instance to Support Fedora Apps Containerisation
CentOS Infra including CentOS CI
- In progress:
- Done:
- Nothing as Fabian is on PTO
Release Engineering
- In progress:
- Fedora 41 Mass Rebuild has started.
- 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
- Retire EPEL 8 Next
- unmaintained bot account: dummy-test-package-gloster gating pipeline tests broken
- Drop modularity from EPEL8.
- Fedora 41 Mass Rebuild Tracker
- Some (?) retired packages not actually getting retired since ~2 days ago
- EPEL 8 buildroot broken (no platform-python)
- Unretire 0install
- Done:
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 deprecation warnings in toddlers
- Add EPEL 10 support to scm_request_processor toddler
- Worked with releng to isolate issue with EPEL 8 builds
- Adjusted CentOS batcave scripts to delete excluded content
- Updated tinyproxy in EPEL 8, EPEL 9, F39, F40, and Rawhide to address CVE-2023-49606
Community Design
CPE has a few members who are working as part of the Community Design Team. This team is working on anything related to design in the Fedora Community.
Updates
- Podman: Improving consistency across all pages 📃
- CoreOS 5th anniversary designs
- Swag designs for Flock 🐤o
- last day to vote for F42 inspo on Fedora discussions
ARC Investigations
The ARC (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.
Updates
- Git Forge Investigation
- Akashdeep Dhar has provided the recap on Git Forge Investigation so far to Ryan Lerch on a 1:1 meeting call
- Akashdeep Dhar plans to get started with investigating the self-hosted GitLab deployment on the user stories
- Akashdeep Dhar has provided service accounts to Tomas Hrcka, Kevin Fenzi, and Ryan Lerch
- Ryan Lerch wants to work on investigating GitLab on the user stories provided using the service account
- Tomas Hrcka will be meeting with the Fedora Governance team
- Share the inability to share the final comparison until Flock
- Open up INVITE-ONLY deployments for GitLab and Forgejo during Flock
- Michal Konecny is looking into deploying Forgejo at his end
- Tomas Hrcka plans on opening the meetings up to the open community
- Especially for testing the user stories with the provided deployment for GitLab and Forgejo made by us on OpenShift
- David Kirwan and Lenka Segura joined the ARC investigation efforts with helping with the OpenShift deployments of GitLab and Forgejo
- This limited access and INVITE-ONLY deployment would be made available to community members to help with user stories
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.