June 2022 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

Few questions on cloud images
by Pino Toscano 06 Jun '23

06 Jun '23

Hello, I have few questions related to the cloud images provides for c8s and c9s, i.e.: - https://cloud.centos.org/centos/8-stream/x86_64/images/ - https://cloud.centos.org/centos/9-stream/x86_64/images/ 1) I see the c9s images are regularly updated, while the c8s images not; is this wanted, or simply a mistake/miss somewhere? If so, will they be kept up-to-date just like the c9s images? 2) are the Vagrant images there officially supported? Let's say you use one, and find a bug; then check on a "classic" installation (baremetal/VM), and the bug isn't there; can users report problems in those cases? 3) would it be possible to have either unversioned or "-latest" symlinks for the latest versions of all the files (i.e. images, checksums, etc)? This way, it will be much easier for users to fetch the latest versions with no need to change URLs frequently. Of course, the assumption is that users of this are always willing to use the latest version. Thanks! -- Pino Toscano

7 14

Proposal: CentOS Public Board Meetings
by Rich Bowen 07 Jan '23

07 Jan '23

In January of 2021, the CentOS Board of Directors opened our monthly meetings to all SIG chairs, in a first step towards more transparent governance. We wanted to see how the larger audience changed the meeting dynamics, if at all, as well as welcoming a broader pool of voices. We are now ready for the second part of this process. Starting in the August meeting, we will be inviting the entire CentOS community to attend these meetings. Due to the nature of the Internet, we won’t be simply publishing the meeting URL, as this often leads to disruptive behavior in meetings, as I am sure many of you have experienced. Rather, in the week before the meeting, we’ll send, to this list, a way to request an invitation to the meeting. In this way, we hope to limit the incidence of such disruptions, while also making the meeting available to anyone who wishes to attend. We will be working on the rules of engagement for these meetings, but they will be, at minimum: * Wait to be recognized by the Chair before speaking * Respect the Chair when told your time to speak is over - this will allow us to remain on agenda, and complete the meetings in the allotted time * In the event that there are Board-confidential topics, these will be put at the end of the meeting, in Executive Session, and guests will be asked to leave. We hope to minimize these items, but they do sometimes happen. The most common scenarios in which this may happen are personnel issues, or information that Red Hat wishes to share with the Board, but is not yet public. * Muting of participants, or, in extreme situations, ejection from the meeting, is at the sole discretion of the Chair. * Meetings will be recorded, and published to YouTube (possibly with edits/redactions, as approved by the Directors). Thus, by joining the meeting you consent to have your presence at the meeting, and anything you say during the meeting, made public. Because there will seldom be time for Q&A during the meeting itself, we plan to add a post-meeting IRC office hours session for followup questions. This will probably be scheduled for a week after the board meeting, to allow time to publish meeting minutes We welcome your comments about the above proposal, and thank you all for your patience as we implement these changes to our governance process.

8 27

Board Nominations Requested
by Shaun McCance 11 Jul '22

11 Jul '22

** Please read this entire email before responding with nominations. ** We have a process, and the process is important. As per our governance docs: https://www.centos.org/about/governance/board/ Every six months, half of our directors are asked if they wish to continue in their seats or step down. This time, we will have one seat to fill. Tru Huynh has indicated to the board his intent to step down. Tru has been a part of this community for a long time, and we all deeply appreciate the work he's done both on the board and across the entire project. We are asking you, the CentOS community, for nominations for who should fill Tru's seat. Note that the vote on who will fill his seat is held by the board itself, but nominations are open to the entire community. If you would like to nominate someone (or self-nominate), please use this Google form: https://forms.gle/WsknUVnPL5zbWcSK6 Please DO NOT send nominations to this list. As this is not a public vote, we don't to give the impression of a popularity contest with public nominations. We also want to avoid any shaming if someone is nominated and is not seated, or chooses not to accept. I will ensure that each nominee is willing and able to serve, and the board will consider them and select the next director from the list. If you wish to nominate someone, you should consider the list of director requirements and recommendations listed at: https://www.centos.org/about/governance/director-requirements/ Thank you for your thoughtful consideration and participation in this process. -- Shaun, for the CentOS Board of Directors

5 9

Changes on CentOS CI and next steps
by Camila Granella 11 Jul '22

11 Jul '22

