December 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

Discussion: Open technical questions concerning SIG content for RHEL releases
by Peter Georg 09 Jun '23

09 Jun '23

Dear all, There has been an inquiry to the CentOS Board to clarify how long SIGs can expect to be able to build against RHEL build targets [1]. This is necessary to allow SIGs themselves to communicate expected lifecycle of their content to users. The outcome of this, in summary, is that SIGs should be able to build against RHEL until it reaches EOL (end of Maintenance Phase) + 30 days (no access to ELS content). This policy follows the one used by EPEL. Note: It is (obviously) still up to every single SIG to decide if and for how long they want to support a particular RHEL (or CentOS Stream) release. This inquiry also included respectively raised some technical questions. These technical questions are not to be decided by the CentOS Board. In [2] it has been recommended to discuss these on centos-devel. So let's do that. I want to start with two open questions which I do know of. In case there are other open question concerning this matter please raise them here. First open question is where to push content produced by SIGs for RHEL8 to. To better understand the issue, let me summarize the current situation, for which we first need to define the used format for tags in CBS: <sig><el>-<project>-<version>-{candidate,testing,release} where <el> can currently be 7,8,8s,9,9s Packages tagged for -testing are pushed to: https://buildlogs.centos.org/centos/<el>/<sig>/<arch>/<project>-<version>/ Packages tagged for -released are push to: If el = 8 or 8s: debuginfo rpm packages: https://debuginfo.centos.org/centos/<el>/<sig>/<arch>/<project>-<version>/ src.rpm packages: https://vault.centos.org/centos/<el>/<sig>/Source/<project>-<version>/ Everything else: http://mirror.centos.org/centos/<el>/<sig>/<arch>/<project>-<version>/ If el = 9 or 9s: http://mirror.stream.centos.org/SIGs/<el>/<sig>/<arch>/<project>-<version>/ For src.rpm <arch> is source. Note: Although it is not relevant for the discussion, in fact on the mirrors the suffix "s" of <el> is replaced by "-stream". This currently is all fine. However it is planned that the infrastructure currently used for packages built for 8 or 8s will disappear once CentOS Stream 8 and CentOS Linux 7 are EOL (June 30th, 2024). So in case any SIG decides to produce content for RHEL 8 after that date packages can not be distributed properly anymore. Only using the -testing tag and thus https://buildlogs.centos.org is not really an option as it would probably produce too much load on these. My proposal: After CentOS Stream 8 went EOL (May 31st, 2024), which is the same date as the end of the Full support phase of RHEL 8, at least the -release tag of all RHEL 8 build targets is locked and SIGs have to opt-in in case they want to build content for RHEL 8 during its Maintenance Support phase (End: May 31st 2029) for a particular build target. For these, tagging for -release will then push content to http://mirror.stream.centos.org/SIGs/8/<sig>/<arch>/<project>-<version>/, i.e. the same location as used for 9 and 9s. This gives SIGs one month for all required changes before the currently infrastructure disappears. Of course this means additional work for SIGs and Infra. However at some point the location where to push content to has to be changed before the currently used infrastructure disappears. Choosing an earlier date would result in work for SIGs who do not want to continue providing any packages once RHEL 8 enters Maintenance Support phase anyway. The second open question concerns the centos-release-* packages provided by SIGs to allow users to easily consume SIGs' content. For 8s and 9s the CBS tags extras<el>-extras-common-{candidate,testing,release} are used to build these packages. This repository is added in CentOS Stream 8 and 9. For packages build for RHEL 8 and 9 there is currently no common way to provide any means of easing the process to consume SIGs' content. My proposal to fix this is by adding extras<el>-extras-common-{candidate,testing,release} for <el> = 8 and 9, i.e., using the same system as currently used for 8s and 9s. To further ease the process I propose to introduce a package named centos-release-extras which contains the repository config pointing to the content of the tags extras<el>-extras-common-{testing,release} (only -release enabled by default) and the CentOS-SIG-Extras GPG key. The centos-release-extras packages itself would be built in the extras<el>-extras-common-el<el> build target. Users of RHEL would then only need to install this single package to allow them to easily install any other centos-release-* packages. Obviously someone needs to maintain the centos-release-extras package. I volunteer to maintain this package. [1]: https://git.centos.org/centos/board/issue/82 [2]: https://pagure.io/centos-infra/issue/1002

