devel

devel@lists.centos.org

16 participants
4590 discussions

Re: [CentOS-devel] re CVE errata in CentOS Stream
by redbaronbrowser 02 Mar '21

02 Mar '21

On Friday, February 19, 2021 5:47 PM, Josh Boyer <jwboyer(a)redhat.com> wrote: > On Fri, Feb 19, 2021 at 5:47 PM redbaronbrowser > redbaronbrowser(a)protonmail.com wrote: > > > I'm not asking for anything ahead of RHEL customers getting it. All I am asking for is pre-approval from management to get access as an Upstream once a problem with RHEL is confirmed. > > If you mean "get access to the fixed code" or "get access to a fixed > build", in a situation like the post-Boot Hole scenario there is no > pre-approval necessary. We will do our best to resolve the issue in > Stream as quickly as possible. You keep coming back to the Fix for the Broken-Fix. I believe you when you say Red Hat has always been working as quickly as possible to Fix any Broken-Fixes. However, once they have the fix the lifecycle of the bug is over. Stream isn't interesting from the perspective of completed bug lifecycles. The interesting aspect to closing the openness gap is the mid-lifecycle of the bug. I am trying to focus on how quickly will Stream users be able to contribute to the fixing of a Broken-Fix. I am sorry if I am parsing too much into Mike's response, but it read to me like it is possible for the code to a Broken-Fix to, by policy, be withheld to only the "entitled" RHEL subscribers to access. I'm asking to what degree Red Hat expects to be able to take advantage us while an active Bugzilla entry exist because a CVE "fix" had unintended side-effects. Can we get quick transparency into accessing broken packages and code even if that broken build is a CVE "fix" related? Or is the policy that we will sit on the sidelines for Red Hat by itself to fix broken security patches much like CentOS has always operated before Stream?

9 32

Meeting minutes of the Storage SIG Monthly, March Edition
by Niels de Vos 02 Mar '21

02 Mar '21

Agenda: https://hackmd.io/Epc35JIESaeotoGzwu5R5w?both#2021-03-02 Minutes: https://www.centos.org/minutes/2021/March/centos-meeting2.2021-03-02-10.00.… Minutes (text): https://www.centos.org/minutes/2021/March/centos-meeting2.2021-03-02-10.00.… Log: https://www.centos.org/minutes/2021/March/centos-meeting2.2021-03-02-10.00.… =========================================================== #centos-meeting2: CentOS Storage SIG monthly, March Edition =========================================================== Meeting started by ndevos at 10:00:58 UTC. The full logs are available at https://www.centos.org/minutes/2021/March/centos-meeting2.2021-03-02-10.00.… . Meeting summary --------------- * Roll Call (ndevos, 10:01:14) * Agenda (ndevos, 10:03:24) * LINK: https://hackmd.io/Epc35JIESaeotoGzwu5R5w?both#2021-03-02 (ndevos, 10:03:29) * centos-release-gluster packages (ndevos, 10:04:34) * Open Floor (ndevos, 10:11:27) * ceph packages update (fmount, 10:13:12) * Any Other Bussiness (ndevos, 10:27:07) Meeting ended at 10:32:11 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * ndevos (58) * fmount (45) * centbot (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

CPE Weekly Report: 2021-02-26
by Aoife Moloney 26 Feb '21

26 Feb '21

