Hi everyone,

This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/).

Week: May 30st to June 3rd 2022

If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update--week-22-2022/

# Highlights of the week

## Infrastructure & Release Engineering Goal of this Initiative ----------------------- 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.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I&R-2022-06-01.pdf

Update ------

### Fedora Infra * Got to the bottom of an issue causing python38 modules to not be available in the epel8 buildroot * Bunch of reinstalling of openqa workers to help AdamW isolate a lockup issue. Still ongoing. * Moved some more ocp3->ocp4 apps. * Tracked down a https push segfault on src.fp.o to the new jq package in rhel 8.6 (downgraded and filed bug) * Got internetx02 (new donated hw replacement for 01) installed with rhel9. * New ipsilon release! Many thanks Abompard! (dedicated otp field, email or login works, and more)

### CentOS Infra including CentOS CI * Artifacts storage node replacement for CI (ready/deployed but to be announced in wider communication plan) https://pagure.io/centos-infra/issue/605 * CBS/koji proxy/settings tuning due to introduced change for gitlab (breaking some builds/tests) https://pagure.io/centos-infra/issue/782 * Roadmap for CentOS CI move to EC2 (working on communication plan) * Business as usual (mirrors proposals, tags) * Blocked: * Git.centos.org (waiting on EXD) * Stream storage migration (waiting on IT)

### Release Engineering * F34 is going EOL in one week * glibc update broke ostree updates in f36, more info https://pagure.io/releng/issue/10816 * Business as usual

## CentOS Stream Goal of this Initiative ----------------------- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream.

Updates ------- * Initial push of c8s packages to gitlab. * New Content Resolver feature: it's now showing repo per package in views. * Fedora ELN: Repositories are now closer to CentOS Stream, the Everything repository has been replaced with Extras which contains the packages not explicitly included in the other Variants.

## CentOS Duffy CI Goal of this Initiative ----------------------- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality.

Updates ------- * Client CLI (almost there) * Migration Preparations

## Package Automation (Packit Service) Goal of this initiative ----------------------- Automate RPM packaging of infra apps/packages

Updates ------- * Business as usual * Continued work on noggin-messages and datanommer-models

## EPEL Goal of this initiative ----------------------- 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 and Scientific Linux (SL), Oracle Linux (OL).

EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more.

Updates ------- * This week we have 5863 (+99) packages, from 2672 (+6) source packages * amavis installation from epel9 problem resolved by backporting upstream patch to switch dependency from libidn to libidn2 * Backported java_arches macro from Fedora to epel9 * Working on a method for enabling CRB repository when epel-release is installed * Deployed fix for some CRB module packages not showing up in the epel8 buildroot, but it caused too many non-default module packages to be included so it had to be rolled back. * Retired lmdb-epel since lmdb-devel was added to RHEL8/RHEL9. Later discovered that some users still depend on the lmdb subpackage (even though nothing in EPEL requires it), so the package was unretired to provided just that subpackage on epel8 only.

Kindest regards, CPE Team