4 11

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

Fedora/CentOS planned outage 2022-12-08 19:00 UTC
by Stephen Smoogen 10 Jan '23

10 Jan '23

lanned Outage - IAD2 Outage - 2022-12-08 19:00 UTC There will be an outage starting at 2022-12-08 19:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2022-12-08 19:00 UTC' Reason for outage: There will be a multi hour outage as a hardware firewall is changed out of the IAD2 data center where most Fedora systems are housed. Outages should be in short cycles as the firewall is changed over to new hardware and rules are tested and confirmed. Affected Services: Most Fedora and CentOS Services will be affected Build systems for s390x will need to be restarted as NFS will break Builds in CentOS Stream and other infrastructure will be blocked during this time. Ticket Link: https://pagure.io/fedora-infrastructure/issue/NNNN Please join #fedora-admin or #fedora-noc on irc.libera.chat or add comments to the ticket for this outage above. -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

2 5

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

Alt Images SIG meeting minutes (2022/12/22)
by Troy Dawson 22 Dec '22

22 Dec '22

Meeting summary --------------- * Image build systems: livecd and kiwi - Infra ticket to create build targets in CBS https://pagure.io/centos-infra/issue/988 -- Looks like nothing is going to happen until next year. But it looks like it will be done before the ImageBuilder stuff happens. - koji is not importing all the comps stuff needed -- https://pagure.io/koji/issue/3626 -- koji skips environment and category groups when importing the comps files. -- The workaround it to use just regular groups for everything. It's alot more work, but at least it is possible. - Neal's backport of the upstreamed kiwi-live feature to support automatic persistent overlays on live USBs was merged into RHEL 9's dracut and it should be in c9s now: https://kojihub.stream.centos.org/koji/buildinfo?buildID=27844 -- Some anaconda patches/fixes are needed so this doing break installations from livecd's. * Image build systems: ImageBuilder - Infra ticket to create build targets in CBS https://pagure.io/centos-infra/issue/971 -- Not expected to get any movement from infra until next year. * Open Floor - Clarified that meetings are twice a month, on the 2nd and 4th Thursday -- Next meeting will be on January 12, 2023 at the usual time. People Present (lines said) --------------------------- * tdawson (66) * Eighth_Doctor (42) * davide (9) * davdunc[m (8) * salimma (6) * centguard (5) * rcallicotte (5) * michel-slm (0 Minutes and Log --------------- https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-22-19.0… https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-22-19.0… https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-22-19.0…

1 0

Changes to CentOS CI: New OpenShift instance and Updates
by Camila Granella 22 Dec '22

22 Dec '22

*TL;DR: new OpenShift instance is up and running for CentOS CI, migrate your workloads by March 31st, 2023. Test your access to both the Duffy API and the new OpenShift instance by the end of 2022. CentOS CI changes approaching the end of Phase 3. * Hello everyone, We are happy to announce that the new OpenShift instance is up and running (ticket [0]). For the tenants that opted in to continue using CentOS CI, you are being required to *migrate your workload to the new OpenShift instance by the end of Q1CY23*, with the final deadline being *March 31st, 2023*. In order to support you through the migration process, the team has created a quick guide that can be found in [1]. We would also like to request you test your access to both the Duffy API and the new OpenShift instance by the *end of 2022*. Please reach out to us in case it is not working. Here is the link to the new OCP cluster [2]. As a reminder, this new OCP cluster is running in AWS, on top of EC2 instances, so coming with different limitations when compared with “on-premises bare-metal OCP deployments”. One notable change is that it is not possible to expose /dev/kvm and so there is no way for tenants to deploy VMs through OpenShift (like with the kubevirt operator or else). Tenants having a need to use VMs can then request some through Duffy API. Finally, here's a friendly reminder of the CentOS CI changes' current status. According to our previous communications [3], we are approaching the end of the last phase of the changes that have been implemented to CentOS CI. *Phase 3 - Decommission* - 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 For a full description of the project phases, you can check [3]. Please, feel free to reach out to us in case you have any questions or concerns. Regards, [0] https://pagure.io/centos-infra/issue/969 [1] https://sigs.centos.org/guide/ci/#migration-to-new-ci-instance [2] https://console-openshift-console.apps.ocp.cloud.ci.centos.org/ [3] https://lists.centos.org/pipermail/ci-users/2022-June/004547.html -- 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/>