*TL;DR: CentOS CI is going hardwareless and if you wish your project remains using it, we need your opt-in by August 2022. There is a Dojo Summer 2022 <https://wiki.centos.org/Events/Dojo/Summer2022> session happening on Thursday, June 17th, that will explain further technical details. * Hello everyone, As many of you know, since the beginning of this year we have been reevaluating the future of CentOS CI, as currently the hardware being used for it is out of warranty. This is due to the fact that CentOS CI came from community donations of hardware which were maintained in a best effort manner by our team. With no warranties, when the physical machine dies we have no means to replace it. Right now though, our hardware, due to a lack of warranty, will not be moved with the upcoming data center changes due to data center requirements to have in warranty hardware for supportability. We decided to take this opportunity to modernize our current infrastructure, pushing it to a hybrid cloud environment. Duffy CI will become the main tool from now on, so that we can support the CI workflow and best practices on cloud and for this reason, the current hardware infra will no longer be available soon. However, as an effort to continuously provide resources and support CI best practices for projects, our team is adapting Duffy CI so that we can maintain most of the characteristics of our current, physical-based offering. At the technical level, what does that mean for you, CI tenants? - A new Duffy API service will replace the existing one: while it will be running in compatibility/legacy mode with the previous version, you will need to adapt your workflow to the new API, but more details below - We will transition to AWS EC2 instances for the aarch64 and x86_64 architectures by default, with a (limited) option to request “metal” instances for projects requiring virtualization for their tests (like KVM/vagrant/etc) - We will keep a (very small) Power9 infra “on-premise” (AWS does not support ppc64le) for the ppc64le tests (available through a dedicated VPN tunnel) - The existing OpenShift cluster will be also decommissioned and a new one (hosted in AWS, so without an option to run kubevirt operator nor VMs) will be then used (you will have to migrate from one to the other) With that being said, tenants can start preparing for the changes to happen with the maximum deadline of the end of December 2022 wherein at this point, Duffy API legacy mode will be removed. You are required to opt-in if you and/or your team want to use Duffy CI. Projects will only be migrated if they reply to this email confirming that they wish to proceed. Worth knowing that not opting in means that your API key will not be migrated and so all your requests to get temporary/ephemeral nodes will be rejected by the new Duffy API. The maximum decommission deadline of the current hardware infrastructure is December 12th, 2022 and the new Duffy CI will go live in August 2022, so please, complete your migration process by the end of CY22. Reminders of deadlines and of the opt-in requirements will be sent monthly, but your confirmation of opt-in is required by August 2022. When approaching December, reminders about deadlines frequency will increase so that we can ensure effective communication throughout the process. Here are the steps in which we will migrate CI Infra: Phase 1 - Deploy Duffy V3 (August 2022) - Deploy in legacy/compatibility mode, so existing tenants (that opted in !) can still request duffy nodes the same way (like with 'python-cicoclient') : no change at tenants side, and exactly same hardware for tests (transparent migration) - New Duffy API endpoint becomes available, and tenants can start adapting their workflows to point to new API (new ‘duffy-cli’ tool coming, with documentation) - Bare metal and VMs options will be available already through the new API (x86_64, aarch64, ppc64le) Phase 2 - Hybrid Cloud (October 2022) - Legacy/compatibility API endpoint will handover EC2 instances instead of local seamicro nodes (VMs vs bare metal) - Bare metal options will be available through the new API only - Legacy seamicro and aarch64/ThunderX hardware are decommissioned - Only remaining "on-premise" option is ppc64le (local cloud) Phase 3 - Decommission (December 2022) - Legacy/compatibility API deprecated and requests (even for EC2 instances) will no longer be accepted - All tenants that opted in will be using only EC2 for aarch64/x86_64 and on-premise cloud for ppc64le OpenShift new deployment planning and timeline To be defined (deadline for planning and timeline: end of June 2022) Do not hesitate to reach out if you have any questions. It is worth knowing that there will be a dedicated session about the Future of CentOS CI infra at the next CentOS Dojo happening on June 17h (check Dojo Summer 2022 <https://wiki.centos.org/Events/Dojo/Summer2022>). That session will be recorded and then available on Youtube but if you have any questions. Feel free to join the CentOS Dojo and reach out to us! Best regards, -- Camila Granella Associate Manager, Software Engineering Red Hat <https://www.redhat.com/> @Red Hat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

3 3

New SIG idea - Stream Live Images / Alt Installs
by Troy Dawson 01 Jul '22

