February 2020 - devel - lists.centos.org

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

Packages dropping out of modules
by Paul Clifford 10 Mar '20

10 Mar '20

Earlier this month this was a report that softhsm was available but not installable in CentOS 8 due to a "No available modular metadata for modular package" error. The solution was to enable the idm:DL1 module, but my understanding is that modular packages shouldn't be visible while their modules are disabled (this seems to be the behaviour in RHEL 8). Looking in http://mirror.centos.org/centos/8/AppStream/x86_64/os/Packages/ there are two versions of softhsm in the AppStream repository: * softhsm-2.4.0-2.module_el8.1.0+253+3b90c921.x86_64.rpm * softhsm-2.4.0-2.module_el8.1.0+265+e1e65be4.x86_64.rpm The repository's modules.yaml file only describes one version of the module, idm:DL1:8010020200121181805:4a0acb9a:x86_64, which owns the newer package. When idm:DL1 is enabled this masks the older softhsm version but when it's disabled (the default) the newer package is removed from view, and with no repository metadata to indicate that the older softhsm is part of a module it effectively becomes an ordinary member of the AppStream repository. So "dnf install softhsm" offers two different package versions based on whether or not idm:DL1 is enabled, instead of failing with "Error: Unable to find a match" when the module is disabled. You can see a similar thing with the go-toolset module. It's enabled by default and disabling it should hide all of its packages. Instead, because a second version has been published (see the two versions of go-toolset, golang, etc at the earlier URL), disabling go-toolset makes the previous versions of all the packages appear as ordinary members of the AppStream repository. I found https://bugs.centos.org/view.php?id=16808 from around the time of the 8.0 release querying the lack of older version data, and have commented on it, but I wanted to confirm that I haven't misunderstood the expected behaviour. For example, if nodejs:12 receives an update and the earlier package versions drop out into the main AppStream repository it seems that this might cause conflicts for someone installing nodejs from a third party repository, even if they've disabled nodejs:12.

6 8

Agenda Board of Directors meeting 2012-02-12
by Karsten Wade 04 Mar '20

04 Mar '20

== agenda 2020-02-12 From: https://blog.centos.org/2020/02/agenda-for-centos-board-of-directors-meetin… 1. Do Directors have any questions or concerns about the process being followed to update the CentOS Project logo? Full story in this blog post by Tuomas Kuosmanen: https://blog.centos.org/2020/01/updating-the-centos-logo-and-visual-style/ 1. Specific design concerns should be handled on centos-devel or in the design repo discussion. 2. Having a face-to-face Board and/or leadership meeting in or near Paris in Summer 2020. What month might be good for Directors? 3. Directors and other Project leaders are invited and encouraged to collaborate with the now four community architects from Red Hat working in/around the CentOS Project: Rich Bowen, Brian Exelbierd, Tuomas Kuosmanen, and Karsten Wade. 4. Report out from Karsten on the Board interview/working session room at the Brussels CentOS Dojo. 5. Consent items: 1. Adopt minutes from 2020-01-08 meeting 2. Noting that Fabian Arrotin has resigned his role as a CentOS Project Director as of October 2019. 6. Rolling (last from 2020-01-08): 1. Any other topics aka What other things do you want on our master initiatives list? 2. Stepping-up our meeting norms 3. Transparency initiatives == notes/thoughts Hi all, travel and the awesome CentOS Dojo in Brussels caught me a few days behind on finishing the agenda for this meeting. Honestly, my processes are still evolving over how late to bring in items, keep adding until the last hours, and/or when to call a cut-off and publish. You can read Rich's report of the Dojo here: https://blog.centos.org/2020/02/event-report-centos-dojo-brussels-jan-31-20… Video from Dojo presentations has begun to be available in our YouTube channel: https://www.youtube.com/channel/UC-IoMrffK5xG1UI-skkTlcA -- Karsten Wade [he/him/his]| Senior Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://theopensourceway.org gpg: AD0E0C41 | https://red.ht/sig

2 1

Re: [CentOS-devel] CentOS 8 docker images
by Brian Stinson 29 Feb '20

29 Feb '20

On Wed, Dec 4, 2019, at 13:37, Philippe Mathieu-Daudé wrote: > Hello Brian, > > On 9/27/19 3:29 PM, brian(a)bstinson.com (Brian Stinson) wrote: > > On Thu, Sep 26, 2019, at 22:30, Lance Albertson wrote: > >> When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen? > >> > >> Thanks! > >> > >> [1] https://github.com/CentOS/sig-cloud-instance-images/issues/151 > >> > >> -- > >> Lance Albertson > > > > Here's what we're working through: > > > > We have cloud and container images built, but we currently aren't happy with the base image size produced by our tooling. > > > > Both cloud and container images are in the QA process and we'll get them out as soon as they're ready. > > Any news on this? > > Thanks, > > Phil. `podman pull centos:8` should get you the container images. Cloud images are something we're working through targeting the upcoming Stream 8 and Linux 8.1.1911 releases. --Brian

4 4

CPE Weekly: 2020-02-28
by Aoife Moloney 28 Feb '20