2 1

CentOS Connect Schedule
by Shaun McCance 21 Dec '22

21 Dec '22

The full schedule for CentOS Connect at FOSDEM is up with 14 amazing talks. CentOS Connect is a free mini-conference on topics across the Enterprise Linux ecosystem. If you're coming to FOSDEM, come in a day early and join us. Registration is free but strongly recommended. Hope to see you there. https://connect.centos.org/

2 1

FreeIPA / Samba / SSSD - new packages same problems
by lejeczek 21 Dec '22

21 Dec '22

Hi gents. It seems this has been a routine - each time when either sssd or Samba or FreeIPA gets new releases (with freeIPA deployed) there will be 'rpm' conflicts: Problem 1: package sssd-common-pac-2.7.3-5.el8.x86_64 requires libndr.so.2()(64bit), but none of the providers can be installed - package sssd-common-pac-2.7.3-5.el8.x86_64 requires libndr.so.2(NDR_0.0.1)(64bit), but none of the providers can be installed - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.4-2.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.3-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.4-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-3.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-4.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-5.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-8.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.1-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.2-1.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.4-1.el8.x86_64 - cannot install the best update candidate for package sssd-common-pac-2.7.3-4.el8.x86_64 - cannot install the best update candidate for package samba-client-libs-4.16.4-2.el8.x86_64 Problem 2: package sssd-idp-2.7.3-4.el8.x86_64 requires sssd-common = 2.7.3-4.el8, but none of the providers can be installed - package libsss_autofs-2.7.3-5.el8.x86_64 conflicts with sssd-common < 2.7.3-5.el8 provided by sssd-common-2.7.3-4.el8.x86_64 - cannot install the best update candidate for package sssd-idp-2.7.3-4.el8.x86_64 - cannot install the best update candidate for package libsss_autofs-2.7.3-4.el8.x86_64 Problem 3: package sssd-common-pac-2.7.3-5.el8.x86_64 requires libndr.so.2()(64bit), but none of the providers can be installed - package sssd-common-pac-2.7.3-5.el8.x86_64 requires libndr.so.2(NDR_0.0.1)(64bit), but none of the providers can be installed Or it's just me? many thanks, L.

6 10

dnf stuff has broken dependencies
by Leon Fauster 19 Dec '22

19 Dec '22