01 Jul '22

Before I get all worked up about this idea, I want to see if it is feasible, and if there is any interest in it. I'd like to start a SIG where we create images (Live and Install iso's) that are based on both CentOS Stream and EPEL together. For live images we could have a CS9-KDE-Live.iso, CS9-XFCE-Live.iso, CS9-GNOME-Live.iso, or even a large CS9-ALL-DESKTOPS-Live.iso. For install images we could have CS9-minimal.iso, maybe a KDE, or others. I mainly want the minimal iso so I don't have to download the massive 8 Gig DVD if I want just the minimum, but don't want to do a network install. So, my two questions are. Would this be possible on the current CentOS Stream infrastructure? Would anyone else want a SIG like this? Troy

5 5

Stream 9: where is the repo file for SIGs/.../centos-plus?
by Anthony Alba 29 Jun '22

29 Jun '22

I unpackaged all the centos-release*rpm files I could find, but couldn't find one that references SIGs/core/$basearch/centos-plus. Regards Anthony

2 1

Centos Stream 8 vagrant images not regularly updated
by Nikolaos Moumoulidis 24 Jun '22

24 Jun '22

Hi all, There was a thread created by a colleague of mine a few months ago ( https://lists.centos.org/pipermail/centos-devel/2022-January/120156.html) regarding the CS8 vagrant images not being upgraded regularly in either https://cloud.centos.org/centos/8-stream/x86_64/images/ or https://app.vagrantup.com/centos/boxes/stream8 and the reply was a new process will be created for this to happen monthly. This hasn't happened yet (I understand, we're all busy), so I wanted to check on the status of if/when it will. Ideally https://app.vagrantup.com/centos/boxes/stream8 would be the best place since the '-latest' suffix scheme seemed to not be feasible for now, but even updated images in https://cloud.centos.org/centos/8-stream/x86_64/images that we could manually update the url to every now and then would work. Thanks, Nikos

1 0

CPE Weekly Update – Week 25 2022
by Akashdeep Dhar 24 Jun '22

24 Jun '22

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: 20th - 24th June 2022 If you wish to read this in form of a blog post, check the post on the Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-25-2022/ Highlights of the week Infrastructure & Release Engineering Goal of this Initiative 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.). 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-22.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update Fedora Infra - Most apps have moved over to the OpenShift4 cluster. Hopefully, the transition should be finishing up this week. - Wiki: All upgraded in production and working (thanks Ryan!) - Resultsdb: All moved over to OpenShift 4 in prod and working (thanks Leo!) - Business proceeding as usual CentOS Infra including CentOS CI - Kerberos settings switch for git.centos.org (kcm on el8 vs keyring on el7) for lookaside upload CGI <https://pagure.io/centos-infra/issue/811> [1] - Issue on iad2 hosted reference mirror <https://pagure.io/centos-infra/issue/812>[2] (epel.next and mirrormanager), all fixed now - Duffy CI ongoing tasks and deployments (all announced) - Equinix nodes migration <https://pagure.io/centos-infra/issue/816>[3] (on their request) - Business proceeding as usual Release Engineering - Compose-tracker updated to f36 in staging, production happening tomorrow - Python 3.11 merged to rawhide - MBS randomly fails to process builds - Rawhide compose failures recently (syslinux retirement, then python 3.11 merge) all fixed now - Business proceeding 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 - CentOS Stream 8: Manually keeping regular RPMs and module RPMs updated on the koji.stream server as current updates are composed and released. CentOS Duffy CI Goal of this Initiative Duffy is a system within CentOS CI infrastructure allowing tenants to provision and access machines (physical and/or virtual, of different architectures and configurations) for the purposes of CI testing. Development of Duffy is largely finished, we're currently planning and testing deployment scenarios. Updates - Release version 3.2.1 - Docs, docs, docs and a Dojo Package Automation (Packit Service) Goal of this initiative Automate RPM packaging of infra apps/packages Updates - Mostly business as usual - Thanks again to all who are reviewing our PRs - Most of our GitHub critical apps are enabled now or close to being enabled Flask-oidc: oauth2client replacement Goal of this initiative Flask-oidc is a library used across the Fedora infrastructure and is the client for ipsilon for its authentication. flask-oidc uses oauth2client. This library is now deprecated and no longer maintained. This will need to be replaced with authlib. Updates: - POC working using authlib, tidying up code to prepare to submit a PR back to upstream 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 a build system, Bugzilla instance, updates manager, mirror manager and more. Updates - This week we have 6442 (+127) packages, from 2882 (+76) source packages - Containerd and puppet retired from EPEL7 because of upstream EOL and multiple CVEs. - Caddy was updated, fixing 4 CVEs in EPEL9 *Index* [1] https://pagure.io/centos-infra/issue/811 [2] https://pagure.io/centos-infra/issue/812 [3] https://pagure.io/centos-infra/issue/816 Thanks and Regards, Akashdeep Dhar (he/him), Objective Representative, Fedora Council Red Hat Community Platform Engineering t0xic0der(a)fedoraproject.org akashdeep(a)redhat.com