28 Feb '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-02-28 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ## CentOS Updates ### CentOS * 5 updates for el8 * 3 updates for el7 * EPEL7 container image on quay.io for python-tox * Exploring fedora-infra jobs that can be containerized ### CentOS Stream * Composes are now automated * CentOS QA are now consuming compose in the test suite and running against CentOS Linux and Stream! * Building the contributor workflow is still ongoing and we will keep you updated when we make some progress on this ## Fedora Updates * F32 Beta Freeze now on ### Data Centre Move * Old OpenStack instance has now been switched off. * The team are planning the shipping logistics of the equipment across country with Red Hat - measurements, weights, insurance amounts - fun stuff! :) * No changes to our expected dates as per our last posting, but if there are we will make sure to let you know asap. ### AAA Replacement Current functionalities developed to date: * User functionality to join groups * Uhange email address and password * Disable account function * Database access function * We are also currently mapping solution on how best to have users move from the current FAS to the new FAS (potential name incoming!). * The team also came to the end of developing our wireframes and mapping our user experience flow. * Unit tests were carried out regarding password controller and the current codebase. Patrick Uiterijk and Christian Heimes still continue to be a huge help to the team in this project so thank you both sincerely! For our full blog post, check out Ben Cottons weekly For more information regarding outstanding issues, please see here. To view our current scrum board, please see here. ### CI/CD * The team have made good progress on getting monitor-gating to run in staging * This is running completely now and while it fails in some steps but not because of itself, means it is already providing us valuable information :) * The team have sent an email to the devel list presenting our ideas and potential proposal for the changelog and release fields proof of concept - check it out here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ### Sustaining Team * Releng and Infra Freeze for Fedora 32 Beta is now, so if you need changes have them reviewed. * FMN is the main blocking point for the retirement of fedmsg, it is also running on an eol Fedora (28) and the team are working on replacing it. Check out their public thread here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ## Docs ### Misc Updates * Some packaging work to get pagure's dependencies added and built in EPEL8 (remaining: pygit2 and celery) were done this week * boot.fedoraproject.org and keys.fpo to wiki page has been retired * koji is being set up to have rhscl and rhdevtools for EPEL-7 * infra 8664 - newer kernel on aarch64-test machines. * infra 8369 - people css and html broken so a patch has been applied from new contributor and pushed out * Investigations into why fedora 32 branched compose was stuck & it was ostree signing. https://pagure.io/robosignatory/issue/44 https://pagure.io/pungi/issue/1350 * Broken epel8-testing update push was fixed and is now resumed * Rawhide compose failure was investigated https://pagure.io/releng/failed-composes/issue/1023 Was ceph. Filed https://bugzilla.redhat.com/show_bug.cgi?id=1805422 untagged it and refired compose. * Vagrant environment for mbbox was worked on https://github.com/fedora-infra/mbbox/pull/1 * Mbbox was moved to fedora-infra https://github.com/fedora-infra/mbbox * Jms-messaging-plugin PRs merged https://github.com/jenkinsci/jms-messaging-plugin/pull/169 https://github.com/jenkinsci/jms-messaging-plugin/pull/168 * Alternative “holistic heuristic” algorithm for computing releases was implemented https://pagure.io/Fedora-Infra/generate_changelog/pull-request/3 Common Python package, modules and misc cleanup https://pagure.io/Fedora-Infra/generate_changelog/pull-request/4 * Update and complete README was worked on https://pagure.io/Fedora-Infra/generate_changelog/pull-request/5 As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

CBS - CentOS 8 buildroots are now available
by Thomas Oulevey 28 Feb '20

28 Feb '20

Dear CentOS community, After 2 weeks of testing, with the infrastructure team and selected SIGs, C8 buildroots are now available in https://cbs.centos.org If you would like to request a tag please use the "Buildsys" project at: https://bugs.centos.org * During this week I'll review old requests/tickets, but please ping me on IRC if you see no activity. * The next steps ordered by priority: - Tackle the missing -devel packages from C8 that blocks builds for SIGs - Make C8 Stream buildroots available. - distgit integration with koji. - evaluate alternative to mash (koji dist-repo) and/or improve current scripts [1]. - improve the signing process. - evaluate C8 as builder nodes. Thank you for your patience and feedback during the past months. -- Thomas 'alphacc' Oulevey on behalf of the Infrastructure Team. [1]: https://git.centos.org/centos/cbs-tools

3 2

Unshipped -devel packages in CentOS Linux
by Brian Stinson 28 Feb '20

28 Feb '20