FYI: The samba issue is gone but following is still an issue: # LANG=C yum update Last metadata expiration check: 0:00:18 ago on Fri Nov 25 23:48:00 2022. Dependencies resolved. Problem 1: package python3-dnf-plugin-modulesync-4.0.21-14.1.el8.noarch requires python3-dnf-plugins-core = 4.0.21-14.1.el8, but none of the providers can be installed - cannot install both python3-dnf-plugins-core-4.0.21-16.el8.noarch and python3-dnf-plugins-core-4.0.21-14.1.el8.noarch - cannot install the best update candidate for package python3-dnf-plugins-core-4.0.21-14.1.el8.noarch - cannot install the best update candidate for package python3-dnf-plugin-modulesync-4.0.21-14.1.el8.noarch Problem 2: problem with installed package python3-dnf-plugin-modulesync-4.0.21-14.1.el8.noarch - package python3-dnf-plugin-modulesync-4.0.21-14.1.el8.noarch requires python3-dnf-plugins-core = 4.0.21-14.1.el8, but none of the providers can be installed - cannot install both python3-dnf-plugins-core-4.0.21-16.el8.noarch and python3-dnf-plugins-core-4.0.21-14.1.el8.noarch - package dnf-plugins-core-4.0.21-16.el8.noarch requires python3-dnf-plugins-core = 4.0.21-16.el8, but none of the providers can be installed - cannot install the best update candidate for package dnf-plugins-core-4.0.21-14.1.el8.noarch ============================================================================================================================================================================= Package Architecture Version Repository Size ============================================================================================================================================================================= Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): python3-dnf-plugins-core noarch 4.0.21-16.el8 baseos 258 k Skipping packages with broken dependencies: dnf-plugins-core noarch 4.0.21-16.el8 baseos 75 k Transaction Summary ============================================================================================================================================================================= Skip 2 Packages Nothing to do. Complete! -- Leon

2 2

CPE Weekly Update – Week 50 2022
by Lenka Segura 16 Dec '22

16 Dec '22

*Hi everyone,* *Reminder: This is the last email we are sending! If you want to stay in touch with the CPE updates, please follow the instructions at the bottom.* *This is a weekly report from the CPE (Community Platform Engineering) Team.The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-50-2022/ <https://communityblog.fedoraproject.org/cpe-weekly-update-week-50-2022/>If you want to receive weekly reports by email in the future, please subscribe to either https://communityblog.fedoraproject.org/ <https://communityblog.fedoraproject.org/> or https://discussion.fedoraproject.org/c/news/commblog/61 <https://discussion.fedoraproject.org/c/news/commblog/61>. We will stop sending them in 2023.Regards,CPE Team*

2 1

Fwd: [CentOS] CentOS 7: Missing Thunderbird Updates
by Chris Schanzle 16 Dec '22

16 Dec '22