1 0

[REPORT] Quarterly Report - CentOS Automotive SIG
by Jeffrey Osier-Mixon 24 Jun '22

24 Jun '22

June 2022 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - acting chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 94 subscribers representing at least 30 organizations, though not all subscribers use corporate emails and some are participating as individuals. _____________________________________ Releases in the most recent quarter (or most recent release, if none in that quarter) The SIG provides a new distribution: Automotive Stream Distribution (AutoSD), a CentOS Stream derivative designed specifically around the needs of an automotive OS, and transparently the upstream project for Red Hat's eventual in-vehicle OS product. AutoSD has been downloaded and used by several organizations who have commented or asked for help, so we know it is getting some traction though of course we don't have exact metrics on usage. _____________________________________ Health report and general activity narrative. The SIG has had two public meetings per month, one formal and one informal "office hours", each with 25-40 attendees, with visible participation from 7-10 separate organizations. This SIG is intended to be a community effort with contributions and shared benefits from all participants. All formal meetings are recorded and posted on this page: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings Several Red Hat employees made the initial contributions to the project as well as the infrastructure required to build and test it. We now occupy a gitlab repository building software regularly using CI, with build instructions provided on the documentation page at https://sigs.centos.org/automotive/ . Sample images are present and downloadable along with customization and build instructions. This is a high-level summary of current activity: - All work has migrating to a CentOS namespace within GitLab in order to cement our intention as a community project: https://gitlab.com/centos/automotive - CI/CD infrastructure is in place - Firmware size has been reduced - Encryption is available via LUKS - a Linux chroot is being worked on for Android devices - manifests now enable EFI runtime services - Lookaside cache structure - Downloadable images are available: https://autosd.sig.centos.org/ - Documentation has been greatly expanded with both community and corporate contributions: https://sigs.centos.org/automotive/ - Documentation now includes detailed contribution guidelines: https://sigs.centos.org/automotive/contributing/contributing-to-auto-sig-re… - Ongoing discussions within the meetings have centered around supported hardware and expectations for documentation - A new meetings page contains recordings of all meetings: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings - Synchronous communications have moved from IRC to Matrix thanks to some help from Fedora: https://app.element.io/#/room/#centos-automotive-sig:fedoraproject.org _____________________________________ Issues for the board to address, if any None, keep up the excellent work :) Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

Dojo at DevConf, August 17
by Shaun McCance 21 Jun '22

21 Jun '22

Thanks to everybody that attended our online Summer Dojo. We are holding an in-person Dojo on August 17 at Boston University. This is the day before the main track of DevConf.US, at the same venue. https://wiki.centos.org/Events/Dojo/DevConfUS2022 The call for presentations is open. We look forward to talks from the entire Enterprise Linux ecosystem, from how it's built to how it's used. We have both 20-minute and 40-minute talk slots. https://forms.gle/QjGki4whyWTvnD4q9 (If you previously tried to submit a presentation and didn't have permission, it's because I forgot to change the settings to allow submissions from outside Red Hat. Sorry. It's fixed now.) Thanks, Shaun McCance CentOS Community Architect Red Hat Open Source Program Office

1 0

Search through CentOS Stream specfiles
by Maxwell G 20 Jun '22

20 Jun '22

Hi everyone, Is there some sort of specfile tarball or other method to search through all the CentOS Stream specfiles for a regex? In Fedora, we have a tarball[1] with all the specfiles that's generated daily, as well as access to Sourcegraph[2]. Is there an equivalent for CentOS Stream/RHEL? Of course, I could manually extract them from the *-source yum repos' SRPMs or distgit, but that would be tedious. [1]: https://src.fedoraproject.org/lookaside/git-seed-latest.tar.xz [2]: https://sourcegraph.com/search? q=context:global+r:src.fedoraproject.org+file:.*%5C.spec%24+ %5EName:&patternType=regexp&case=yes -- Thanks, Maxwell G (@gotmax23) Pronouns: He/Him/His