Hi Folks, We're gearing up to build the next minor release of CentOS Linux 8 so I thought now would be a good time to revisit the conversation we've been having about what to do with unshipped -devel packages. Just a reminder on a few guiding principles: - The BaseOS, AppStream, and PowerTools repos in CentOS Linux are designed and composed to match Upstream as closely as possible, both in content and behavior - Unshipped devel packages have no defined maintenance lifecycle in Upstream, and especially not in CentOS - We know that some of these devel packages are essential to build applications that the CentOS (and probably EPEL) communities care about. The problems we need to solve if we decide to ship these packages somewhere in a CentOS artifact: - Communicate that these packages are provided as-is and are not meant for runtime dependencies - Provide the packages in a form that is consumable for individuals and the EPEL community I'd like to propose that we create a separate repository, disabled by default that is composed of the -devel packages that we care about, bundled in a module. The name of this repository and the module is up for discussion, but I would like the naming to help with the communication that these are not for general consumption. I'd also like to discuss how we populate this repo/module. It would be easiest to just dump every unshipped package in and move on, but that doesn't help us track which of these packages are truly important outside of building the distro. Shipping *everything* also represents a larger content set to manage if lifecycle issues come up in the future. An alternative would be to store this definition in git (we'll need to do that anyways), and allow folks to make pull requests to include new content, shipping this as a separate repo would let us spin updates on demand. Looking forward to the discussion! -- Brian Stinson CentOS Infra Team

14 29

CentOS website redesign ideas
by Alain Reguera Delgado 27 Feb '20

27 Feb '20

Hi, The CentOS website redesign effort is going on and there is already some code to evaluate at: https://github.com/areguera/centos-jekyll-sites/tree/staging The redesign uses jekyll static site generator, Montserrat typography and the artistic motif we used in CentOS distributions, to highlight the visual connection among these elements. The navigation header and footer changed to use a dark blue background consistent with CentOS artistic motif. On header the logo and link elements were moved from left to center with respective spaces so the left side of the logo and the left side of the content look aligned on left. On footer, links to CentOS About and CentOS Community were displayed along The CentOS Project description. The content is based on what we have now in www.centos.org. I tried to replicate it but there are content still missing (on purpose to see how the "404 Not found page" looks like ;). The written information may need some consistency. For example on page titles, sometimes we write "The CentOS ...", others just "CentOS ...", and others no "CentOS" word at all. The download links are missing on purpose so to bring debate about the way to go here. In the proposed code, we use two cards, one for CentOS Linux and other for CentOS Stream. Each card has tabs inside to organize download information about major releases of each distribution. This organization uses a table to relate architectures, packages, release notes, documentation and end-of-life. These cards are reused both in the home page and the download page, so we only need to change them in a single place (e.g., https://github.com/areguera/centos-jekyll-sites/blob/staging/_includes/cent… ). What's your impressions so far? You are welcome to share your comments, suggestions, and code/design contributions. Thanks, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

3 7

CFP open for Dojo @ Facebook
by Rich Bowen 26 Feb '20

26 Feb '20

The Call for Presentations for the CentOS Dojo at Facebook is now open, and will close in about two weeks - on March 16th We are looking for talks on all CentOS related topics: * Large-scale installations * SIG progress updates * Containers * System management tools (automation, or tools like Cockpit) It's also worth noting that attendees of our FOSDEM Dojo requested more talks about: * Specific CentOS topics, many talks were not very CentOS related and were then duplicated at the nearby FOSDEM * CentOS internals * id management. Integration with active directory * Cloud and storage * Containers * How to get involved and where is help required * How to contribute to CentOS * New features in new releases, process of preparation new releases The Dojo will be held on April 24th, at the Facebook campus. Event details, and links to the Call for Presentations, are at https://wiki.centos.org/Events/Dojo/Facebook2020 -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

CPE: AAA FAS Replacement update
by Sarah Finn 26 Feb '20

26 Feb '20

Hi all, Please see the latest AAA FAS replacement project update below: AAA: FAS replacement project update 2/25/20 The month of February was a very busy month for the CPE AAA team and community contributors working on this initiative. Great progress was made in the development phase of the AAA: FAS replacement build. Sprint 2 and 3 resulted in the completion of multiple user stories which added user functionality to join groups, change email address and password, disable account, database access along with putting a mapping solution in place for users moving from the current FAS to the new FAS (potential name incoming!). We also came to the end of developing our wireframes and mapping our user experience flow. Unit tests were carried out regarding password controller and the current codebase. We received great support from the wider CPE team as well as Patrick Uiterwijk to allow us progress with user stories by gaining permissions and merging PR’s for the integration of CentOS CI. Christian Heimes assisted us greatly with sharing his knowledge regarding FREE IPA and answered numerous questions to allow us to move forward. Sprint 4 began on Thursday the 20th of February. This sprint will focus on development tasks which will include working on FAS Json, Free IPA, API, Fedora Messaging integration, continuous deployment to stage environment, developing a secure coding tool to ensure code adheres to best practice, as well as continuing working on user functionality user stories. Please see our github board here <https://github.com/orgs/fedora-infra/projects/6>to view current activity. We also received some sad news since our last update, that we are losing a team member, Rick Elrod, as he moves on to pastures new with the Ansible team. Rick provided an excellent POC for AAA which is leaving us in good shape to continue on as planned. Thanks Rick and we will hopefully still see you around as a contributor going forward. We also welcomed a new team member Leonardo (Leo) Rossetti who joined at the start of Sprint 4 and has already hit the ground running. Leo is currently working on our FAS JSON user stories. Regarding delivery of AAA, we may look at a phased release , this current phase focus is on the development of AAA to be delivered by 3/31/20. It is looking likely that the deployment of AAA will happen in a later phase due to requiring System Admin assistance. We are likely to gain this on the completion of the Colo Move (which is our planned data center move), approximately in mid April. We are enquiring to see if deploying to staging is possible within this phase to allow for a long testing period. I will provide an update on this in our next blog. The integration of CentOS will be worked on within an additional phase following the completion of AAA centric stories for Fedora. On a final note, I would like to commend the CPE AAA team on their collaboration and productivity throughout this initiative even in the face of unknowns, team changes, cross team dependencies and other challenges, they continued to proactively work together and find solutions to keep this initiative moving forward. We welcome all feedback, thoughts and contributions as we progress through this project. Please feel free to comment on any issue to log your thoughts. For more information regarding outstanding issues, please see here. <https://github.com/fedora-infra/securitas/issues> To view our current scrum board, please see here. <https://github.com/orgs/fedora-infra/projects/6> Thanks all, -- Sarah Finn She/Her Agile Practitioner Red Hat <https://www.redhat.com/> Waterford, Ireland sfinn(a)redhat.com M: 0879830832 @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

