Monday, 2023-12-11

opendevreviewIury Gregory Melo Ferreira proposed openstack/ironic master: Move BFV job to non-voting  https://review.opendev.org/c/openstack/ironic/+/90326701:09
iurygregoryJayF, dtantsur, rpittau ^ we probably need to disable till we can figure out the reason (I think is probably something related to the changes Jay mentioned, since on Thursday everything was ok)01:12
JayFiurygregory: I am -0 to that move; I'd instead prefer us move quickly to identify+revert the breaking change on the nova side, right now master state is broken which is not awesome. This will be a big focus for me tomorrow.02:34
opendevreviewparesh proposed openstack/ironic master: Fixes Raid creation in iLO6 and other BMC with latest schema  https://review.opendev.org/c/openstack/ironic/+/90274407:40
opendevreviewparesh proposed openstack/ironic master: Fixes Raid creation in iLO6 and other BMC with latest schema  https://review.opendev.org/c/openstack/ironic/+/90274407:46
rpittaugood morning ironic! o/07:50
opendevreviewVasyl Saienko proposed openstack/networking-baremetal master: Do not try to bind port when we can't  https://review.opendev.org/c/openstack/networking-baremetal/+/90325208:00
rpittauJayF, TheJulia, dtantsur, iurygregory: I see some changes in nova between December 7 and 8 that may have caused the bfv issue, all involving migration to openstacksdk, chain starts here https://review.opendev.org/c/openstack/nova/+/65969108:02
dtantsurJayF: I don't agree with this take. If the regression was in our project, we could say that fixing it quickly is preferred. But we cannot wait for the turnaround on the nova side.09:49
dtantsurEspecially with https://review.opendev.org/c/openstack/ironic/+/903185 hanging in limbo breaking unclear number of redfish deployments09:54
dtantsurJayF: https://review.opendev.org/c/openstack/nova/+/90332410:05
dtantsurlet's see what gets merged first, I'll throw a testing patch in10:05
opendevreviewDmitry Tantsur proposed openstack/ironic master: [DNM] Test the BFV job fix  https://review.opendev.org/c/openstack/ironic/+/90332510:07
dtantsurrpittau, iurygregory ^^^10:08
dtantsurmeanwhile,10:13
dtantsurTheJulia: do you know if https://docs.nvidia.com/networking/display/bluefield2dpuenug/supported+interfaces#src-37852583_SupportedInterfaces-NC-SIManagementInterface means that they also rely on NC-SI? Or is it just an option?10:13
opendevreviewDmitry Tantsur proposed openstack/bifrost master: Switch IPA building to Debian Bookworm  https://review.opendev.org/c/openstack/bifrost/+/90316210:40
jrosserdtantsur: that connector is to allow the host system BMC to share the physical port on the DPU10:55
dtantsurjrosser: yep, but is it mandatory?10:56
jrosserwell that entirely depends10:56
dtantsuror do you expect the most people to have a separate BMC NIC?10:56
jrosserif you manage the host through a dedicated OOB port, or it shares an existing onboard port and the use case is OK with that, then so be it10:57
jrosserbut if the use case mandates that host OOB is presented on the DPU physical port then it would be mandatory10:57
dtantsurThe background of my question is: we know that some NC-SI implementation have problems with Ironic because such nodes cannot be powered off (you lose your BMC access)10:58
jrossernot all motherboards present the other end of that connector either10:58
jrossertbh that does not surprise me10:58
dtantsurSo, if we're going to see more such hardware, it's a reason for us to raise the priority of fixing NC-SI support.11:00
jrosseri have bluefields and don't use the NCSI connector, so in that sense it's not mandatory11:00
dtantsuraha. good to know, thanks!11:01
jrosserbut in other situations i have other NIC which absolutely have to use NCSI, and it has been difficult11:01
dtantsurI see11:01
jrosserrelatedly we have some newer hosts where the ncsi is wired to an OCP slot rather than being presented as a ribbon cable connector, so you have no choice but to select an OCP NIC if you want to use it11:05
jrosserdtantsur: one issue we did have with ncsi in general was wildly different performance between nic vendors11:07
opendevreviewVerification of a change to openstack/ironic-python-agent master failed: Fix referencing to the raid_device var which is not set  https://review.opendev.org/c/openstack/ironic-python-agent/+/90032411:07
jrosseron one vendor you could straightforwardly boot from virtual media over it, on another vendor the performance was so incredibly slow that uploading the virtual media to the BMC was essentially impossible11:09
dtantsurfun times11:17
iurygregorygood morning Ironic11:22
opendevreviewDmitry Tantsur proposed openstack/sushy-tools master: Expose VirtualMedia on Systems in addition to Managers  https://review.opendev.org/c/openstack/sushy-tools/+/90333111:48
opendevreviewVasyl Saienko proposed openstack/networking-baremetal master: Do not try to bind port when we can't  https://review.opendev.org/c/openstack/networking-baremetal/+/90325212:39
opendevreviewDmitry Tantsur proposed openstack/sushy-tools master: Expose VirtualMedia on Systems in addition to Managers  https://review.opendev.org/c/openstack/sushy-tools/+/90333112:44
iurygregoryFYI: today I won't be able to join the upstream meeting13:07
TheJuliagood morning13:38
n0obgood afternoon13:40
JayFdtantsur: the redfish breakage needing to land is a good point15:00
JayFdtantsur: ty for the fix after looking yesterday I suspected the shape would be something like that15:01
JayFno idea how this ever passed our CI in the first place though15:01
JayF#startmeeting ironic15:01
opendevmeetMeeting started Mon Dec 11 15:01:29 2023 UTC and is due to finish in 60 minutes.  The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'ironic'15:01
JayF#topic Announcements/Reminder15:01
JayF#info Standing reminder to review patches tagged ironic-week-prio and to hashtag any patches ready for review with ironic-week-prio: https://tinyurl.com/ironic-weekly-prio-dash15:01
TheJuliao/15:03
TheJuliadtantsur: w/r/t ncsi, just an option afaik15:03
JayFNo action items from last week, skipping that one15:03
JayF#topic Caracal release schedule15:03
JayF#info Next milestone C-2, Jan 1115:03
JayF#topic Meeting schedule for holiday15:03
JayFI propose we cancel the 12/25 and 1/1 meetings. Well, I propose I won't be here, you all can do what you want with Christmas + New Years Day :D15:04
JayFIf I don't hear an objection going to move ahead with that plan15:05
rpittauo/15:05
JayF#action JayF to email mailing list about Christmas + New Year's Day meetings being cancelled15:06
JayF#topic Review Ironic CI Status15:06
JayFSo Ironic CI is currently busted, BFV job was broken by some Ironic driver changes that landed15:06
dtantsurThe bfv fix hasn't merged yet..15:06
JayFthe fix is in the nova gate, if it gets clogged up we can push a quick -nv to get things free15:07
JayFI'm a bit confused how this landed broken, I had a patch w/Depends-On on the tip that passed all our jobs15:07
opendevreviewVerification of a change to openstack/ironic-python-agent master failed: Fix referencing to the raid_device var which is not set  https://review.opendev.org/c/openstack/ironic-python-agent/+/90032415:07
TheJuliaI don't know what patches in question, but it looked like it was lacking a key we expected to be present15:08
TheJuliapossibly a race condition?!15:08
JayFWell, there was a comment on the original change that it could be racey, but with dtantsur's fix, it doesn't look like it could've ever worked15:08
JayFso I'm thinking maybe a follow up just to ensure our jobs are running nova from git15:08
JayFwell, we know it is, because they broken15:09
JayFEither way, we know the path forward, path behind matters less, not like we push major changes to Ironic<>Nova driver often.15:09
JayFAnything else on CI/Nova breakage?15:09
dtantsurWe cannot run nova NOT from git15:10
JayFfair15:11
JayFmoving on15:11
JayF#topic Bug Deputy15:11
JayFI was the bug deputy. I triaged some bugs. I did not put together a report.15:11
JayFI'll note for whoever is taking it next (I can go another week if needed), there's something mildly screwy with the dashboard15:11
JayFI didn't have time to look, but either launchpad API returns bad data or something in our bug deduplication breaks on non-Ironic projects15:11
JayFbut I managed to triage most new bugs15:12
rpittauI can go for it this week15:12
JayF#action rpittau to be bug deputy this week15:12
JayFwell, I say I didn't have time to look; I looked; I didn't solve lol15:12
rpittau:D15:12
JayFWe have lots of RFEs up15:13
JayFincluding some I proxied as bug deputy15:13
JayF#topic RFE Review15:13
JayFdtantsur: has three, going to link them in and let you talk about them15:13
JayF#link https://bugs.launchpad.net/ironic/+bug/204554815:13
JayF#link https://bugs.launchpad.net/ironic/+bug/204555115:13
JayFboth carryovers from last week, we didn't have many folks in the meeting and wanted more people to see these15:13
JayFthey were provisionally approved15:13
dtantsurYeah, thanks!15:13
JayF#link https://bugs.launchpad.net/sushy-tools/+bug/2046153 "Testing the minimal subset of Redfish features" is the new one for dtantsur 15:14
TheJuliano objection to 2045548, only concern about the kernel command line length limit15:14
dtantsurTheJulia: do you remember the limit from the top of your head?15:14
TheJulia1024 chars15:14
TheJuliatotal15:14
dtantsurI think we're quite good still15:14
TheJuliayeah, maybe move it to the end *just in case*15:15
TheJuliaI think the kernel truncates it, if memory serves it is also configurable and at one point was 256 charts15:15
TheJuliachars15:15
dtantsurI'll how doable that is (without relying on Python dict ordering)15:15
TheJuliaI was thinking template wise15:15
TheJuliafwiw15:16
dtantsurI think all these arguments end up in a dict.. anyway, technical details15:16
TheJuliathey do, but the actual line draws from several different fields in the tempalate, the actual consumption side, yes hits  dict and entires may be truncated15:16
JayFhow long until ipa-b64-config=dgjskljdfhgksljdhg15:16
dtantsurlol15:17
JayFI'm only half-joking, we're getting more complex in the preboot configuration we need15:17
dtantsurwith virtual media, we should start embedding it as a file already (we actually have all the code there)15:17
JayFthat is worthy of being written up15:17
* JayF notes he is +1 to all the proposed RFEs15:17
dtantsurI'll try to.. but I cannot do everything at once15:18
TheJuliaThe second rfe, I guess I'm trying to understand why we feel the need to create the second script/why we feel it is explicitly needed. I.e. is there a path not to have it, and do we need more, or less complexity to get there15:18
TheJuliaeverything at once is impossible15:18
dtantsur2045551 is a bit more interesting. It's continuation of the whole "self-configuring ironic" thing15:18
dtantsurto be clear: this script exists now, it's just normally hand-written15:18
dtantsurwe *could* roll this logic into boot.ipxe, but then we won't be able to reuse the ipxe_script_template15:19
dtantsurlike, I don't want https://github.com/metal3-io/ironic-image/blob/main/ironic-config/inspector.ipxe.j2 to be handwritten any more15:19
TheJuliaI'm personally pro all together, if possible15:19
dtantsurNot sure I know what you mean15:20
TheJuliafrom my pov, there is no technical reason why we've kept that pattern, out of "this is the way we always did it"15:21
TheJuliaand we should evolve that. What that looks like exactly, more so depends on the overall requirements15:21
dtantsurit falls the loop <MAC1>, <MAC2>, ..., fallback15:21
dtantsurwhere do you suggest it goes, https://opendev.org/openstack/ironic/src/branch/master/ironic/drivers/modules/boot.ipxe ?15:21
TheJuliayes, except what did we do in bifrost?15:21
dtantsursame as in metal3: a separate file15:22
dtantsurit's also the approach we document for ironic-inspector15:22
TheJuliawe could take boot_failed path15:22
TheJuliaoh, so bifrost got changed way from the single file ?15:22
dtantsurif we add that to boot.ipxe, then the operators who customize boot.ipxe and ipxe_config.template will need to change their templates15:22
TheJuliayes15:22
dtantsurbifrost has always worked like that15:22
TheJuliathat is unavailable15:22
dtantsurnothing I touched implemented inspection as part of boot.ipxe15:23
dtantsur(I don't think TripleO either)15:23
TheJuliamaybe bifrost for the past five years, but a very long time ago it was a single file15:23
dtantsurpossibly? if so, it's long gone15:23
TheJuliayeah15:23
dtantsurI'm not sure why we'd ask people to duplicate their templates though15:23
TheJuliait worked quite nicely, from my point of view, but that was a long time ago15:23
TheJulianor am I15:23
dtantsur(not my pain any more since we don't customize ipxe_config.template, but still)15:23
TheJuliaother than hardware discovery15:24
dtantsurI'm afraid your memory misleads you15:24
dtantsurhttps://opendev.org/openstack/bifrost/commit/c1f9beac6358efd70a4197f57f71ef98499fa7d6 is your patch that introduced inspector support, and it uses the separate file15:25
TheJuliasweet!15:25
dtantsurThe value I see in the separate file is to reuse ipxe_config.template out of box15:25
* TheJulia shrugs 15:26
dtantsurso, people who customized something for cleaning, deployment and managed inspection will get the same thing for the unmanaged inspection15:26
dtantsurI'm worried about managed and unmanaged inspection ever diverging15:26
TheJuliayeah, I just worry how much debt we're carrying for that and if we should make it more streamlined, or not15:26
JayFI need to step away for a minute; if you all get done with this next up are those two sushy-tools RFEs which I'm +1 with very low context on (I put them on the agenda from seeing them in triage)15:27
JayF#chair TheJulia dtantsur 15:27
opendevmeetCurrent chairs: JayF TheJulia dtantsur15:27
TheJuliaI guess i always thought we were going to try and drift everything towards managed15:27
TheJuliaanyway, we should carry on15:27
dtantsurWe will try, but we don't succeed right away15:27
TheJulianaturally :)15:27
dtantsurPeople want auto-discovery all the time...15:27
TheJuliatrue15:27
TheJuliaand we have to still soft of have that as a path, but that doesn't mean things can't evolve15:27
TheJuliaOnward?15:28
dtantsurMmmm, so no consensus?15:28
TheJuliadtantsur: lazy consensus?15:28
dtantsurI thought you were against the RFE as it's written?15:28
TheJuliaeh, not a fan, but doesn't mean I'm going to take a hardline stance on it15:29
TheJuliaI'm more asking question for the big picture15:29
TheJulia#link https://bugs.launchpad.net/sushy-tools/+bug/204590615:29
TheJulia#link https://bugs.launchpad.net/sushy-tools/+bug/204590815:29
dtantsurI don't have anything against extending sushy-tools as long as we have some understanding why people are doing it15:30
dtantsuri.e. they're not doing it in production15:30
TheJulia++15:30
TheJuliaThe first one, seems like a "non-issue"/"just do it"15:30
JayFI think these are the folks who came by here the other day15:30
JayFsomeone dropped in and asked if we'd be OK with getting features into sushy-tools15:30
dtantsuryeah, SKU,Serial are not even RFE-worthy15:30
JayFand I gave them the usual interrogation; sounds like they are building a product in the category of Ironic15:30
JayFand want to enhance the testing suite in sushy-tools more15:31
TheJuliathe latter one, yeah, I'm trying to understand why15:31
dtantsurif it's for testing their product - no problem15:31
dtantsuras long as it does not end up putting more burden on us15:31
JayFTheJulia: I could easily see a datacenter management product monitoring power usage, especially if it's oriented differently than OpenStack15:31
JayFdtantsur: if anything, getting another project depending on sushy{,-tools} may reduce our overall burden15:32
TheJuliaJayF: of course, which I think kind of goes to dtantsur's comment15:32
dtantsurby the way, we should rename sushy-tools15:32
dtantsurit causes too much confusion with sushy proper15:32
TheJulia++++15:32
* dtantsur has recently learned there is an alternative to sushy-tools called ksushy15:32
TheJulia.....15:32
dtantsurikr?15:33
JayFtoo bad we didn't get OIF to (tm) sushy15:33
JayFlol;15:33
dtantsur:D15:33
JayFI'd be OK with a sushy-tools rename, maybe start a next-PTG etherpad with that?15:33
dtantsurpossibly15:33
TheJuliaor send something to the mailing list15:33
TheJuliadeferring to a PTG is a bad habit15:33
TheJuliabecause it forces discussion to halt until high bandwidth discussion15:33
JayFMaybe; but in this case I'd say halfway thru the cycle is a bad time to rename it15:34
dtantsurI'm +1 to both proposals if they don't end up dumping a lot of obscure code on us15:34
TheJuliawhich casues the topic to drop15:34
JayFwhich is the only reason I punted it; not for the high-bw but for the "after release" :)15:34
TheJuliaJayF: would need to be well communicated and we would already be into the next cycle once we reach the PTG15:34
TheJuliaI've left a comment on the first sushy-tools rfe15:34
JayFgood point15:34
dtantsurWe could have renaming by forking fwiw15:34
JayFso we are approving all those RFEs, right?15:35
dtantsurAlso dropping the static emulator that I'm afraid nobody uses15:35
dtantsuryeah15:35
JayF#info All RFEs evaluated at meeting are approved.15:35
JayF#topic Open Discussion15:35
dtantsurmmm, also mine? :)15:35
TheJuliauhh, we did't get to the last one15:35
dtantsurI don't mind it :D15:35
JayF#undo15:35
opendevmeetRemoving item from minutes: #topic Open Discussion15:35
JayF#undo15:35
opendevmeetRemoving item from minutes: #info All RFEs evaluated at meeting are approved.15:35
* JayF presses << on the tape player15:35
JayFWhat last one TheJulia?15:35
JayFTheJulia: we batched dtantsur'15:35
dtantsur#link https://bugs.launchpad.net/sushy-tools/+bug/2046153 Testing the minimal subset of Redfish features15:36
JayF**we batched dtantsur's three together, so even though we did them out of order, I thought we discussed all 5?15:36
dtantsurIt's not even really an RFE, more of a heads-up15:36
dtantsurI want us to avoid relying on a redfish implementation having ALL features we support15:36
TheJuliathe last one wasn't linked until when dtantsur just did so15:36
TheJuliathought we were going in order15:36
dtantsurfor that, I want a CI job that runs with a bare sushy-tools with no extras at all15:36
dtantsurobjections, concerns?15:36
TheJuliadtantsur: none really15:37
TheJuliait *should* be a test scenario in the tempest plugin explicitly instead of a separate CI job itself, if at all possible.15:37
JayFTheJulia: some mornings I can hide when I didn't get my coffee made before meeting... others... :)15:37
dtantsurTheJulia: I was thinking to just changing one non-vmedia job15:38
TheJuliaor just, run the emulator on minimal and make sure none of the advanced features are turned on15:38
dtantsurall I care about is that we don't e.g. depends on firmware versions being available as we've just accidentally done15:38
TheJuliaok15:38
dtantsur(context: https://review.opendev.org/c/openstack/ironic/+/903185)15:38
dtantsur(in the past, we accidentally made EthernetInterfaces required, breaking mmm Cisco?)15:39
TheJuliasweet!15:39
JayFsounds like a pretty good diea then 15:39
TheJuliayeah, every redfish feature we do, we should be checking "if the value is not none"15:40
TheJuliastupidly easy thing to miss though15:40
dtantsuron that note, I also want to document which resources we require and which we can use if they are present15:40
dtantsur(quite unfortunately, that the profiles work stagnated..)15:41
TheJuliaso a profile merged, but it is not quite clear15:41
dtantsurBackground: from time to time, our partners ask me for a list of Redfish APIs we require15:41
dtantsurso I essentially have this document downstream. I can just publish it.15:42
TheJuliamakes sense, the profile is rather broad15:42
TheJuliaAnd I'm not sure anyone is using it :\15:43
JayFIDK how to go about this; but if we could document quirks too that'd be cool15:43
JayFe.g. the bug around gigabyte servers wanting a different payload for boot mode than anything else15:43
dtantsurWe're trying to fix such things instead :)15:43
TheJuliaDid we get a reply to that one?15:43
JayFhttps://bugs.launchpad.net/ironic/+bug/2045191 yes15:44
JayFIn fact it looks very good15:44
JayFI left it incomplete because I wanted someone more redfishy to verify it was enough info15:44
JayFbut it LGTM15:44
-opendevstatus- NOTICE: Zuul jobs reporting POST_FAILURE were due to an incident with one of our cloud providers; this provider has been temporarily disabled and changes can be rechecked.15:44
JayFI also reached out a handful of different ways trying to get a contact in Gigabytes' server engineering team15:44
JayF#topic Open Discussion15:45
JayF(we are basically already doing this, just reflecting the reality)15:45
dtantsuranother fishy item, just as a heads-up: https://review.opendev.org/c/openstack/sushy-tools/+/90333115:45
TheJuliaoh joy, yeah, what we have to do with them was semi-incompatiable with some of the other vendors15:45
TheJulia..... hmmmmmm15:46
JayFThis is part of why I'm trying to work out a contact in their server group :D 15:46
JayFSeems like the sort of thing that ... collaboration could improve future versions of15:46
TheJuliayeah15:46
JayF(I do not think I was/will be successful FWIW)15:46
TheJuliaI don't know if I'll have time to take a look this week, this week is shaping up already to be a very busy week15:47
JayFI'm going to be focusing primarily on nova driver bits, trying to get sharding spec mergable and getting all the code lined back up15:48
JayFso I can work on those tempest tests again 15:48
TheJuliaI suspect we could likely just teach ironic to recognize such a constrant and send back the same value or something slightly wicked15:48
TheJuliabut where in that sequence is sort of a question, I'll need to look a little deeper15:48
JayFMakes sense.15:49
JayFOh, one thing I wanted to mention for open discussion15:50
JayFright now there are patches up in openstack/releases to retire Ironic Train/Ussuri branches due to the unmaintained branches migration15:50
JayFAIUI devstack/various supporting CI cast things are going away for Train/Ussuri15:50
opendevreviewRiccardo Pittau proposed openstack/bifrost master: Fix disable-dhcp option in playbook  https://review.opendev.org/c/openstack/bifrost/+/90313515:50
JayFif anyone wants to keep these up, and in unmaintained/* branches, they have [slightly less than, at this point] a month to go -1 that patch and volunteer to be the steward of those branches15:51
JayFhttps://review.opendev.org/c/openstack/releases/+/90319915:51
JayF#info Train is scheduled to be EOL: https://review.opendev.org/c/openstack/releases/+/903199 -- if you wish it to not EOL, you must -1 that patch and volunteer to steward the branch.15:51
JayFAnything else about that or for open discussion?15:52
TheJuliaI guess the Train is soon departing the last station15:52
JayF4+ years is too good of a run for a single release of software :D 15:53
JayFI'm going to close out the meeting if there's nothing else?15:53
TheJulia... unless we're required to release for 5 years15:54
TheJuliahttps://www.digitalsme.eu/cyber-resilience-act-the-eu-strikes-a-deal-on-security-requirements-for-digital-products/15:54
JayFI think this is confirmation we're off the Ironic path for the day :D 15:55
JayF#endmeeting15:55
opendevmeetMeeting ended Mon Dec 11 15:55:36 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-12-11-15.01.html15:55
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-12-11-15.01.txt15:55
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-12-11-15.01.log.html15:55
JayFTheJulia: put that up there with "nobody outside the US deserves >40 bits of encryption" in the crappy tech law hall of fame15:56
TheJulialolz15:56
TheJuliaso does that mean the 128bit encryption service pack accidently applying to the 40 bit NT4 machine... comes in, third?15:57
JayFaha, https://review.opendev.org/c/openstack/nova/+/867798 was what I tested on top of15:58
JayFso we broke in the middle of the patch chain15:58
JayFthat at least explains why things happened to break up15:58
JayFs/up/us15:58
JayFdtantsur: I'll point out, eventlet maintainer just handed over keys to other maintainers16:01
JayFdtantsur: so we might have a path outta your py3.6 pain16:01
dtantsur\o/16:02
rpittauwow16:03
JayFhttps://github.com/eventlet/eventlet/issues/82416:03
TheJuliawow, sweet16:03
JayFI feel like all I did was send like, 3-4 emails and have a bunch of conversations and then hand over to Herve16:03
JayFbut somehow still feels like the most impactful thing I've gotten moving in a while lol16:03
TheJuliawell, short term wise :)16:04
JayFI think it'16:04
JayF*it's pretty obvious I follow the "sunshine and rainbows and inspirational" viewpoint of OSS16:04
TheJulialol16:05
JayFand "saving a decade+ old project from lack of maintainership to provide an offramp with a peaceful transition of power" is the Mona Lisa of inspirational OSS moments lol16:05
TheJuliaeh, yeah16:05
JayFThat's one of the things I appreciate the most about OpenStack; we do a decent job (at least on the primary projects) of having continuity of maintainership over time16:06
dtantsur++16:28
opendevreviewDmitry Tantsur proposed openstack/sushy-tools master: Add feature sets to test with different available feature  https://review.opendev.org/c/openstack/sushy-tools/+/90336016:49
opendevreviewDmitry Tantsur proposed openstack/ironic master: [DNM] Test with reduced sushy-tools feature set  https://review.opendev.org/c/openstack/ironic/+/90336116:51
opendevreviewDmitry Tantsur proposed openstack/ironic master: [DNM] Test with reduced sushy-tools feature set  https://review.opendev.org/c/openstack/ironic/+/90336116:53
rpittaugood night! o/17:08
JayF\o17:09
mnasiadkadtantsur: tried c9s based IPA on Yoga - but getting Unexpected exception performing clean step delete_configuration. UnboundLocalError: local variable 'raid_device' referenced before assignment - and fresh c8s builds suffer from eventlet issue (I think) - so I'm a bit stuck with my sw raid problem ;-)17:32
stevebaker[m]good morning19:07
TheJuliagood morning19:13
opendevreviewBaptiste Jonglez proposed openstack/networking-generic-switch master: Introduce NGS agent design  https://review.opendev.org/c/openstack/networking-generic-switch/+/89704719:25
opendevreviewIury Gregory Melo Ferreira proposed openstack/ironic master: [WIP] RedfishFirmwareInterface - Unit Tests & More logs  https://review.opendev.org/c/openstack/ironic/+/90337920:20
JayF> tempest-integrated-compute TIMED_OUT20:21
JayFnooooooooooooo20:21
JayFafter 5 hours and 30 minutes in the gate20:21
iurygregoryyeah20:21
JayFthe nova driver fix went boom :( nova gate is really unstable and everything getting batched makes it more painful20:21
iurygregoryI just saw that 20:21
iurygregory=( 20:21
JayFiurygregory: fwiw, when I say -0, I just mean *I personally* don't wanna +2/-1 such a change20:21
JayFiurygregory: doesn't mean you couldn't have done it anyway or I wouldve been upset if you did20:22
iurygregoryJayF, I totally understand =)20:22
JayFfor now we need to -nv it I suspect :(20:22
iurygregoryprobably, I think it's valid going to nv (if we are in a hurry), but 5hrs and 30min to get the timed-out hurst quite a lot 20:26
JayFwell, let me put it this way, at last TC meeting (or maybe one before?) someone reported needing 10+ rechecks to land something in nova20:33
JayFso while I was gung-ho this weekend to find a fix, get it in the gate, and be hopeful, I only have hope for one ride around the block :D 20:34
JayFlol20:34
iurygregory10 rechecks?20:35
JayFyep20:35
JayFwe do a gate health check in tc meetings, so I hear when the shared pieces are in especially bad shape20:36
JayF(fwiw we are usually in good shape in Ironic comparatively .... except when we're not LOL)20:36
iurygregoryif we consider 7h:30min (since the job that failed took 2hrs in check) I hope my math is correct.. each run takes 450min, 4500min is 75hrs20:37
iurygregoryOMG!20:37
JayFwell remember that the 5:30 represents multiple failures due to how the gate is stacked20:38
JayFwhen I first checked that change this morning, it was like, #12 down the list20:38
JayFrandom failures took out changes above it in the gate list over and over for hours, until finally it got a chance to get far enough to fail on its own lol20:38
JayF(because we try to, for instance, if 10 things wanna merge across devstack/nova/cinder/etc -- anything with a shared gate -- we merge them all together and try to get them landed with *one* shared CI job)20:39
* TheJulia wonders if the gate should maybe just have a depth limit on speculativeness20:39
JayFThat's about as deep as I've seen one, I suspect on Monday mornings it might get silly as people start approving things first thing20:39
*** dmellado2 is now known as dmellado23:16

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