devel January 2021

devel@lists.centos.org

71 participants
46 discussions

RFC: Stream Kernel SIG Proposal
by redbaronbrowser 19 May '21

19 May '21

There are four main goals of this SIG: First, break down changes in the Stream version 4.18.0 kernel into individual patches. When possible, document the source the patch is from and the purpose of the patch. Moving forward also document which Stream kernel package revision introduced the patch. Second, build CentOS Plus kernel for Stream. Third, package newer LTS kernels during the LTS lifespan. These would be available as alternative kernels for Stream similar to the CentOS Plus kernel. Fourth, work on tools for better delivery of live security patches to be applied via kpatch. The reasoning for this SIG is to improve the openness of kernels available through Stream. Normally a distribution upstream would have access to which patch or commit each addition to the kernel belongs to. The patch name or commit comment would also give information as to the purpose of the patch. Stream's kernel reports to be 4.18.0 but uses a tar that is 110% the size of a true 4.18.0 tar. A breakdown of the additional 10% is not provided. Hence Stream's kernel still functions similar to a downstream rather than providing what is expected for a successful upstream project. This SIG would help close the kernel openness gap by documenting the changes. Stream users would then be in a better position to track down individual patches that cause regressions or bugs. This SIG would also help smooth the adoption of Stream for users that depend on CentOS Plus kernel features. Next, this SIG should help improve feedback to the LTS kernel developers. Tracking LTS kernel changes may also help with documenting some changes in the primary Stream kernel. Lastly, this SIG should help improve kernel security by promoting methods to enable kernel security updates even when a reboot of the system is not possible.

12 42

centos-release-stream.x86_64 VS centos-stream-release.noarch
by lejeczek 13 Feb '21

13 Feb '21

Hi devel Is that not something that needs looking into? -> $ dnf search release | grep -i strea Last metadata expiration check: 0:07:24 ago on Thu 28 Jan 2021 09:46:52 GMT. centos-release-stream.x86_64 : CentOS-Stream release file centos-stream-release.noarch : CentOS Stream release files Installing one package and not the other messes things a bit. regards, L.

4 5

CBS default maven module for virt8-ovirt-44-el8
by Sandro Bonazzola 05 Feb '21

05 Feb '21