[No response on CentOS list, so trying CentOS-devel.] -------- Forwarded Message -------- Subject: [CentOS] CentOS 7: Missing Thunderbird Updates Date: Mon, 21 Nov 2022 15:33:56 -0500 From: Chris Schanzle via CentOS <centos(a)centos.org> Reply-To: Chris Schanzle <christopher.schanzle(a)nist.gov>, CentOS mailing list <centos(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Hi, Looks like CentOS 7 hasn't shipped Thunderbird updates for a while. The latest I see in repos is: Sep 1 15:22 thunderbird-91.13.0-1.el7.centos.x86_64.rpm Perusing through the RHEL announcements, that was from the RHSA-2022:6169-01 on 2022-08-24. Seems none of the 102.x versions have shipped: 2022-09-26 RHSA-2022:6710-01 thunderbird-102.3.0-3.el7_9.x86_64.rpm 2022-10-18 RHSA-2022:6998-01 thunderbird-102.3.0-4.el7_9.x86_64.rpm 2022-10-25 RHSA-2022:7184-01 thunderbird-102.4.0-1.el7_9.x86_64.rpm And for completeness, just announced today: 2022-11-21 RHSA-2022:8555-01 thunderbird-102.5.0-2.el7_9.x86_64.rpm Thanks in advance for efforts to find and clear the blockage!

6 19

RFC: CentOS Project Mission statement
by Patrick Riehecky 15 Dec '22

15 Dec '22

As part of the on-boarding process each Special Interest Group is expected to provide their mission/objectives. The CentOS Project itself doesn't currently have one. I'd like to rectify that. In part because I don't want to ask folks to do something we've not done ourselves. And in part because I find these sorts of statements somewhat handy. Explaining the current role of CentOS within the ecosystem currently tends to point towards longer documents with useful details. A short but to the point Mission Statement could help provide a quick explanation of our objectives without the challenge of keeping the technical details up to date. As members of the community, the board would like your help improving this draft statement to better reflect your understanding of the CentOS Project mission. --- Draft Mission Statement CentOS aims to make Enterprise Linux better by providing project resources for contributors with similar interests to collaborate or communicate about the experience for everyone within our ecosystem. Whether it is artwork, development, discussion, or troubleshooting - CentOS should provide a clear way to get involved for contributors of all skill and interest levels. --- Initial discussion and board ticket : https://git.centos.org/centos/board/issue/85

1 1

Adding ACL for rsync.stream.centos.org (like we always did for msync.centos.org)
by Fabian Arrotin 13 Dec '22

13 Dec '22

Forwarding here (but in readable format) what was sent to centos-mirror-announce list (where all public mirrors are normally subscribed), so sending to centos-devel for awareness : Just this little mail to announce that we have now put in place the same mechanism to only allow registered third-party mirrors to pull/rsync from us. (ticket https://pagure.io/centos-infra/issue/999) Due to lack of bandwidth/resources and also sponsored nodes disappearing (and so remaining sponsored infra being overloaded with requests), we had to adapt the process to also have ACL in place for CentOS Stream 9 (as it was already documented for years on https://wiki.centos.org/HowTos/CreatePublicMirrors) to only allow ip address[es] (ipv4 and ipv6) from these registered mirrors (https://pagure.io/centos-infra/issues?status=Closed&tags=mirrormanager&clos…) Should you suddenly be blocked (because you are now using a different ip that differs from the one you added in your initial ticket on centos-infra tracker), feel free to create ticket to request the ip to be updated in our ACL. Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Fwd: [CentOS-mirror-announce] Adding ACL for rsync.stream.centos.org (like we always did for msync.centos.org)
by Fabian Arrotin 13 Dec '22

13 Dec '22

FYI -------- Forwarded Message -------- Subject: [CentOS-mirror-announce] Adding ACL for rsync.stream.centos.org (like we always did for msync.centos.org) Date: Tue, 13 Dec 2022 10:12:16 +0100 From: Fabian Arrotin <arrfab(a)centos.org> Reply-To: Announcements to mirror admins from the CentOS team <centos-mirror-announce(a)centos.org> To: centos-mirror-announce(a)centos.org

1 0

Infrastructure SIG Meeting Summary, Next Meeting Agenda
by Aoife Moloney 12 Dec '22

12 Dec '22

# CentOS Infra SIG bi-weekly meeting summary Hi All, The Infrastructure SIG has changed our meeting times and cadences and in an effort to be more transparent, we/I are going to be sending out a summary after every meeting and also details on when the next meeting will be, joining details and the main topic(s) we will be discussing. Our most recent Infra SIG meeting was on Wednesday November 30th. Below is a short summary of the discussion: ## Summary from 2022-11-30 * Reminder to migrate your tenancy to the new AWS cluster [[see email]( https://lists.centos.org/pipermail/centos-devel/2022-November/120674.html) in December * The ticket for ImageBuild on CBS [[971]( https://pagure.io/centos-infra/issue/971) is not prioritized for December due to other work items in flight ## Next Meeting Agenda (2022-12-14) * Zuul for CentOS Stream to possibly address integration testing - anyone with an interest in this conversation are welcome to join * AOB ### Next Meeting Time & joining details: * Wednesday 14th Dec @ 12:30pm UTC+1 * Google Meet: meet.google.com/sgb-ubrz-vzz or Join by phone ‪(IE) +353 1 571 1000‬ PIN: ‪360 311 061 1805‬# Kindest regards, Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA <https://www.redhat.com> Communications House Cork Road Waterford <https://www.redhat.com>

1 0

CPE Weekly Update - Week 49 2022
by Michal Konecny 09 Dec '22

09 Dec '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-49-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in 2023. Regards, CPE Team

1 0

Alt Images SIG meeting minutes (2022/12/08)
by Troy Dawson 08 Dec '22

08 Dec '22

Meeting summary --------------- * Image build systems: livecd and kiwi - Infra ticket to create build targets in CBS https://pagure.io/centos-infra/issue/988 -- Looks like we need to wait at least another week before work starts on this. - Eighth_Doctor starting to work on getting configs into our SIG repos * Image build systems: ImageBuilder - Infra ticket to create build targets in CBS https://pagure.io/centos-infra/issue/971 -- Not expected to get any movement from infra until next year. * Open Floor - Decided to change meetings from weekly to bi-weekly. -- Next meeting will be on December 22 at the usual time. People Present (lines said) --------------- * tdawson (39) * michel-slm (13) * davide (6) * Eighth_Doctor (6) * centguard (5) * rcallicotte (0) Minutes and Log --------------- https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-08-19.0… https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-08-19.0… https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-08-19.0…

1 0

[CloudSIG] CentOS Cloud SIG meeting (2022-12-08)
by Christian Glombek 08 Dec '22

08 Dec '22

========================== #centos-meeting: Cloud SIG ========================== Meeting started by lorbus at 15:02:22 UTC. The full logs are available athttps://www.centos.org/minutes/2022/December/centos-meeting.2022-12-08-15… . Meeting summary --------------- * LINK: https://etherpad.opendev.org/p/centos-cloud-sig (lorbus, 15:05:22) * RDO/OpenStack Update (lorbus, 15:06:43) * OKD/SCOS Update (lorbus, 15:09:41) * a new OKD/SCOS preview release has been done (lorbus, 15:10:29) * LINK: https://github.com/okd-project/okd-scos/releases/tag/4.12.0-0.okd-scos-2022… (lorbus, 15:10:34) * Documentation Update (lorbus, 15:15:49) * Open Floor (lorbus, 15:17:29) * LINK: https://blog.centos.org/2022/11/centos-community-newsletter-november-2022/ (lorbus, 15:18:32) * Christian Glombek is assuming the role of Cloud SIG co-chair (lorbus, 15:19:01) Meeting ended at 15:24:54 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * lorbus (28) * centguard (4) * davdunc[m (1) * davdunc (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Storage-SIG] Ceph 16.2.10 on el8
by Luis Domingues 08 Dec '22

08 Dec '22

Hi, On some servers that are running a variant of el8, we have ceph installed using the Storage-SIG repos. We saw that 16.2.10 packages are only built for 8-stream and 9-stream. Is building packages for el8 completely stopped? I did not found any information about Storage SIG dropping el8 support. Thanks, Luis

2 1

epel-release-8-11 in extras VS epel-release-8-18 in epel
by Leon Fauster 07 Dec '22

07 Dec '22

Hey, would it make sense updating the epel-release-8 in extras repo? While doing some new EL8 deployments I had some hassle ... :-) -- Thanks, Leon

1 0

dnf-makecache.service failing every few days and dnf-automatic.service samba sssd issues (again).
by Jelle de Jong 06 Dec '22

06 Dec '22

Hello everybody, 1. I got many systems with failing dnf-makecache.service because some mirror/repo is tried once and fails. Is there an option to make dnf more reliable, to try the mirror url a few times and check its availability? man yum.conf does not # cat /etc/yum.conf [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True best=True skip_if_unavailable=False ExecStart=/usr/bin/dnf makecache --timer 2. I saw in the mailing list the messages about samba sssd dependency issues. I got lots of servers failing my dnf-automatic because of this when can I expect a resolution for this? Kind regards, Jelle

1 2

unscheduled outage (resolved): cbs.centos.org
by Fabian Arrotin 05 Dec '22

05 Dec '22

Just for awareness : I noticed this morning through monitoring that the cache/proxy used by kojid builders (needed to reach out to gitlab/etc) was down during the night, so while kojihub itself was available, the kojid nodes weren't even checking in. I quickly reconfigured (with ansible) another caching proxy and so restored connectivity. If you noticed some build issues during some hours, please resubmit these, but it seems most were just queued and so picked up "normally" as soon as connection was restored. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

3 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel December 2022