5 5

CPE Weekly Update – Week 24 2022
by Michal Konecny 20 Jun '22

20 Jun '22

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: 13th - 17th June 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-24-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-15.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update ------ ### Fedora Infra * Resultsdb almost moved to ocp4 in prod, just a few parts to finish (Thanks Leo!) * Ocp4 cluster now on our vpn, so all proxies can reach apps (thanks darknao!) * Wiki upgrade looking good in staging, prod to come (thanks ryan!) * Some more vm’s to f36 * About 50% done moving apps to ocp4. * Image builder prod move blocked due to firewall issues ### CentOS Infra including CentOS CI * https://git.centos.org went live last monday * Trying to resume discussion with RH IT for Stream storage migration * New CI infra deployment tasks to be ready * https://lists.centos.org/pipermail/ci-users/2022-June/004547.html ### Release Engineering * ELN composes were broken over the weekend because of ODCS backend / front end version mismatch * Nodejs-sig removed as the default assignee on a bunch of components in BZ * we have discovered workflow in bodhi that locks update in a weird state more info https://github.com/fedora-infra/bodhi/issues/4566 ## 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 ------- * We imported all RPMs for modules (CentOS Stream 8) to the shared buildsystem * All sources imported to GitLab (CentOS Stream 8) ## CentOS Duffy CI Goal of this Initiative ----------------------- Duffy is a system within CentOS CI infrastructure allowing tenants to provision and access machines (physical and/or virtual, of different architectures and configurations) for the purposes of CI testing. Development of Duffy is largely finished, we're currently planning and testing deployment scenarios. Updates ------- * Test and polish `duffy client …` experience * Docs and CentOS Dojo talk prep ## Package Automation (Packit Service) Goal of this initiative ----------------------- Automate RPM packaging of infra apps/packages Updates ------- * Almost finished, only mirrormanager2 remaining from our critical apps on Github * Couple of outliers (fasjson, flask-mod-auth) need downstream repos created * Datanommer.models manually packaged so datagrepper can be automated * Noggin now fully automated ## Flask-oidc: oauth2client replacement Goal of this initiative ----------------------- Flask-oidc is a library used across the Fedora infrastructure and is the client for ipsilon for its authentication. flask-oidc uses oauth2client. This library is now deprecated and no longer maintained. This will need to be replaced with authlib. Updates: -------- * Working [poc app](https://app-flask-oidc-dev.apps.ocp.stg.fedoraproject.org/oidc/) which authenticates against noggin/ipa using authlib and OIDC. * Working on an upstream PR with the working code now. ## 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 6315 (+297) packages, from 2806 (+76) source packages * [XFCE now available in epel9-testing](https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5fe… * Removed epel9 packages that were included in rhel9.0 * oniguruma: [backported fix](https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-a9236c0113) for CVE-2019-13225 (moderate) from rhel8 to epel7 * drbd: pull request to [switch pacemaker dependency from requires to recommends](https://src.fedoraproject.org/rpms/drbd/pull-request/2) to comply with policy Kindest regards, CPE Team

3 2

How does a 9-stream package move from Koji to released-to-mirrors?
by Ian Wienand 16 Jun '22

16 Jun '22