1 0

kernel-rt for CentOS 8
by Tim 25 Feb '20

25 Feb '20

Hello there, I'd like to suggest a kernel-rt repo for CentOS 8 like 7 has. Are there any plans? Thanks Tim

1 0

plans & future of OpenStack
by lejeczek 24 Feb '20

24 Feb '20

hi everybody, I want to ask devel about Openstack and/or cloud SIG in near future with regards to Centos 8. Is there any future for it in Centos 8 and if yes then, are there any scheduled releases perhaps? many thanks, L.

3 5

httpd-itk
by Marko Bevc 23 Feb '20

23 Feb '20

Hi. qq, is there a reason httpd-itk package is missing in EPEL? -- Marko

3 4

CPE Weekly: 2020-02-21
by Aoife Moloney 21 Feb '20

21 Feb '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-02-21 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ## Fedora Updates ### Data Centre Move * The F32 Schedule Key has been updated to include data centre move implications: https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html * The F32 Infrastructure has also been updated to include them too: https://fedorapeople.org/groups/schedule/f-32/f-32-infrastructure-tasks.html * If you have an instance in the fedora private openstack cloud that, please remove it, or lose it! This instance will be turned off on 2020-02-27. You have been warned! :) ### AAA Replacement * I forgot **all** the links last week - my bad! So here is the corrected AAA project work - the team are using a kanban board in GitHub, not Jira for their work and their blog post to the Fedora Community Blog is linked. * The team made great progress in sprint 3, completing over 10 tickets! Check out their kanban board here: https://github.com/orgs/fedora-infra/projects/6 * The blog post can also be viewed here: https://communityblog.fedoraproject.org/aaa-fas-replacement-project-update/ * The team meet on Jitsi Monday-Thursday @ 0915-0945 UTC to talk about tickets they are working on (and to see each other :) ) and if you wish to join, the link is here: https://meet.jit.si/FedoraInfraAAAStandups * They also update the #fedora-aaa channel on IRC with updates and chat regularly about the project here too so feel free to join, contribute or just observe! ### CI/CD * The team has managed to get its monitor-gating script deployed and running on openshift in staging and it has already identified an issue with the packager workflow there (in this case in waiverdb, a ticket has been opened upstream to investigate it). * The team wrote a document listing all the ideas they investigated/thought about for dropping changelog and release fields from spec file * The team made a decision on the recommended approach that will be submitted to the devel list for further consideration and inputs. ### Sustaining Team * The ongoings of these ongoings, are ongoing :) * Infra and Releng tickets are reviewed daily (Mon-Fri) in #fedora-admin at 1900UTC. * * Packit integration in the-new-hotness https://github.com/packit-service/packit/issues/689 * * Jms-messaging-plugin reviews https://github.com/jenkinsci/jms-messaging-plugin/pull/169 https://github.com/jenkinsci/jms-messaging-plugin/pull/168 https://github.com/jenkinsci/jms-messaging-plugin/pull/162 * * Compose-tracker now track the time a compose takes, more info here https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ## Docs ### Misc Updates ### Git Forge Requirements * Thank you for your engagement on our Git Forge requirements emails. We have received (a lot of) content from (a lot of) sources both internally and externally. * A decision around the Git Forge is still some time away yet, as this decision impacts so many, but we will keep you up to date on where we are in the process on a weekly basis via this email blast. * Right now we are compiling requirements we have received into a complete set to be able to move to a technical comparison of services between Pagure vs GitHub vs GitLab. * We expect to have the requirements set done by March 11th and will make the requirements available to view as soon as they are all accounted for. * If our dates change, good or bad, we will keep you updated and thank you for your patience and understanding as always! ## CentOS Updates ### CentOS * Tycho module has been unblocked which was needed for jmc * Data is being moved for CentOS Infra and trying a new solution for backups https://github.com/CentOS/ansible-role-centos-backup/commit/e32fb06b74c506c… * VDO was deployed for storage duplication and compression * CentOS CI is stable overall with an updated fedora image and python-tox fix, which is allowing the AAA/Securitas team move forward with integrating CentOS account auth in this project too. ### CentOS Stream * The packit team are trying out the dev/staging instances of git.centos.org * We have been receiving regular updates over the last two days As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Dojo in Boston in September - any interest?
by Rich Bowen 20 Feb '20