Hi Everyone, If you would like to see this report and toggle to the section you are most interested in, I would suggest visiting this link https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view and use the header bar on your left to skip to where you want to go! ## Initiative FYI Links Initiatives repo here: https://pagure.io/cpe/initiatives-proposal 2021 Quarterly Planning timetable here: https://docs.fedoraproject.org/en-US/cpe/time_tables/ so you know when I need it in by to review it. Details on initiative requesting/how to work with us on new projects here: https://docs.fedoraproject.org/en-US/cpe/initiatives/ ### Misc I hope you all enjoyed DevConf.cz last week! There were some great talks and I am looking forward to catching up on the ones I unfortunately missed when they are posted in a few weeks! Also if you missed the CentOS Dojo at FOSDEM, you can watch all talks on the CentOS YouTube channel here https://www.youtube.com/playlist?list=PLuRtbOXpVDjC7RkMYSy-gk47s5vZyKPbt ## Project Updates *The below updates are pulled directly from our CPE team call we have every week.* ## CentOS Updates ### CentOS * CentOS CI updated OCP to 4.6.17 * Rolled out security fixes to ci.centos.org Jenkins and cert update ### CentOS Stream * Documentation updated on the shortened CentOS Linux -> CentOS Stream conversion, see the demo here https://asciinema.org/a/393875 * CentOS Extras is now separately delivered for Stream and Linux * CentOS Stream 8 container images are published now to quay.io ### Fedora * We are now in F34 freeze! All changes to frozen hosts take 2 +1s * Bodhi updates-testing activated for F34 * Fedscm-admin work started on default branches * Openh264 repos are hosted on Cisco CDN ### Noggin/AAA * User migration script has been successfully re-run * Lots of docs updates - check out the docs section for more information https://noggin-aaa.readthedocs.io/en/latest/ * PR opened for changes to docs to add pkinit to docs to allow applicable certs be shipped for packages but it seems fedora-packager Fedora package has to be built with the change applied https://pagure.io/fedora-packager/pull-request/166 * If you are experiencing any issues with your application authenticating with Noggin, please reach out to the team on IRC channel #fedora-aaa * The work tracker for this project can be found here https://github.com/orgs/fedora-infra/projects/6 * And please report any issues you find in the repo https://github.com/fedora-infra/noggin ## Team Info ### Background: The Community Platform Engineering group, or CPE for short, 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. See our wiki page here for more information:https://docs.fedoraproject.org/en-US/cpe/ 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?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

[CloudSiG] Meeting notes from 2021-02-25
by Amy Marrich 25 Feb '21

25 Feb '21

Congratulations to new co-chairs Alfredo Moralejo Alonso and Paul B. Isaacs. Also, please note the SiG will be moving to a bi-weekly meeting cadence on even weeks. And lastly, but not least importantly! Welcome to our new SiG members - davdunc, hrw, and konkan Thanks, Amy ====================================================== #centos-meeting: CentOS Cloud SIG meeting (2021-02-25) ====================================================== Meeting started by spotz at 15:00:31 UTC. The full logs are available athttps://www.centos.org/minutes/2021/February/centos-meeting.2021-02-25-15… . Meeting summary --------------- * Roll Call (spotz, 15:00:52) * LINK: https://etherpad.opendev.org/p/centos-cloud-sig (spotz, 15:01:50) * Close Nominaations (spotz, 15:13:43) Meeting ended at 16:00:09 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * spotz (40) * amoralej (32) * paulbisaacs (19) * apevec (9) * centbot (7) * ykarel (4) * jcapitao (2) * jpena (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot *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

[NFVSIG] NFV SIG meeting minutes - 2021-02-24
by Alfredo Moralejo Alonso 24 Feb '21

24 Feb '21

============================================== #centos-meeting: NFV SIG meeting - 2021-02-24 ============================================== Meeting started by tfherbert at 15:00:35 UTC. The full logs are available athttps://www.centos.org/minutes/2021/February/centos-meeting.2021-02-24-15… . Meeting summary --------------- * agenda bashing (tfherbert, 15:01:00) * current topic is agenda bashing -- by for now. (tfherbert, 15:03:20) * FDP 21.A followup (amoralej, 15:06:52) * builds for openvswitch 2.11 and 2.13, ovn 2.13 and openvswitch-selinux-extra-policy for 21.A were pushed to CentOS mirrors (amoralej, 15:08:08) * https://access.redhat.com/errata/RHSA-2021:0497 was published with CVE (amoralej, 15:10:44) * openvswitch2.13-2.13.0-79.5.1.el8 and ovn2.13-20.12.0-17.el8 have been built and pushed to -testing (amoralej, 15:11:49) * promotion to -release is currently in CI https://review.rdoproject.org/r/#/c/32083/ (amoralej, 15:12:09) * CentOS 8 Stream status (amoralej, 15:13:23) * LINK: https://cbs.centos.org/koji/buildinfo?buildID=32074 (amoralej, 15:13:57) * AGREED: to use disttag el8s in nfv8s-openvswitch-2-el8 build root (amoralej, 15:27:08) * AGREED: to create and promote separated builds for C8 and C8S in nfv sig tags (amoralej, 15:27:36) * Status of automation and CI (amoralej, 15:29:39) * it was agreed to use gerrit based approach for automation in tag and test using gerrit reviews (amoralej, 15:30:19) * automation is implemented and functional for 2.13 stream (amoralej, 15:37:21) * ACTION: NFVSIG members willing to review and approve promotions, please create your account in https://review.rdoproject.org (amoralej, 15:38:22) * LINK: https://cbs.centos.org/koji/buildinfo?buildID=31847 (amoralej, 15:56:34) * LINK: https://access.redhat.com/solutions/3358 (santana, 15:58:03) Meeting ended at 16:01:03 UTC. Action Items ------------ * NFVSIG members willing to review and approve promotions, please create your account in https://review.rdoproject.org Action Items, by person ----------------------- * **UNASSIGNED** * NFVSIG members willing to review and approve promotions, please create your account in https://review.rdoproject.org People Present (lines said) --------------------------- * amoralej (123) * santana (24) * ykarel (12) * tfherbert (10) * centbot (6) * dholler (5) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Cloud] Cloud SiG Meeting Reminder and Chair/Co-Chair Nominations and Elections
by Amy Marrich 24 Feb '21