Hello, We are waiting on a change made to libselinux [1] to hit the 9-stream mirrors as described in [2]. It's rather unclear to me how this happens? I have read [3] but unfortunately I'm still not groking it. I know this build has been committed to gitlib, and koji has picked it up and built it [4]. It has tags * c9s-build-side-477-stack-gate * c9s-candidate * c9s-pending which [3] sort-of explains -- the package build has passed testing? >From what I understand, it then goes into a compose visible from [5]. Not sure what "odcs" stands for, but these seem to be daily builds (?-daily-centos-stream maybe?). Then there is production/ which has timestamped directories currently: CentOS-Stream-9-20220531.0/ CentOS-Stream-9-20220606.0/ CentOS-Stream-9-20220607.0/ CentOS-Stream-9-20220613.0/ latest-CentOS-Stream/ Are these production composes weekly, daily, or perhaps ad-hoc depending on somebody flipping a switch? Something suggests to me that "latest-CentOS-Stream" should be ~= to the mirror repos [6]. Is that right? If I look in CentOS-STream-9-20220613.0 (latest-CentOS-stream, currently), it indeed has libselinux-3.4-2 that we want. However, if I sort the mirror by date [7] nothing seems to have updated since 2022-06-06? So, if I'm on the right track here -- what promotes the "production" compose to the public mirrors? Thanks for any insight -i [1] https://gitlab.com/redhat/centos-stream/rpms/libselinux/-/commit/c68e490c94… [2] https://bugzilla.redhat.com/show_bug.cgi?id=2094683 [3] https://docs.centos.org/en-US/stream-contrib/quickstart/ [4] https://kojihub.stream.centos.org/koji/buildinfo?buildID=21551 [5] https://composes.stream.centos.org/ [6] http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/Packages/ [7] http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/Packages/?C=M;O=D

3 3

Samba from SIG is broken - ?
by lejeczek 15 Jun '22

15 Jun '22

Hi guys. I filed a bug report with RH's Bugzilla but nothing happened there thus thought I'd let - if SIGs read this list - you guys know that Samba 4.16 is broken, hard-crashes. For better picture - Samba is managed by IPA -> $ systemctl restart smb.service Starting Samba SMB Daemon... [2022/06/08 19:17:32.937351, 0, pid=49122] ../../source3/smbd/server.c:1741(main) smbd version 4.16.1 started. Copyright Andrew Tridgell and the Samba Team 1992-2022 [2022/06/08 19:17:32.960756, 0, pid=49122] ../../lib/util/fault.c:172(smb_panic_log) =============================================================== [2022/06/08 19:17:32.960925, 0, pid=49122] ../../lib/util/fault.c:176(smb_panic_log) INTERNAL ERROR: Signal 6: Aborted in pid 49122 (4.16.1) [2022/06/08 19:17:32.960981, 0, pid=49122] ../../lib/util/fault.c:181(smb_panic_log) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting [2022/06/08 19:17:32.961022, 0, pid=49122] ../../lib/util/fault.c:182(smb_panic_log) =============================================================== [2022/06/08 19:17:32.961056, 0, pid=49122] ../../lib/util/fault.c:184(smb_panic_log) PANIC (pid 49122): Signal 6: Aborted in 4.16.1 [2022/06/08 19:17:32.961647, 0, pid=49122] ../../lib/util/fault.c:288(log_stack_trace) BACKTRACE: 15 stack frames: #0 /lib64/libsamba-util.so.0(log_stack_trace+0x34) [0x7f41bbc0c7c4] #1 /lib64/libsamba-util.so.0(smb_panic+0xd) [0x7f41bbc0ca1d] #2 /lib64/libsamba-util.so.0(+0xeab9) [0x7f41bbc0cab9] #3 /lib64/libpthread.so.0(+0x12ce0) [0x7f41bb83bce0] #4 /lib64/libc.so.6(gsignal+0x10f) [0x7f41bb2a4a4f] #5 /lib64/libc.so.6(abort+0x127) [0x7f41bb277db5] #6 /lib64/libtalloc.so.2(+0x2f40) [0x7f41a34a7f40] #7 /lib64/libtalloc.so.2(+0x336c) [0x7f41a34a836c] #8 /usr/lib64/samba/pdb/ipasam.so(+0x11c2f) [0x7f41a38e7c2f] #9 /lib64/libsamba-passdb.so.0(make_pdb_method_name+0xb2) [0x7f41bbdae2f2] #10 /lib64/libsamba-passdb.so.0(+0x1d604) [0x7f41bbdae604] #11 /lib64/libsamba-passdb.so.0(initialize_password_db+0x1d) [0x7f41bbdb096d] #12 /usr/sbin/smbd(main+0x5d9) [0x55c945bbcf09] #13 /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f41bb290ca3] #14 /usr/sbin/smbd(_start+0x2e) [0x55c945bbe6de] [2022/06/08 19:17:32.962008, 0, pid=49122] ../../source3/lib/dumpcore.c:318(dump_core) coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern smb.service: Main process exited, code=dumped, status=6/ABRT smb.service: Failed with result 'core-dump'. Failed to start Samba SMB Daemon. many thanks, L.

3 5

June board meeting recording and office hours
by Shaun McCance 14 Jun '22

14 Jun '22

Hi folks, I've uploaded the recording of last week's board meeting: https://youtu.be/qPluJM12AhQ If you'd like to discuss any issues with the board, we'll have an open board office hours this Thursday, June 16, at 14:00 UTC. https://meet.google.com/ppx-hjdj-zrc Email me directly if you need dial-in info instead. Thanks, Shaun

1 0

[Infra] : Planned outage : git.centos.org
by Fabian Arrotin 13 Jun '22

13 Jun '22

Due to a scheduled pagure upgrade, we'll have to move the existing Pagure instance (aka https://git.centos.org) to a new node. Migration is scheduled for """"Monday June 13rd, 7:00 am UTC time"""". You can convert to local time with $(date -d '2022-06-13 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to : - backup/restore last DB dump - import and convert DB schema for newer pagure version - last data (sources in lookaside cache and git repositories) sync - verify service and switch public IP to new host. Important note wrt that migration is that we're moving from pagure 5.8 running on CentOS 7 to pagure 5.13 on RHEL 8. It means it's a new host and so sshd host keys will change (we didn't want to import older host keys to comply with newer algo) The new fingerprint will be displayed at usual place (https://git.centos.org/ssh_info) but it only matters for SIGs users pushing to specific projects/branches over ssh. For people pulling through https, nothing changes. Here are in advance the new fingerprints : rsa=3072 SHA256:qeSehpwh3X7HI0D/jF7N4qZcergdr9tUCdaZ2EIdiLc (RSA) rsa_md5=3072 MD5:a9:a1:ba:83:96:71:28:ca:86:19:c0:5d:4f:48:9f:63 (RSA) ecdsa=256 SHA256:vIRsg5g/t/7ucYP4NKTkcPJdE7CWbFQVInscthHKihU (ECDSA) ecdsa_md5=256 MD5:8f:40:35:4f:b9:43:60:d9:09:c0:5f:80:52:69:c8:8d (ECDSA) Also worth knowing that we also present a signed cert for sshd host keys, so if you already trust our CA (https://github.com/CentOS/ansible-role-sshd/blob/master/defaults/main.yml#L…) in your ~/.ssh/known_hosts file, you'll not even have to accept new key Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 1

Two Dojos
by Shaun McCance 10 Jun '22

10 Jun '22

Hi all, In case you missed it, we are having a free online Dojo next week on Friday, June 17. The schedule is live. It is free, but registration is required. https://wiki.centos.org/Events/Dojo/Summer2022 But wait, there's more! We've just announced an in-person Dojo to be held at Boston University on August 17. This is the day before the main sessions of DevConf.US. The CFP is open. The Dojo is free, as always, but we recommend and appreciate registrations to help us plan. https://wiki.centos.org/Events/Dojo/DevConfUS2022 I hope to see you all online next week, and I'm looking forward to finally seeing some of you in person in two months. Thanks, Shaun McCance CentOS Community Architect Red Hat Open Source Program Office

1 0

glibc-2.34-37.el9 enables rseq by default
by Florian Weimer 09 Jun '22

09 Jun '22

We are going to enable rseq registration in glibc by default starting with glibc-2.34-37.el9 (already built in Koji). To facilitate integration with other rseq users, we have backported the GLIBC_2.35 symbol set for rseq integration. Such an ABI update during a major release is not entirely unprecedented for glibc, but hasn't happened in recent times. If an application links against the symbols, RPM will generate the appropriate dependencies, forcing an upgrade to a compatible glibc version. This is unlikely to happen soon because the interface is glibc-specific and has only been added in glibc 2.35, so applications would have to be written specifically for this interface. As a side effect, criu needs to be updated to criu-3.17-2.el9 to remain functional. The background is that rseq is required to implement a useful version of sched_getcpu on AArch64. Previously, a system call had to be used, and with rseq, execution can remain in userspace. The benefit is less on other architectures, but still there (e.g., on x86-64, an obscure LSL instruction is replaced with a memory load). And once glibc registers its rseq area, nothing else in the process can register it again, which is why we need some interface to rseq-using applications. Rather than coming up with our own interface, we decided to just use the upstream interface. Not entirely by accident, the GLIBC_2.35 symbol set for ld.so consists precisely of the rseq symbols, so RPM dependency management should interoperate well with this change. (Our RPM version requires backporting such symbol sets in their entirety, we do not have per-symbol package versioning information like Debian in our package builds.) Due to a kernel bug on the CentOS builders, sched_getcpu may return the wrong values during package builds. I requested a builder kernel update here: Please upgrade c9s builders to an 8.4 or later kernel <https://issues.redhat.com/browse/CS-1129> Downstream, we have plans for maintaining ABI compatibility with RHEL 9.0: backporting the symbol set there as well, without registering rseq by default. I don't know yet if we are going to backport further symbol sets to CentOS 9 Stream. The requirement to backport full symbol sets could be quite onerous. Historically, the main driver for such backports has been to enable running applications on CentOS that have been built on other distributions. I suspect the glibc incompatibility is simply the first problem people saw, and we don't know what problems would have come next after had we eliminated the glibc obstacle. Applications for CentOS should really be built and tested on CentOS. Thanks, Florian

2 2

kmods SIG workflow skips the -70 EL9 kernel - why?
by Anthony Alba 09 Jun '22

09 Jun '22

Hi - I am confused about the SIGs Stream 9 workflow: I would expect the -70 kernel to make it into kmods SIG as I see it in kojihub. Yet the artifacts (I look at kmod-btrfs as example) skip the -70 kernel. Rebuild for 5.14.0-73.el9 Rebuild for 5.14.0-69.el9 So what determines if a kernel release makes into kmods? Cheers, Anthony Alba

2 2

corosynclib rpm issues - ?
by lejeczek 08 Jun '22

08 Jun '22

Hi guys, anybody sees this/similar? -> $ dnf clean all -> $ dnf update Error: Problem: package corosync-3.1.5-3.el9.x86_64 requires corosynclib(x86-64) = 3.1.5-3.el9, but none of the providers can be installed - cannot install both corosynclib-3.1.5-4.el9.x86_64 and corosynclib-3.1.5-3.el9.x86_64 - cannot install both corosynclib-3.1.5-3.el9.x86_64 and corosynclib-3.1.5-4.el9.x86_64 - cannot install the best update candidate for package corosynclib-3.1.5-3.el9.x86_64 - problem with installed package corosync-3.1.5-3.el9.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) -> $ dnf update --allowerasing Dependencies resolved. =================================================================================================== Package Architecture Version Repository Size =================================================================================================== Upgrading: corosynclib x86_64 3.1.5-4.el9 appstream 55 k Removing dependent packages: corosync x86_64 3.1.5-3.el9 @highavailability 606 k glusterfs-ganesha x86_64 10.2-1.el9s @centos-gluster10 64 k pacemaker x86_64 2.1.2-4.el9 @highavailability 1.2 M pcs x86_64 0.11.1-10.el9 @highavailability 26 M many thanks, L.

