Originally published at: Infra and RelEng Update - Week 45, 2024 – Fedora Community Blog
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. 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: 4th November 2024 – 8th November 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:
- Need OIDC credentials for fedora magazine in staging
- Retirement of `monitor-dashboard` tracker
- Create a POC integration in Konflux for fedora-infra/webhook-to-fedora-messaging
- Retirement of `monitor-gating` tracker
- setup ipa02.stg and ipa03.stg again as replicas
- Move OpenShift apps from deploymentconfig to deployment
- RFE: fedoras container image register change
- The process to update the OpenH264 repos is broken
- httpd 2.4.61 causing issue in fedora infrastructure
- Support allocation dedicated hosts for Testing Farm
- EPEL minor version archive repos in MirrorManager
- vmhost-x86-copr01.rdu-cc.fedoraproject.org DOWN
- Update DRAC Firmware on All Dell Servers
- Add yselkowitz to list to notify when ELN builds fail
- Recurring issue that Bugzilla stops sending messages to fedora-messaging
- Cleaning script for communishift
- rhel7 eol
- move resultsdb-ci-listener deployment pipeline
- rhel7 EOL – github2fedmsg
- Setup RISC-V builder(s) VM in Fedora Infrastructure
- Move from iptables to firewalld
- Help me move my discourse bots to production?
- 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:
- COPR group creation request – haunted ARM SoCs
- releases.json on https://getfedora.org/releases.json lost f39
- Planned Outage – pagure.io – 2024-10-31 18:00 UTC
- debuginfod01 disk issues
- Pagure messages are not being delivered to toddlers
- Add versioning/lifecycle config to prod FCOS S3 bucket
- Please delete or anonymize an incorrectly created account
- Archive data more than once a year, due to local diskspace issues
- Mailman deployment memory spikes
- Searching mailing list archives does not work
CentOS Infra including CentOS CI
- In progress:
- Done:
Release Engineering
- In progress:
- Fewar koji admins
- Update the Final RC SOP
- please create epel10 based el10-openjdk tag
- Fedora-FEX-Rootfs is missing from koji tags
- Could we have fedoraproject-updates-archive.fedoraproject.org for Rawhide?
- Impact check for Changes/FEX
- 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
- Drop modularity from EPEL8.
- 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:
- Package golang-github-peterbourgon-diskv not tagged epel10.0
- Stalled EPEL package: gperftools
- Stalled EPEL package: nvml
- consistent naming of release artifacts
- New branch created incorrectly
- package gsoap not in list for tag epel10.0-testing-candidate
- Stalled EPEL packages: armadillo and libgta
- fedora:latest container still provides f40 not f41
- Moar koji admins
- Block following retired packages in koji please
- epel10 build rejected
- Stalled EPEL package: python-webencodings
- Fedora Atomic Desktops ostree 41 stable refs are not setup properly
- F41 cloud nightlys are trying to tag into f41
- Create detached signatures for the ignition 2.20.0 release
- retirement processing based on age of pushed commit that adds “dead.package” is too strict
- Please add permission for blocking for epel tags for toddlers
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.