24 Feb '21

Just a reminder that the Cloud SiG will meet this Thursday (fourth Thursday of the month) at 15:00 UTC in the #centos-meeting room on Freenode. With the SiG membership[0] cleanup completed, we would like to take nominations for the chair and co-chair roles. Please reply to this email with your self-nominations and nominations for other members of the SiG. If you are nominated by another member of the SiG please re[;y to this mail as well with your acceptance. Nominations will conclude during this week's meeting. If we have a quorum, we will hold elections during this week's meeting. If a quorum is not met, we will ask for 1-2 volunteers and hold an election outside our regular meetings in the next week. Any questions please reach out. Thanks, Amy (spotz) 0 - https://accounts.centos.org/group/members/sig-cloud/ *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/>

3 2

Simplified CS8 upgrade steps
by Carl George 24 Feb '21

24 Feb '21

Howdy everyone, Previously it was a three step process to upgrade from CentOS Linux 8 (CL8) to CentOS Stream 8 (CS8). We have reduced it to a two step process by adding the centos-stream-repos package to the Extras repo in CL8. You can now upgrade from CL8 to CS8 by running just these two commands. [root@centos ~]# dnf swap centos-linux-repos centos-stream-repos [root@centos ~]# dnf distro-sync The instructions have been updated on the main website. I recorded a short screencast to demonstrate the process. https://asciinema.org/a/393875 -- Carl George

2 1

[Promo] Call for content: March newsletter
by Rich Bowen 22 Feb '21

22 Feb '21

Hi, folks, If there is something that you would like to highlight in the March newsletter - or, indeed, if there's something that you think that *I* should highlight - please speak up here, or even better, over on the centos-promo mailing list - https://lists.centos.org/mailman/listinfo/centos-promo Thanks! --Rich

1 0

Re: [CentOS-devel] re CVE errata in CentOS Stream
by redbaronbrowser 19 Feb '21

19 Feb '21