1 1

CPE Weekly Update – Week 22 2022
by Lenka Segura 03 Jun '22

03 Jun '22

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

1 0

[NFV SIG] NFV SIG meeting minutes - 2020-06-01
by Alfredo Moralejo Alonso 01 Jun '22

01 Jun '22

============================================= #centos-meeting: NFV SIG meeting - 2020-06-01 ============================================= Meeting started by amoralej at 15:04:02 UTC. The full logs are available athttps://www.centos.org/minutes/2022/June/centos-meeting.2022-06-01-15.04.… . Meeting summary --------------- * FDP update (amoralej, 15:05:35) * new ovn versions have been released https://access.redhat.com/errata/RHBA-2022:4784 https://access.redhat.com/errata/RHBA-2022:4791 (amoralej, 15:06:41) * LINK: https://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/S… (amoralej, 15:08:56) * openvswitch2.17 has been included in last fdp release https://access.redhat.com/errata/RHBA-2022:4789 (amoralej, 15:11:18) * NFV SIG will rebuild it from srpm in ftp.redhat.com until we can get builds from pre-release (amoralej, 15:11:46) * Dominik Holler is leaving the SIG (amoralej, 15:31:10) * Thank dholler for your work on NFV SIG! (amoralej, 15:31:36) * Thanks for reviving the SIG, and to get good ovn and ovs builds to the community! Was a nice experience! (dholler, 15:32:30) Meeting ended at 15:41:13 UTC. Action Items ------------ People Present (lines said) --------------------------- * amoralej (63) * ykarel (15) * eraviv (7) * dholler (6)

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2022