20 Feb '20

For the past two years, I've hosted a CentOS Dojo at DevConf.US in Boston. Each time it has been a struggle to find speakers, and then we had pretty poor attendance. This year, DevConf.US (CFP is now open!) has moved away from Boston University, to the Sheraton in Framingham. My question to this audience is whether it's worth our time trying to put together a Dojo to be held on the Tuesday of that event - September 22nd - at that same location. I would need roughly 10 speakers, and about 75 attendees, to make it worthwhile to do this. Please do let me know, either on-list or off-list, if you think you'd be interested in either speaking or attending. For those that don't know, a Dojo is a one-day event featuring technical content from anywhere in the CentOS ecosystem. Details here: https://wiki.centos.org/Events/Dojo Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

SIG Key Needed
by Irina Boverman 20 Feb '20

20 Feb '20

I need keys created for a Messaging Sig. I filled request back in Oct. '19, but it is still outstanding. Can someone assist in creating this key? https://bugs.centos.org/view.php?id=16198 -- Regards, Irina.

4 3

Backport of xfrm kernel bugfix
by Matt Dees 18 Feb '20

18 Feb '20

Hi All! We have been dealing with a memory leak in the kernel for IKEv2 and IPSec connections relating to a memory leak in xfrm support on both el8 and el7. The symptom of this issue is that memory will continue allocating in slab over time making a box oom after too many connections. As per some external discussions I am sending the patch + bug report on to this list. It has already been accepted into upstream kernels (4.19 included) and is a pretty straight forward backport. I have tested and installed this on a few centos8 systems to validate that this does indeed solve the memory leak issue. rbz# 1780470

4 4

CentOS 8 Stream: updated kernel, kmod-kvdo, vdo, createrepo_c, and drpm
by Carl George 18 Feb '20

18 Feb '20

Howdy everyone, The CentOS team is pleased to announce that we have updated the kernel, kmod-kvdo, vdo, createrepo_c, and drpm packages in CentOS 8 Stream. These updates have already been published and are propagating out to the mirror network now. We're hoping to get developer feedback on these packages to help demonstrate the value of Stream and identify any potential issues before they make their way into RHEL and regular CentOS. We've listed some notable features from these updates below. We won't always announce updated Stream packages like this, but we wanted to highlight some of the early successes as we figure out the Stream workflow. Enjoy! # kernel-4.18.0-177.el8 * Reduce preemption network latency in kubernetes * https://github.blog/2019-11-21-debugging-network-stalls-on-kubernetes/ * https://bugzilla.redhat.com/show_bug.cgi?id=1795049 * Fix memory leak on xfrm state destroy * https://lore.kernel.org/netdev/CAMnf+PjGq2qsZzg=+H5Z5kO+PSQbo=R0MHW5rv1CWrq… * https://lists.centos.org/pipermail/centos-devel/2019-December/036366.html # createrepo_c-0.15.1-1.el8 * Allow pip to see installation of python3-createrepo_c * https://github.com/rpm-software-management/createrepo_c/pull/167 * https://bugzilla.redhat.com/show_bug.cgi?id=1695677 * Add support for reading and merging module metadata * https://github.com/rpm-software-management/createrepo_c/pull/146 * Add --pkgorigins mode for Koji * https://github.com/rpm-software-management/createrepo_c/pull/154 -- Carl George

1 0

CPE Weekly: 2020-02-14
by Aoife Moloney 14 Feb '20

14 Feb '20