On Friday, February 19, 2021 2:26 PM, Josh Boyer <jwboyer(a)redhat.com> wrote: > On Fri, Feb 19, 2021 at 2:45 PM redbaronbrowser > redbaronbrowser(a)protonmail.com wrote: > > > > > On Wednesday, February 17, 2021 9:01 PM, Mike McGrath mmcgrath(a)redhat.com wrote: > > > > > > > > > There's a bit of nuance to this question in that policy states that CVEs should be fixed in RHEL before CentOS Stream. > I'm not sure what policies you're referring to. Can you point to > where they are documented? I suspect you mean the various blogs and > answers on the list, which are good discussions but I don't want to > assume that those are policies, nor do I want to assume that is what > you are referring to. I trimmed the coversation down to the policy I'm refering to. > Also, Stream and CI/CD are indeed important and related. However, > that doesn't mean there is a single universal approach to everything. I am not implying there is a single universal approach to everything. What I am asking is if exceptions to the policy Mike McGrath stated has already been established so the Stream community can get access to help quickly? Or would a RHEL user indicating a CVE fix cause a regression require seeking management approval before releasing the information to Stream? > > Will there be a way to expedite a CVE fix attempt into Stream after reports of a regression from RHEL users? > > Can you help me understand why an answer to that question matters > given that we are not providing an SLA on CVE fixes in Stream? I > understand that leaves things ambiguous, but even if the answer to > your question was "yes" it doesn't change anything in a manner that > matters from a Stream contributors perspective. I was not expecting an SLA on CVE fixes. If a CVE fix works as intended then I expect the policy MG stated to be the policy followed. I am not trying to object to that. A service-level agreement is between Red Hat and RHEL customers. There is no service agreement with Stream users so I never expected a SLA. Instead I was thinking more along the lines of an ULA (Upstream Level Agreement) that if a CVE "fix" is confirmed to be a CVE "breakage" similar to "Boot Hole," that management approval is already in place for the RHEL team to move access to that regression code to Stream users to be able to review. The SLA policy applying only to RHEL would continue to do so. But it sounds like as it stands now if a CVE "fix" causes unexpected problems, even after the problems are confirmed it may be weeks until management approves the Upstream getting access to help work on the issue. All I'm asking for a ULA which may only apply to 0.01% of updates so that management approval already pre-exists to release it to Upstream in a number of hours instead of weeks. > I am trying to be very clear here to avoid the mistake we made, > inadvertent or not, with the CentOS Linux lifecycle change. There is > no SLA on CVE fixes in Stream. Ok > > Will there be a repo for known problematic security updates such as a CR-broken? > > Not to my knowledge. > > > What would be the roll of Stream if "Boot Hole" could happen again? Why is Stef Walter bringing it up? Are we being asked to help prevent or reduce the impact of that should it occur? > > Stef can speak for himself as to why it was mentioned. It is perhaps > a confusing issue to raise in the context of Stream, because that > particular CVE was under embargo anyway. There is no call to action > nor opportunity for the Stream community to deal with embargoed CVEs > in Stream itself. That is the nature of embargoes. I think you mean the development of the "Boot Hole" patch took place during an embargo, right? Once "Boot Hole" was released and actually impacted RHEL customers, wasn't the embargo period already over? I'm not asking for anything ahead of RHEL customers getting it. All I am asking for is pre-approval from management to get access as an Upstream once a problem with RHEL is confirmed. > > Put another way, is Stream a true Upstream or a hybrid? Is it really the policy that Stream is strictly a downstream when it comes to CVEs? Or if something unexpect happens again, is the policy in place were we act as an Upstream for addressing it? > > With the nuance of CVEs in play, it's a hybrid. Mike already > explained that nuance above. In terms of closing the openness gap, that seems more than just a nuance. Of the CentOS 7 errata announced, 20% has been security updates. The existing information in the Stream FAQ and CentOS blog imply we are becoming the 100% Upstream. Instead the reality seems closer to being 80% Upstream and 20% Downstream.

1 0

No default stream configured for modules in powertools
by Peter Georg 19 Feb '21

19 Feb '21

Hi everyone, I just tried to install the new python39 stream on one of my systems. This includes the python39-Cython package. I realized that a simple "dnf install python39-Cython" does not work as the package is part of powertools (whereas python38-Cython is in appstream) [1]. Hence python39-Cython is not part of the "python39" module, but part of "python39-devel" - the corresponding module for python39 subpackages in powertools. Afaik this is required as a stream may only contain packages residing in one repository. Ultimately the install fails because the python39-devel module has not set a default stream. For the python39 module a default stream is set. I checked and can confirm that none of the modules in powertools has set a default stream. This is puzzling as all these modules have only one stream and the corresponding modules in appstream have a default stream set. Wouldn't it make more sense to use the same default for both the module in appstream and the corresponding module in powertools (or any other repository it may reside in)? Best Peter [1] Of course I could run a "dnf module enable python39-devel" before issuing the install command. However I use many scripts to setup systems that simply expect a list of packages to install, all these fail. Note that I do not even have to specify a stream to enable the correct one. While this makes sense as there is only one stream, it should not work according to the documentation (see man dnf): "In case stream is not specified, the enabled or the default stream is used, in this order." No stream is enabled and there is no default stream. This whole process just feels inconsistent.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel