Thursday, 2022-03-10

*** pojadhav- is now known as pojadhav06:33
wuchunyanghi,team,  Is there a PTL for Trove right now ?08:24
fungiwuchunyang: not yet, no: https://governance.openstack.org/tc/reference/projects/trove.html11:37
fungithough since you volunteered on the mailing list i'm sure the tc members will discuss your offer11:38
wuchunyangthanks fungi11:38
fungiyou're welcome11:39
*** pojadhav is now known as pojadhav|afk12:46
*** pojadhav|afk is now known as pojadhav13:37
gmannwuchunyang: thanks or volunteer, we will discuss in today meeting and let you know.14:26
knikollai won't be able to attend the meeting today as I am out of office. 14:45
gmannknikolla: ack, thanks for updates.14:45
arne_wiebalckgmann: I have the meeting clash we discussed.14:53
gmanntc-members: meeting in an 7 min from now in IRC14:53
gmannarne_wiebalck: ack.14:53
jungleboyjAck14:59
gmann#startmeeting tc15:00
opendevmeetMeeting started Thu Mar 10 15:00:19 2022 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'tc'15:00
gmann#topic Roll call15:00
jungleboyjo/15:00
dansmitho/15:00
rosmaitao/15:00
slaweqo/15:00
dmendiza[m]🙋15:00
gmanno/15:01
spotz_o/15:02
arne_wiebalcko/15:02
gmann#topic Follow up on past action items15:02
gmann- gmann to add the FIPs testing direction in next meeting agenda15:03
gmannadded in agenda and we will discuss in end of today meeting15:03
gmann- slaweq to send the ML to call for PTL for adjutant and trove project15:03
gmannslaweq:  sent on ML15:03
slaweqI did :)15:03
slaweqand there are some volunteers potentially15:04
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027557.html15:04
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027558.html15:04
slaweqthx gmann for links15:04
gmann+1 yeah, let's discuss those in leaderless project topic15:04
gmann#topic Gate health check15:04
gmannthere is more traffic yesterday and took more time to merge patches but not worst. 15:04
gmannany other news15:05
dansmithugh, I meant to do some digging,15:05
dansmithbut I was chasing down what seemed like a common failure in some patches related to volume resize (I think)15:05
dansmithand it seemed like maybe it was a problem with the worker instead of any of our stuff,15:05
dansmithbut then I applied updates and restarted my system and lost some state (like a noob)15:06
jungleboyj:-(15:06
gmannoh15:06
dansmiththat was the only thing I was chasing at the time.. seemed like I've also seen a bunch of blind rechecks lately, have others?15:06
gmannslaweq: you have the script for recheck for neutorn. right?15:07
gmanncan we extend that for all project and we can see how much we are doing?15:07
gmannscript to count the recheck15:07
slaweqgmann: I have script which can count number of rechecks in every project15:07
dansmithah, that'd be interesting15:08
gmannyeah and will be good to check here weekly15:08
slaweqI can prepare such data for patches from all projects15:08
gmann+115:08
jungleboyjslaweq:  That is interesting.15:08
slaweqsure, I will prepare it for next week15:08
gmannperfect, thanks.15:09
dansmithagree, especially in light of losing some capacity, we might need to lead a charge to get people to actually look for the reasons before they recheck15:09
gmannI remember neutron CI meeting discuss/monitor sich data in very nice way.15:09
slaweqdansmith: yeah, that's why I did it and we are checking it every week15:09
dansmithslaweq: ++15:09
slaweqnow it's good as we are below 1 recheck in averega15:09
gmannnice15:10
slaweqbut we had weeks where we had e.g. 10 rechecks to get patch merge :)15:10
slaweq10 in average15:10
gmannslaweq: let's add a etherpad where we can put weekly data there and check in meeting.15:10
slaweqgmann: sure, I will do that15:10
gmannthanks15:10
gmannfor centos9-stream failure on detach. this can help but I have not debugged the failure on this yet #link https://review.opendev.org/c/openstack/tempest/+/83160815:11
gmannI thought of doing before rc-1 but could not finish.15:11
gmannanything else on gate things?15:12
gmann#topic Z cycle Leaderless projects15:13
gmannwe are left with two project and slaweq got success to get the volunteer for trove 15:13
gmann#link https://etherpad.opendev.org/p/zed-leaderless15:13
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027654.html15:14
gmannwu.chunyang volunteer to maintain it as they are using it15:14
gmannchecking their contribution in Trove or so15:16
jungleboyj++15:16
gmannI find these #link https://review.opendev.org/q/owner:wuchunyang%2540yovole.com+project:openstack/trove15:16
slaweqI looked here https://www.stackalytics.io/?release=all&user_id=wu.chunyang&metric=commits15:17
gmannyeah15:17
gmannI think we can go ahead and assign the PTL, any other opinion 15:17
slaweq+115:17
gmannespecially there is no maintainer in that project15:17
gmannif no objection here, I will propose the PTL assignment patch15:18
jungleboyj+115:18
rosmaitano objection15:18
gmannok, I will propose patch after meeting15:19
gmann1nd project Adjutant 15:19
gmannBraden Albert asked to wait until March end #link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.html15:19
gmannwhich we can wait and we can check in PTG. based on situation that time we can take call.15:19
gmannthat is all on leaderless projects, anything to discuss on this topic?15:20
jungleboyjWell, that isn't too bad.15:20
gmannyeah, more leaderless project this time but fastest to fill them. 15:20
jungleboyj++ Focus on the positive.15:21
gmannwhich indicates we need to adjust our election process or so. but anyways we will discuss it in PTG15:21
gmann#topic PTG Preparation15:22
gmannwe selected the time slot of TC discussions #link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027584.html15:22
gmannPlease plan accordingly. and topic wise schedule we will prepare later15:22
gmannkeep adding the topics you would like to discuss this etherpad #link https://etherpad.opendev.org/p/tc-zed-ptg15:23
gmannthat is all for PTG for now, anything else?15:23
gmannand this etherpad for TC+PTL sessions https://etherpad.opendev.org/p/tc-ptl-interaction-zed15:23
gmann#link https://etherpad.opendev.org/p/tc-ptl-interaction-zed15:23
ade_lee_is there a specific time to give updates on community goals like fips?15:23
ade_lee_or should I add to the above agenda?15:24
gmannade_lee_: we have not prepared the exact topic wise schedule but please add your preference in etherpad and we can try for that L39 in #link https://etherpad.opendev.org/p/tc-zed-ptg15:24
gmannarne_wiebalck: oh or you mean for today meeting?15:24
gmannade_lee_: ^^15:25
ade_lee_ah gotcha -- I just saw that line15:25
gmanncool15:25
gmannade_lee_: if time conflict you can add the details in etherpad also but I  can try to schedule as per your availability 15:26
ade_lee_gmann, ok great thanks15:26
gmannand yes, if anyone has preference on any topic to avoid conflict with any specific time/day please mention that in etherpad15:26
gmannI do not promise to avoid 100% conflict but we can try :)15:27
gmannmoving to next topic...15:27
gmann#topic Check on Yoga Tracker progress15:27
gmann#link https://etherpad.opendev.org/p/tc-yoga-tracker15:28
gmannlet's go by one by one as we are very  close to Yoga cycle end15:28
gmann1. Technical Guidelines: dansmith 15:28
dansmithyeah I suck15:29
gmanndansmith: I think you are already doing lot of things, but just to know any plan for unified limit like next cycle?15:29
dansmithyeah, nova merged theirs now,15:29
gmannyeah15:29
dansmithso we have two examples to go by15:29
dansmithI still want to do this, it was just always the easiest thing to push aside15:29
gmannsure, no worry. if you have time but having nova completed is good progress overall15:30
dansmithack15:30
gmann3. TAG framework removal proposal15:30
gmannfor this few tags are pending specially release script patch and VMT one which needs to wait for OpenStack website to be updated by foundation15:31
gmannso this is good progress and can be completed based on these deps15:31
gmann4. Improvement in project governance - diablo_rojo_phone  15:32
gmannfor this we discussed to have a 'Tech pre-review'  process proposal15:32
gmannbut I did see anything up yet15:32
gmann5. Release name process change -belmiro15:33
gmann#link https://review.opendev.org/c/openstack/governance/+/82956315:33
gmannBelmiro proposal is in good shape and with more +1 there15:33
gmannand as discussed in last or this week, we will discuss the release name-removal things separately in PTG as it need lot of discussion and deps15:33
gmannjungleboyj: diablo_rojo_phone arne_wiebalck spotz knikolla ^^ if you would like to review it as I am planning to merge it early tomorrow (early in CST)15:34
* jungleboyj just opened a tab for it. :-)15:35
gmannif no strong objection from yoru review or here15:35
gmann6. Community-wide goals: ricolin gmann 15:35
diablo_rojo_phoneI can review today15:35
gmannjungleboyj: diablo_rojo_phone thanks 15:35
gmannwe have done the community restructure but left with the checklist15:36
gmannI will try if I can push something up next week15:36
gmann7. User Survey Feedback Analysis/Responses - jungleboyj 15:36
jungleboyjI too suck.  :-)15:36
jungleboyjI have started on that.  Will have things ready for the PTG.15:36
gmannjungleboyj: perfect, thanks. and before PTG is good time15:37
dansmithjungleboyj: suck buddies? wait, that.. nevermind :)15:37
* jungleboyj laughs15:37
gmannanything else on Yoga tracker items progress?15:37
jungleboyjWell, that was something I never expected from dansmith .  :-)15:37
slaweqdansmith: You made my day with "suck buddies" :D15:38
dansmithslaweq: yw :P15:38
gmann:P15:38
gmann#topic Adding FIPs gate jobs and direction on how to run them in optimize way w.r.t. infra resource shortage.15:38
gmannade_lee_: can you please brief about what is your plan about adding FIPs job in gate ?15:39
gmannand then we can discuss what best we can do to utilize the infra resource in best way15:39
gmannI remember you were trying to add as experimental in Tempest gate15:39
gmannwhich is not merged yet15:40
ade_lee_gmann, well - its been really project by porject at this point - and only in checks .15:40
ade_lee_many projects have a fips gate15:40
dansmithI think the concern is more about us having to test it on centos, and that not going very well15:40
ade_lee_and some (like cinder) are still working on getting gates in15:40
dansmithAFAICT, the centos jobs we've tried have been too unstable to keep voting15:41
dansmithso is there a plan to be able to test these on ubuntu at some point in the future?15:41
gmannso it has to be on centos and adding in project check pipeline as non voting?15:41
ade_lee_understood, centos has been trying as of late15:41
gmannand is centos one passing and stable?15:41
ade_lee_dansmith, I've contacted canonical about fips on ubuntu but there are issues15:41
gmanndansmith: if it is stable then we can add but again if stable which I doubt on any centos job15:42
ade_lee_mainly because fips on ubuntu is a premium feautre -- ie. one that requires a subscription15:42
dansmithlol15:42
gmann:)15:42
fungiubuntu doesn't provide fips support "for free" (it's a paid feature which requires obtaining and applying license keys)15:42
ade_lee_if we figure a way around that we can switch to ubuntu15:42
dansmithmaybe that's the problem with the centos jobs? we forgot to put quarters in the slot?15:42
jungleboyjBwah ha ha!15:42
ade_lee_dansmith, I've been trying to move the contos jobs to centos-9 which appears to be getting more stable 15:43
jungleboyjBased on experience it would have to be a huge stack of quarters.15:43
fungicanonical seems like they might be willing to give us license keys, but we have no way to prevent people from accessing those in jobs15:43
dansmithreally? that's surprising, but good if there's a horizon15:43
dansmithfungi: I would have thought the license would be for support and not "a license key to turn off a bunch of ciphers"15:43
ade_lee_the latest problem there has been changes to openssl to disallow sha1 in signatures by default15:43
ade_lee_and thats been causing all sorts of headaches, but we're finding them15:44
gmannbut should we try them as periodic or experimental and on few projects and if they are stable then try to add in all other projects?15:44
spotz_Is there anything the CentOS community can do to help? I’ve been promoting working with our neighbors 15:44
dansmithspotz_: suck less? (/me continues today's theme)15:44
fungidansmith: right, it's the customizations they're gating behind the license key, someone could certainly roll their own fips support for any distro if they have the time and interest15:44
gmannspotz: yeah, help in fixing the centos jobs, and for devstack support which is broken regularly and we do not have many centos people to help there15:44
dansmithspotz_: the problems seem to come from libvirt, qemu, and all over, so it's not really a single thing to fix AFAICT15:45
clarkbdansmith: to put it more diplomatically I would say putting mor eemphasis and reverting broken changes and/or fixing them. The whole ping sysctl perms thing was broken for like a month and was a trivial revert that could've been done instead15:45
spotz_Ok15:45
dansmithclarkb: yeah I was just trying to say: it's not one bug we need fixed, it seems systemic15:45
clarkbthey appear to be changing things aggressively via pulls from upstream rhel and when it breaks they don't fix centos they wait for rhel to fix15:45
clarkbdansmith: agreed15:45
dansmithwhich also makes me not really want to try to fix it and just work on being able to run it on something stable15:46
clarkbbasically when thing sgo wrong they are not addressed in a timely manner directly in centos and instead deferred to rhel if I read between the lines in the bug tracker properly15:46
clarkband that leads to long periods of broken in centos15:46
fungiwe've added rocky linux very recently, which is a rhel clone (currently rhel 8 as there's still no rhel 9)15:46
dansmithclarkb: yeah and I kinda think that's the "new way" we should expect from here on out15:46
spotz_That is something being worked on15:46
slaweqmaybe stupid question but what about fedora? Would it be better than centos maybe?15:46
gmannnot sure if that is tried for FIPs15:47
fungislaweq: not for long-term testing since we can't keep running it for stable branches15:47
clarkbya rocky seems like a good option to look at if stablitiy is the issue15:47
slaweqk15:47
fungiour stable support lifetime is several times that of fedora support for a given release15:47
gmannback to FIPs jobs running: ade_lee_ do you have any rough list that how many projects run FIPs jobs in check or gate pipeline? 15:47
ade_lee_counting ...15:48
ade_lee_keystone, barbican, glance, nova, cinder (in progress), ceilometer, tripleo , manila , neutron 15:48
ade_lee_horizon (in progress)15:49
* ade_lee_ getting my spreadsheet15:49
slaweqjust to be clear: neutron has those jobs in periodic, not check nor gate pipelines15:49
gmannoctavia, designate also15:49
gmannand in tempest experimental but that is not merged yet15:50
gmannslaweq: +115:50
gmannade_lee_: can we add them as perioidic for all those projects and collect more data on stability and ion next cycle or so where we select this goal then we start adding in each pipeline15:51
ade_lee_I think thats it , but I may have missed one or tow15:51
johnsomYeah, Octavia and Designate are both on plan for FIPs jobs. Octavia even has FIPs enabled in the amphora instances today.15:51
ade_lee_gmann, we can -- seems reasonable until centos is more stable15:52
gmannespecially when infra resource shortage coming soon..15:52
ade_lee_how often do periodic jobs run?15:52
gmannade_lee_: yeah or until anyone gift  us ubuntu preimum  :)15:52
gmannade_lee_: you can configure, like weekly or month15:52
clarkbcurrently daily15:52
dansmithwhat about debian? do they have a fips knob?15:53
gmannweekly also you can configure 15:53
slaweqin neutron periodic those jobs are pretty stable: https://zuul.openstack.org/builds?job_name=neutron-ovs-tempest-fips&job_name=neutron-ovn-tempest-ovs-release-fips&project=openstack%2Fneutron&pipeline=periodic&skip=0 :)15:53
gmannade_lee_: like this https://github.com/openstack/placement/blob/master/.zuul.yaml#L6415:53
ade_lee_ok - that seems like a reasonable compromise -- and yeah, some of the jobs are quite stable ^^ see neutron/ cilometer15:53
slaweqof course it's just few days as we run them like that but seems pretty ok IMHO15:53
gmannok15:54
ade_lee_and barbican/keystone15:54
fungithe crypto-policies package on debian has a fips-mode-setup tool15:54
gmannbut whatever you like daily weekly or depends on projects and how stable they are15:54
ade_lee_sure thats fair 15:54
ade_lee_is it possible to trigger a periodic job manually in a review?15:55
fungigetting "ubuntu premium" isn't so much the problem, as i mentioned, it's securing the key when run against arbitrary code which has root access to the nodes15:55
slaweqade_lee_: I think You can add same job to periodic and experimental pipelines15:55
gmannade_lee_: for that you can add in experimental queue also15:55
fungiade_lee_: if you want to trigger a job manually you put it in experimental, yeah15:55
fungiyou can have the job in both pipelines15:55
gmannslaweq: +115:55
slaweqand then trigger it in review with "check experimental"15:55
ade_lee_ok cool - I can do that15:55
fungiyou can't "trigger" the periodic pipeline, that's what makes it periodic15:56
fungiit's triggered by a timer15:56
dansmithfungi: uh I disagree. "wait" is an action :P15:56
gmannok, let's convert the existing FIPs job to run periodic/experimental for all projects they have been added or going to be added15:56
jungleboyj:-)15:56
gmannade_lee_: ^^ ok for you15:56
ade_lee_suuL: advance time15:56
ade_lee_works for me15:56
gmannperfect, any objection from anyone on above proposal 15:57
dansmithto recap,15:57
dansmithit's fips jobs go in experimental or periodic?15:57
ade_lee_fyi, on the tripleo side of things, things are progressing enough, that we make fips testing the default15:57
gmanndansmith: yes15:57
ade_lee_as we're testing on centos 9 in any case15:57
dansmithno objection from me :)15:57
gmannade_lee_: ack. and in PTG we will check the goal status and see if we can run more or so or other distro FIPs nobs15:58
ade_lee_and we can exampine data on stability at the ptg15:58
gmannyeah15:58
gmanncool, thanks ade_lee_ for joining and discussion15:58
gmann#topic Open Reviews15:58
gmann2 min left15:58
ade_lee_and I'lltry sync again with canonical15:58
rosmaitais there a way you can see all the fips jobs builds in zuul?15:58
gmannade_lee_: +115:58
rosmaitai can see this one for glance: https://zuul.openstack.org/builds?job_name=glance-multistore-cinder-import-fips&skip=015:59
rosmaitabut if i wanted to look at all of them, is there a way to do that15:59
fungiif they have known names, you can add them all to a query yes15:59
ade_lee_ack -- I was wondering about that too15:59
fungii don't think you can regex that unfortunately15:59
fungior glob15:59
*** pojadhav is now known as pojadhav|dinner16:00
gmannyeah by name, it does not work as regex https://zuul.openstack.org/builds?job_name=*fips&skip=016:00
fungibut if someone makes a list of them, we could make a query and link it somewhere16:00
gmannanyway we are out of time16:00
rosmaitafungi: ty16:00
ade_lee_fungi, I can find the names and provide to you to help make a query?16:00
gmannwe have discussed about open reivews, please check those16:00
gmannthat is all for today meeting, anything else?16:00
gmannok, thanks for joining everyone 16:01
gmann#endmeeting16:01
opendevmeetMeeting ended Thu Mar 10 16:01:27 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-10-15.00.html16:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-10-15.00.txt16:01
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-10-15.00.log.html16:01
slaweqthx16:01
slaweqhave a great rest of the day @all :)16:01
rosmaitayou too16:01
fungiade_lee_: sure, you can also just assemble the query on the builds page, or look at how it structures the url and do a quick bit of loop script to make it16:02
jungleboyjThanks!16:03
ade_lee_fungi, ok - I'll play around with it16:03
rosmaitagmann: i have a question about the status of translation in openstack ... for example, the french and italian .po files were deleted from cinder recently16:04
rosmaitai am wondering if i missed some discussion on the ML, or whether we should talk about this at the PTG16:05
gmannrosmaita: ok, ianychoi[m] is and i think only maintainer for those16:05
clarkbrosmaita: I believe there were threshold rules in place as a decision was made that slightly translated projects were worse than just the default of english16:05
clarkbif it was the bot that removed the files that is likely why16:05
rosmaitaclarkb: i think that's what happened16:05
gmannrosmaita: there were some discussion last month on overall translation status16:05
clarkbthe translation tooling definitely needs some help16:06
clarkbzanata isn't really something we can keep relying on16:06
gmannthis one http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026244.html16:06
rosmaitagmann: ty16:06
clarkbbut ya the threshold rules (I think 70% maybe?) are likely why it was removed if by the bot16:06
gmannrosmaita: is anyone complained about removal or you noticed it?16:07
rosmaitait came up in a discussion about logging messages vs. exception messages that end-users might see16:07
rosmaitano one complained16:07
rosmaitabut everyone thought it was weird that some major languages were removed16:08
dansmithmeh french? never heard of it.16:08
clarkbrosmaita: keep in mind that its the churn to the source strings that causes that ultimately16:08
rosmaitai guess the threshold is per-project? so we might have no french in cinder, but have frence in glance?16:08
clarkbrosmaita: like ya it was removed, but it was removed because your strings have updated and there isn't anyone to translate them (or they aren't translating them quickly enough to keep up)16:09
clarkbyes per project16:09
rosmaitaok, so we could address this ourselves by recruiting some appropriate people16:09
jungleboyjrosmaita:  So, we just need to get ttx to help out then.  ;-)16:10
clarkbrosmaita: and/or reduce string churn16:10
clarkbthings were translated until you changed the source16:10
jungleboyj:-)16:10
gmannwe are struggling on more translator maintainer in i18 SIG and as per last check its ianychoi[m] continue to help but it is great if people need it can come and help 16:10
rosmaitawell, it's hard to prevent churn when people insist on correcting typos!16:11
rosmaitabut maybe if we explain correcting english means no more french or italian, people will let those slide16:11
gmannrosmaita and i agree to discuss and find some solution if we can in PTG16:12
gmannrosmaita: can you please add it etherpad and we will try to ring ianychoi[m] also there 16:12
rosmaitasure, will do16:13
gmannthanks 16:13
jungleboyjrosmaita:  Never!  Typos must go!16:13
*** gmann is now known as gmann_afk16:13
rosmaitaclarkb: your remark about zanata ... what's the problem with it?16:13
clarkbrosmaita: red hat killed it years ago and is no longer maintained16:13
clarkbIdeally someone would find time to plan and perform a migration to another tool16:14
rosmaitathat was my next question!16:14
clarkbit is unfortunate because zanata worked really well and I think the translators enjoyed using it too16:14
fungirosmaita: the last time we looked into options, weblate looked promising, and they have a hosted service we could rely on (like back when we used transifex) so opendev wouldn't have to run the service for it16:15
rosmaitahmmm ... zanata says there are 136394.92 hours remaining, i guess of stuff to be translated16:16
rosmaitathat's kind of a lot16:16
fungiopenstack is kind of a big project16:16
rosmaitaand apparently a very verbose one16:17
spotz_Hey all, if we can get a list of the centOS issues I’ll get a list of folks we can work with16:18
fungispotz_: the anecdotes i heard seemed like they could be kernel layer or unfortunate hypervisor level interactions leading to things just dying in hard to diagnose ways, but hopefully someone has more details16:19
clarkbspotz_: the one I was aawre of was they updated ping to no longer be setuid and instead rely on a special sysctl setting to allow non root to ping. Except that sysctl (part of systemd) didn't get updated as part of that change (use case for zuul and depends-on). They then updated sysctl but found something about that update was broken. Eventually I believed this was fixed, but16:19
clarkbIMO the immediate reaction should've been to just revert the setuid removal. Then redeploy properly.16:19
clarkbThe major issue being everything seeemed to flow through rhel, but since rhel isn't released continuously like centos they weren't catching the issues when landing stuff to rhel. Instead they were caught one at a time in centos as they pulled from rhel and it led to very long period of time before it was actually fixed16:20
fungipulling from future-rhel-9 into centos stream 9 i guess?16:21
clarkbfungi: this was on stream-816:21
clarkbbut ya future rhel 8 into stream-816:21
fungioh, wow. why would they make that change in rhel 8? that itself is kinda insane16:21
clarkbrather than fixing stream-8 directly and/or reverting16:21
fungi"ping is no longer setuid" seems like the sort of thing you wouldn't backport to an already released major rhel version16:22
spotz_It’s supposed to be changing with 9 so it’s more cent then rhel for most things. Ok 8 hasn’t moved to that flow yet so not surprised there 16:23
clarkbya if I could give any advice it would be to encourage reverts for problems that can be reverted then take another pass at it with more planning16:24
clarkbif you are going to continuously release your software this seems imperative16:24
clarkbthen if I thought I'd get away with a sales pitch using a tool that enforced ordering of dependencies in changes (like zuul) would go a long way to avoiding these problems in a continuously released distribution16:25
fungiright, if centos stream is intended to be used in production, then taking care to provide a production level experience to its users (like they had in pre-stream)16:25
clarkbultimately the issue was that the ping update depended on a systemd (sysctl) update. One landed before the other16:25
spotz_Ok screenshotted this to del with next week when back at work. But hopefully we’re not seeing that order of things with 9:as it’s supposed to have a better workflow16:25
fungiand yes, zuul is great for testing interdependencies and enforcing correct ordering of changes16:27
clarkbAnother thing I noticed whe nthe ping thing happened is that the centos imports from rhel lose almost all context from upstream16:27
clarkbthis might be a feature, I'm not sure. But it makes it really difficult to see what is changing without reding the actual diffs16:28
*** gmann_afk is now known as gmann16:29
opendevreviewGhanshyam proposed openstack/governance master: Appoint Wu Chunyang as Trove PTL  https://review.opendev.org/c/openstack/governance/+/83315217:27
gmannwuchunyang ^^ need your +1 as ack.17:27
*** pojadhav|dinner is now known as pojadhav17:48
opendevreviewSlawek Kaplonski proposed openstack/governance master: Add slaweq nomination as vice-chair  https://review.opendev.org/c/openstack/governance/+/83317120:05

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!