# CPE Weekly: 2020-02-14 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ## CentOS Updates ### CentOS * Tuning/adding more mirrorlist servers due to EC2/AWS change from last week * Updates are really faster now for CentOS users in AWS/EC2 (more than 100TiB of updated packages served internally with a 98.33% ratio served from cache, so faster than ever) * Moving data from CentOs Infra and switching to a new solution for backup for infra: * https://github.com/CentOS/ansible-role-centos-backup/ * https://github.com/CentOS/ansible-role-restic * VDO (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht…) * Investigating how to incorporate CentOS auth into the new AAA solution * We'll need proper communication plan to ask everybody to get a FAS account when we'll migrate ### CentOS Stream * The CPE team are collaborating with the Packit team internally to develop a workflow for contributor patches * We are working towards demoing a contributor patch from submission to end for Red Hat Summit in April! ## Fedora Updates ### Data Centre Move By June 15th 2020, dedicated Fedora servers will have moved to a new data centre in Northern Virginia. If you want to read more, check out our post on hackmd: https://hackmd.io/@Ap8CkTlpSfmjb44UGV-kWA/rJsk7A-QL Here are some key dates and actions we need you to know: * On 28th Feb, the old OpenStack instance in Fedora Cloud will be retired. * Please reach out to Kevin before 25th Feb if you need to take action for your instance if you are an instance owner. Here is the link to the current status: https://pagure.io/fedora-infrastructure/issue/8614 * On 13th April, the CPE team will begin to ship servers to our new data centre - this does not affect F32 distribution or release * From March 1st, the CPE team will begin to build the Minimum Viable Fedora infrastructure in the new datacenter * Between May 20th - July 1st, we will be redirecting Fedora services to run on the 'MVF' offering to facilitate the final part of the move and allow for re-racking and testing * By July 1st we hope to have BAU (business as usual) for Fedora infra ### AAA Replacement This project is replacing our old existing fas (fedora account system) with a new freeipa based system. * Check out our blog on the teams progress to date! * You can also see our jira board for tickets we are working on * And we have an IRC channel - #fedora-AAA * We are currently working on the FreeIPA API integration and the folks at FreeIPA have been really helpful so far to work with ### CI/CD * The team have been trying to get a local instance of Koji running this week * They are investigating different algorithms that could help generate the next release if a package based on its git history. * Monitoring-gating is being deployed in OpenShift in staging ### Sustaining Team * The team meets daily @ 1900 UTC in #fedora-admin on IRC * The priority work is: ** Fedora 32 ** Assisting with technical debt to facilitate the colo move ** mbbox upgrading ** CentOS CI OpenShift upgrading * The team also have a public thread on knowledge sharing, https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… so take a look! ## Docs * Merged https://pagure.io/fedora-docs/quick-docs/pull-request/175 * Merged https://pagure.io/fedora-docs/quick-docs/pull-request/174 * Merged https://pagure.io/fedora-docs/quick-docs/pull-request/173 * Merged https://pagure.io/fedora-docs/quick-docs/pull-request/167 * Reviewed https://pagure.io/fedora-docs/install-guide/pull-request/40 * Also work underway on CentOS 8.1 docs ### Misc Updates * The team are also working on creating Fedora infra application map - stay tuned for the publication soon! * keys.fedoraproject.org has been turned off * boot.fedoraproject.org will be retired this week * Certs have been changed to letsencrypt for fedorahosted/fedoracommunity * Moved Koji calls to a backend task worker in Bodhi: https://github.com/fedora-infra/bodhi/issues/3061 * kdreyer's playbook repo has been integrated: https://pagure.io/koji-vagrant/pull-request/1 * Testing dist-git repo as a submodule has been added: https://pagure.io/koji-vagrant/pull-request/2 * Ticket in Monitor-Gating has been reviewed: https://pagure.io/fedora-ci/monitor-gating/pull-request/8 As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

[CloudSIG] meeting minutes (2020-02-13)
by Rain Leander 13 Feb '20

13 Feb '20

#centos-meeting: CentOS Cloud SIG meeting (2020-02-13) Meeting started by leanderthal at 15:02:07 UTC (full logs <https://www.centos.org/minutes/2020/February/centos-meeting.2020-02-13-15.0…> ). Meeting summary 1. *roll call o/* (leanderthal <https://www.centos.org/minutes/2020/February/centos-meeting.2020-02-13-15.0…>, 15:02:20) 2. *chair for next week* (leanderthal <https://www.centos.org/minutes/2020/February/centos-meeting.2020-02-13-15.0…>, 15:15:59) 1. *ACTION*: leanderthal to chair next week's cloud sig meeting ( leanderthal <https://www.centos.org/minutes/2020/February/centos-meeting.2020-02-13-15.0…>, 15:16:20) 3. *open floor* (leanderthal <https://www.centos.org/minutes/2020/February/centos-meeting.2020-02-13-15.0…>, 15:16:26) Meeting ended at 15:29:48 UTC (full logs <https://www.centos.org/minutes/2020/February/centos-meeting.2020-02-13-15.0…> ). Action items 1. leanderthal to chair next week's cloud sig meeting Action items, by person 1. leanderthal 1. leanderthal to chair next week's cloud sig meeting People present (lines said) 1. leanderthal (6) 2. centbot (2) -- K Rain Leander OpenStack Community Liaison Open Source Program Office https://www.rdoproject.org/ http://community.redhat.com

1 0

centos-release-ceph-nautilus package for el8
by Giulio Fidente 12 Feb '20

12 Feb '20

hi, storage-sig managed to rebuild / crosstag all ceph nautilus deps into storage8-ceph-nautilus-candidate [1] target thanks to the new el8 buildroot many thanks to all the people who worked hard to get the el8 buildroot working; we're hoping to see soon ceph nautilus tested on el8 in quite a few openstack jobs thanks to the new packages we can't build the centos-release-ceph-nautilus package to provision the .repo files for el8 though [2] because the build target we expected to have for that "core8-extras-common-el8.centos" doesn't exist yet do people have ideas/plans on how to get the -release package built and distributed? thanks! 1. https://cbs.centos.org/koji/builds?order=nvr&tagID=1891&inherited=1&latest=1 2. https://cbs.centos.org/koji/packageinfo?packageID=7290 -- Giulio Fidente GPG KEY: 08D733BA

4 6

fedmsg in centos
by Jan Sakalos 12 Feb '20

12 Feb '20

Hello, I am member of packit team, working on integration packit into centos infrastructure. I would like to ask if there is fedmsg bus implemented in centos infrastructure and if you can provide me with configuration details. -- Thanks, Ján Sakáloš

4 3

Centos 8 TLS libs & tools - then Squid proxy Centos 7
by lejeczek 12 Feb '20

12 Feb '20

hi devel guys, I thought I'd ask here directly for it begins to worry me a bit. What's that? Well.. it's a freshly set up Centos8 box which has no direct way out but via Squid proxy(Centos7 squid-3.5.20-12.el7_6.1.x86_64) and it seems that lots of things do not want to work, eg.: $ podman search centos ERRO[0000] error searching registry "registry.fedoraproject.org": couldn't search registry "registry.fedoraproject.org": error pinging docker registry registry.fedoraproject.org: Get https://registry.fedoraproject.org/v2/: proxyconnect tcp: tls: first record does not look like a TLS handshake ERRO[0000] error searching registry "docker.io": couldn't search registry "docker.io": error pinging docker registry index.docker.io: Get https://index.docker.io/v2/: proxyconnect tcp: tls: first record does not look like a TLS handshake ERRO[0000] error searching registry "registry.access.redhat.com": couldn't search registry "registry.access.redhat.com": error pinging docker registry registry.access.redhat.com: Get https://registry.access.redhat.com/v2/: proxyconnect tcp: tls: first record does not look like a TLS handshake ERRO[0000] error searching registry "registry.centos.org": couldn't search registry "registry.centos.org": error pinging docker registry registry.centos.org: Get https://registry.centos.org/v2/: proxyconnect tcp: tls: first record does not look like a TLS handshake Another example is R from EPEL, installing any package/library in R also fails in similar way and at Squid's end I get lots of: ... 1581503634.209 1 10.5.8.17 TAG_NONE/400 4300 %1F%8Dl%E4%C9z%CFD$%ED%87%EF%A9%F4%F7%05%E7%9Cja%E8%23Y%B5%A5%EBb%7BT%8F%B4 - HIER_NONE/- text/html 1581503634.211 1 10.5.8.17 TAG_NONE/400 4315 NONE error:invalid-request - HIER_NONE/- text/html 1581503634.211 0 10.5.8.17 TAG_NONE/400 4120 &%AFi%BB%1A%AD%03%9C - HIER_NONE/- text/html 1581503634.211 0 10.5.8.17 TAG_NONE/400 4270 T%88vH5%BAw%EE%FB%1F9%DE%D5%B9%90%C7%05?%F1%D6%22%E3%5B%8F%7F%7C%E6 - HIER_NONE/- text/html 1581503634.212 0 10.5.8.17 TAG_NONE/400 4300 %85S%80%BAKh%8E%AB+%90%D4%8Ad%F0%B4%EB%C1or%5E%BEY%800+%F8%98%AF%04!%97%F0 - HIER_NONE/- text/html 1581503634.212 0 10.5.8.17 TAG_NONE/400 4192 %DA%E6%9E3%DB%9AP%E0q%A3%89c%BBeO%C2%A5%0F - HIER_NONE/- text/html 1581503634.213 0 10.5.8.17 TAG_NONE/400 4074 %1Ej%8D%17 - HIER_NONE/- text/html 1581503634.213 0 10.5.8.17 TAG_NONE/400 4564 NONE error:invalid-request - HIER_NONE/- text/html 1581503663.358 529 10.8.9.208 TCP_TUNNEL/200 4442 CONNECT v10.events.data.microsoft.com:443 - HIER_DIRECT/52.114.128.10 - 1581503708.562 1 10.5.8.17 TAG_NONE/400 4300 %EF%1E%F9%10:%9E%CE(%85%F4%CD%DEc%809%0EnU%BD%E3%9F@%14%8C%FF!%03%7C?*%B5l - HIER_NONE/- text/html 1581503708.563 1 10.5.8.17 TAG_NONE/400 4315 NONE error:invalid-request - HIER_NONE/- text/html 1581503708.564 0 10.5.8.17 TAG_NONE/400 4315 %9D%7D%17.%D0%F4%B2%C9%B6V%8E%B5%BB%10X%AF%F1%E3g%3C%14%90%C2%F7%AF%E6P%19%1D6%98%C1%DB - HIER_NONE/- text/html 1581503708.564 0 10.5.8.17 TAG_NONE/400 4242 -N%08,%3E.%93%F87l%0F%7F%89G%0E%1C%A0%A7%90%DF%8A+%D9%E4c - HIER_NONE/- text/html 1581503708.565 1 10.5.8.17 TAG_NONE/400 4315 %D1f%E3%891%EA%86%07%07%B7%EEu%BF%83F%AD%E4%A2%FB7%CE%ACw%1Cf*%E2%FD%BD%9A%5E%07 - HIER_NONE/- text/html 1581503708.565 0 10.5.8.17 TAG_NONE/400 4315 NONE error:invalid-request - HIER_NONE/- text/html 1581503708.565 0 10.5.8.17 TAG_NONE/400 4280 %A3%13%EE%D9%5CIfKzS%F39x%AB%CE%F8%D0A%D7Y%8A4%C17%FC%9A%B9%98%87%CBz - HIER_NONE/- text/html 1581503708.566 0 10.5.8.17 TAG_NONE/400 4174 %C1;%A4q%8E%81%E6%CE%E1%DC%81N%1D%F0 - HIER_NONE/- text/html Everything else seems to work fine, a small group of Centoses 7 use that Squid just fine, Windows boxes too. Would you share any thoughts as to what might be going on there? many thanks, L.

4 4

a problem with "ca-certificates" rpm?
by lejeczek 12 Feb '20

12 Feb '20

hi guys, Anything I try to do with dnf and outside what 'centos', eg. adding a gluster repo or any third-party repo I get: ... [MIRROR] rdo-release.rpm: Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://rdoproject.org/repos/rdo-release.rpm [SSL certificate problem: certificate is not yet valid] [FAILED] rdo-release.rpm: Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://rdoproject.org/repos/rdo-release.rpm [SSL certificate problem: certificate is not yet valid] ... Any ideas, suggestions on why centos is not happy that way? many thanks, L.

2 2

npm install issue in docker CE using Cent OS 8
by Amey Abhyankar 10 Feb '20

10 Feb '20

Hello, I am trying to run a Dockerfile with 'npm install' but getting errors. Version details as follows = Cent OS version: 8 Docker CE version: 19.03.4 Dockerfile: ------------------------------------- # Create image based on the official Node 10 image from dockerhub FROM node:10.16.3 # Create a directory where our app will be placed RUN mkdir -p /app # Change directory so that our commands run inside this new directory WORKDIR /app # Copy dependency definitions COPY package*.json /app/ # Install dependecies RUN npm cache clear --force RUN npm install -verbose # Get all the code needed to run the app COPY . /app/ # Expose the port the app runs in EXPOSE 4200 # Serve the app CMD ["npm", "start"] ------------------------------------- Error: ------------------------------------- Step 6/9 : RUN npm install -verbose ---> Running in f6cf6cf24712 npm info it worked if it ends with ok npm verb cli [ '/usr/local/bin/node', npm verb cli '/usr/local/bin/npm', npm verb cli 'install', npm verb cli '-verbose' ] npm info using npm(a)6.9.0 npm info using node(a)v10.16.3 npm verb npm-session 8c25dbc16da110c3 npm info lifecycle app01-uiapp(a)0.0.0~preinstall: app01-uiapp(a)0.0.0 npm timing stage:loadCurrentTree Completed in 20ms npm timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms npm timing stage:loadIdealTree:loadShrinkwrap Completed in 1768ms npm timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 2534ms npm timing stage:loadIdealTree Completed in 5336ms npm timing stage:generateActionsToTake Completed in 1623ms npm verb correctMkdir /root/.npm/_locks correctMkdir not in flight; initializing npm verb makeDirectory /root/.npm/_locks creation not in flight; initializing npm verb lock using /root/.npm/_locks/staging-bd3355550c5a469e.lock for /app/node_modules/.staging npm timing action:extract Completed in 315443ms npm verb unlock done using /root/.npm/_locks/staging-bd3355550c5a469e.lock for /app/node_modules/.staging npm timing stage:rollbackFailedOptional Completed in 3ms npm timing stage:runTopLevelLifecycles Completed in 323677ms npm verb type system npm verb stack FetchError: request to https://registry.npmjs.org/core-js/-/core-js-3.6.4.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443 npm verb stack at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14) npm verb stack at ClientRequest.emit (events.js:198:13) npm verb stack at TLSSocket.socketErrorListener (_http_client.js:392:9) npm verb stack at TLSSocket.emit (events.js:198:13) npm verb stack at emitErrorNT (internal/streams/destroy.js:91:8) npm verb stack at emitErrorAndCloseNT (internal/streams/destroy.js:59:3) npm verb stack at process._tickCallback (internal/process/next_tick.js:63:19) npm verb cwd /app npm verb Linux 4.18.0-80.11.2.el8_0.x86_64 npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-verbose" npm verb node v10.16.3 npm verb npm v6.9.0 npm ERR! code EAI_AGAIN npm ERR! errno EAI_AGAIN npm ERR! request to https://registry.npmjs.org/core-js/-/core-js-3.6.4.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443 npm verb exit [ 1, true ] npm timing npm Completed in 624434ms npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2020-02-10T04_26_38_115Z-debug.log The command '/bin/sh -c npm install -verbose' returned a non-zero code: 1 ------------------------------------- Other details: I can ping/wget the tgz file from base Cent OS 8 machine that means it's not the DNS issue. Any hints how to fix this issue? Thanks. Regards, Amey.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2020