Hi, I'm seeing the following error: Executing: xmvn --batch-mode --offline -Dmaven.test.skip=true -Dworkspace.root.dir=/builddir/build/BUILD/apache-sshd-2.6.0 package org.fedoraproject.xmvn:xmvn-mojo:install org.fedoraproject.xmvn:xmvn-mojo:javadoc org.fedoraproject.xmvn:xmvn-mojo:builddep ['xmvn', '--batch-mode', '--offline', '-Dmaven.test.skip=true', '-Dworkspace.root.dir=/builddir/build/BUILD/apache-sshd-2.6.0', 'package', 'org.fedoraproject.xmvn:xmvn-mojo:install', 'org.fedoraproject.xmvn:xmvn-mojo:javadoc', 'org.fedoraproject.xmvn:xmvn-mojo:builddep'] /usr/share/maven/bin/mvn: line 36: /etc/java/maven.conf: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.QeIPBF (%build) Bad exit status from /var/tmp/rpm-tmp.QeIPBF (%build) RPM build errors: which is a known bug of maven 3.6 shipped in RHEL 8.3 ( https://bugzilla.redhat.com/show_bug.cgi?id=1897375) There's a build in koji ( https://koji.mbox.centos.org/koji/taskinfo?taskID=207396) which should have the fix for this issue. Can we get that build in CBS build root? If not, can we get maven:3.5 module enabled instead of maven:3.6? thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 3

First round of RHEL programs announced
by Mike McGrath 04 Feb '21

04 Feb '21

Hi all, I know this was a hot topic on the list so I thought I'd share today's blog post which covers no-cost RHEL for small production workloads and no-cost RHEL for customer development teams. Keep in mind there are other programs coming, these just got done first. https://www.redhat.com/en/blog/new-year-new-red-hat-enterprise-linux-progra… Bullet Points: - Self-Support RHEL for no-cost in production use cases of up to 16 systems. - No-cost RHEL for customer development teams (larger number of systems for non-production cases). - Available no later than February 1 - Single Sign-on via a Red Hat account, or Github, Twitter, Facebook or other accounts (You'll soon not need to provide all kinds of personal information like you used to). -- Mike McGrath Linux Engineering - Chicago Red Hat mmcgrath(a)redhat.com T: (312)-660-3547

36 141

CentOS/Fedora authentication system merge (Please Read)
by Fabian Arrotin 03 Feb '21

03 Feb '21

# Introduction and background As it was preannounced some time ago , the CentOS Board agreed to merge the CentOS accounts (https://accounts.centos.org) with the Fedora FAS (https://admin.fedoraproject.org/accounts/) As both projects were running their own instance of FAS (running on el6/CentOS 6, so coming to EOL, so that needed to be migrated to new solution/platform), but that there are a lot of contributors common to both projects, it made sense to "migrate and merge" both into one, and so having only one account that can be used for both. The AAA/Noggin team worked in the last months on the new authentication system that will be used as foundation. The core block will be (Free)IPA (https://www.freeipa.org , already available in the distribution) and the community portal feature will be provided by noggin (https://github.com/fedora-infra/noggin) If you want to know more about noggin, consider watching the presentation given at last Fedora Nest event (https://www.youtube.com/watch?v=x1SevUmkE60) # What does it mean for you, contributors and SIG members ? Fedora already had an IPA infra, but "hidden" behind FAS, so accounts were already created in IPA backend. For CentOS, we were just using plain FAS, so users in our own backend (fas db). The "Merge" operation will go like this : - Fedora will kick fas2ipa script (https://github.com/fedora-infra/fas2ipa), synchronizing FAS attributes back into IPA, including group memberships coming from FAS/Fedora - Then the same process will be ran but importing from ACO (https://accounts.centos.org) into the same IPA backend. That's where the "fun" begins: * If the same nick/account exists at both side, the script is considering FAS as authoritative (remember, the FAS user *already* exists there, and is only modified for group[s] membership and attributes) * What is used to consider same nick/account being the same person ? the email (validated when registering account) will be used as primary key. So that means that you should *now* verify/update your email address in FAS and ACO so that they match * in case of a email address mismatch, the ACO account isn't migrated (group membership) but put in a queue to be verified * in case of matching email address, existing account is added to imported ACO groups The "open" question is about what to do for same account but in fact being different people (question is debated between Fedora and CentOS through the AAA initiative) # What has been already done ? You can follow publicly the status through dedicated tracker ( https://github.com/orgs/fedora-infra/projects/6 ), but let me focus on the CentOS Side (sending this to centos-devel so centos contributors) In the last months, Fedora already deployed a staging (.stg.) IPA instance, as well as a noggin community portal. For CentOS, we deployed (to be able to test integration) the following components in front of the Fedora IPA: * https://accounts.stg.centos.org (using noggin, with a centos visual theme applied) * https://id.stg.centos.org (ipsilon, used for openid/openidc IdP) We then reached out to some "key users" to validate that some applications migrated to new authentication system were working fine. We tested with : * pagure (https://git.stg.centos.org) * koji * openshift/OCP * some other apps using openid In December 2020, there was a first ran of the fas2ipa script, so (consider this a snapshot) existing accounts in both FAS and ACO were merged. >From that import, there were 123 accounts that were duplicates ones, but as said, it can be that they are the same account but using different email addresses. # What do you have to do ? You can try to login through https://accounts.stg.centos.org and see if you can login. Important remark: if you *didn't* have a FAS account , your account was imported/created for the first time in IPA, so that means that you'll have to use the "Forgot Password ?" feature on portal to reset your account (mail will be sent to email address tied to your account) # When will the real migration happen ? We'll wait on AAA/noggin team to give us estimated date, and when they'll migrate Fedora first. Once that will be done, we'll migrate ACO to the new setup (probably fas2ipa script ran during a week-end, but to be announced) # How will that impact my workflow for CentOS as SIG member ? Worth knowing that all deployed services using ACO will have to be reconfigured for AAA. That currently means : * https://git.centos.org (and also the MQTT bus for git push notifications) * https://cbs.centos.org (and also non public signing service) * other small services using OpenID/OpenIDC for authentication (https://blog.centos.org, some jenkins instances used by QA team, etc) As said, we have already staged all changes to support new auth in our ansible roles. When we'll have rolled out these changes, your existing TLS certificate that you use to authenticate with for cbs.centos.org *will not* work anymore (important) That means that you'll have to retrieve a new TLS cert, signed by the IPA CA cert. How to do that ? I'll see about how porting this to know repository, but for now, there is a copr repo that you can use : https://copr.fedorainfracloud.org/coprs/arrfab/fasjson-client/ IMPORTANT : do *not* use this pkg now, or do this from another workstation/vm/account/whatever : the new 'centos-cert' util would replace your currently working TLS cert (from ACO) . (Well, as fasjson for prod *isn't* deployed yet, that would not work at all, but it would when deployed If you have questions, feel free to ask in this thread, or join #fedora-aaa on Freenode. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

3 3

CentOS Stream 8 kernel
by Gena Makhomed 01 Feb '21

01 Feb '21

Hello All, I found regression in the CentOS Stream 8 kernels, and create bug report https://bugzilla.redhat.com/show_bug.cgi?id=1913806 After reading https://wiki.centos.org/Contribute/CentOSStream I try to download kernel sources and look for root cause of bug, but dist-git and source-git repos does not contain kernel sources, even if I try to execute %prep phase. For this reason I can't even try to find root cause of this bug by myself. This bug is critical for me, because currently I try to use systemd-nspawn for containers virtualization in production. If future CentOS 8.4 will contain this bug - it will be disaster. What else I can do (as user or developer) for fixing this bug? P.S. https://centos.org/distro-faq/ Q5: Does this mean that CentOS Stream is the RHEL BETA test platform now? A: No. CentOS Stream will be getting fixes and features ahead of RHEL. Generally speaking we expect CentOS Stream to have fewer bugs and more runtime features as it moves forward in time but always giving direct indication of what is going into a RHEL release ================================== But currently I hit the bug, which is absent in CentOS 8.3 but present in CentOS Stream 8. Looks like CentOS Stream 8 is really the beta version for future RHEL minor release, despite the CentOS FAQ. Sorry, but this is true. -- Best regards, Gena

9 13

SIGs need to designate a "sponsor" (Re: Upcoming authentication changes)
by Rich Bowen 29 Jan '21

29 Jan '21

Hopefully you have seen Fabian's email earlier today with details about the upcoming changes to the authentication system. If you participate in a SIG, we need for you to identify someone who is the SIG lead, who will manage (the term FreeIPA uses here is "sponsor") the authentication (ie, SIG membership) for your particular SIG. For SIGs that don't speak up, we'll be using the information that's on your SIG wiki page, but I'm pretty sure that a lot of those are incorrect, and I'll be reaching out to some of you individually. Meanwhile, if you can update that information, we'll save everyone some time. Thanks.

4 4

[Cloud SiG] CentOS Cloud SIG meeting (2021-01-28)
by Amy Marrich 28 Jan '21

28 Jan '21

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2021-01-28) ====================================================== Meeting started by spotz at 15:01:58 UTC. The full logs are available athttps://www.centos.org/minutes/2021/January/centos-meeting.2021-01-28-15.… Meeting summary --------------- * LINK: https://etherpad.opendev.org/p/centos-cloud-sig (spotz, 15:02:09) * ROll Call (spotz, 15:02:15) * Mission (spotz, 15:06:35) * LINK: https://wiki.centos.org/SpecialInterestGroup/Cloud (amoralej, 15:11:48) * LINK: https://www.centos.org/community/calendar/ I found to be more helpful (spotz, 15:13:19) * Chair/CO-Chair (spotz, 15:17:22) * Board Attendee (spotz, 15:39:40) * Sponsor for authentication (spotz, 15:42:45) * LINK: https://accounts.centos.org/group/view/sig-cloud (amoralej, 15:50:54) * Meeting Frequency (spotz, 15:55:49) Meeting ended at 16:01:42 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * spotz (77) * amoralej (70) * ykarel (9) * jcapitao (6) * jpena (6) * centbot (4) Generated by `MeetBot`_ 0.1.4 *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz <https://www.redhat.com/>

1 0

Virtualization SIG meeting minutes - 2021-Jan-27
by Sandro Bonazzola 27 Jan '21

27 Jan '21

#centos-meeting: Virtualization SIGMeeting started by sbonazzo at 16:05:16 UTC (full logs <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…> ). Meeting summary 1. 1. ACTION: look through CentOS Virt SIG wiki and update anything that needs updating (sbonazzo <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:09:18) 2. *Advanced Virtualization* (etrunko <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:09:59) 1. Reports of libvirt crashing with latest build (etrunko <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:10:35) 2. https://bugzilla.redhat.com/show_bug.cgi?id=1915601 (etrunko <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:10:39) 3. https://cbs.centos.org/koji/buildinfo?buildID=31798 (etrunko <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:11:54) 4. Fix has been officially released last Monday. The libvirt package has just been built for the Virt SIG. (sbonazzo <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:12:07) 3. *oVirt updates* (sbonazzo <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:12:56) 1. having troubles building apache-sshd within CBS, opened a ticket on it: https://bugs.centos.org/view.php?id=18036 (sbonazzo <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:13:31) 2. upstream working on getting CentOS Stream as default platform for oVirt, still having some troubles there (sbonazzo <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:14:14) 3. looking into having better collaboration and adding some oVirt test within CentOS Stream CI (sbonazzo <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:14:59) 4. *Xen updates* (anthonyper <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:17:32) 1. Xen 4.12 package only missing one XSA release recently (anthonyper <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:18:16) 2. Nearly done with 4.13 packaging, I just need to check if packages are missing. (anthonyper <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:19:31) 5. *AoB* (sbonazzo <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…>, 16:20:15) Meeting ended at 16:21:29 UTC (full logs <https://www.centos.org/minutes/2021/January/centos-meeting.2021-01-27-16.05…> ). Action items 1. look through CentOS Virt SIG wiki and update anything that needs updating -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

1 0

CentOS related article at The Register
by redbaronbrowser 27 Jan '21

27 Jan '21

The Register has an article about CentOS: https://www.theregister.com/2021/01/26/killing_centos/ My best guess is the title and how the quotes form the interview was framed in the article wasn't what Red Hat expected. Maybe the reader should be taken with a grain of salt. I am posting it here for a number of reasons: First, my guess is the majority of members of centos-devel mailing list have already seen the article or would have seen it regardless of if I posted the link to it here. Second, I think it would be good to give someone from Red Hat a chance to respond to if there is inaccuracies in how the article characterizes things. Third, is this how we expect governance of Stream to work moving forward?

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2021