Wednesday, 2023-05-31

iurygregoryJayF, regarding bugfix branches, we don't need them downstream anymore from what I've checked, I will let rpittau confirm this =)00:45
opendevreviewVerification of a change to openstack/ironic stable/xena failed: Fix Cinder Integration fallout from CVE-2023-2088  https://review.opendev.org/c/openstack/ironic/+/88358005:44
adam-metal3Hello Ironic! So I am bit confused I thought the Ironic community has migrated back to launchpad for planning, but I only see bugreports there, is it so, that bugs should be reported on launchpad and new feature proposals on StoryBoard?06:41
dtantsuradam-metal3: everything goes to launchpad07:58
dtantsuryou can tag feature requests as [RFE]07:58
adam-metal3dtantsur: Thanks!07:59
rpittaugood morning ironic! o/07:59
adam-metal3rpittau; hi !08:00
rpittauJayF, iurygregory, we don't use bugfix branches anymore downstream BUT we're going to use them for metal3, specifically for the ironic container, and BTW I'm going to request a new bugfix branch this week :)08:00
rpittauhey adam-metal3 :)08:00
*** Continuity_ is now known as Continuity08:28
opendevreviewVerification of a change to openstack/bifrost master failed: Reduce multiple tasks to task with loop  https://review.opendev.org/c/openstack/bifrost/+/87718610:57
iurygregorygood morning Ironic11:21
iurygregoryrpittau, "bugfix/18.1 (xena) (should be supported until June 2023)" JayF wants to remove the branches that are reaching the eol time, there is an email on openstack-discuss "[ironic] Retirement of ironic-prometheus-exporter bugfix/2.1 branch" but involves the other projects we have =) 11:23
rpittauiurygregory: bugfix branches have a life expectancy of 6 months, after that time they're not supported and they should probably be retired/removed, so I'm fine with that11:27
rpittauif 18.1 is to be supported until June 2023, then after June will be EoL :)11:29
opendevreviewMerged openstack/bifrost master: Set [inspector]require_managed_boot explicitly  https://review.opendev.org/c/openstack/bifrost/+/87746912:01
opendevreviewMohammed Boukhalfa proposed openstack/sushy-tools master: Add fake_ipa inspection, lookup and heartbeater to fake system  https://review.opendev.org/c/openstack/sushy-tools/+/87536612:47
JayFrpittau: the reason that one bug fixed branch is labeled June 2023, is last time someone told me they are only 6 months old and I wanted to retire them I was told not to do that one until June 2023.13:32
JayFSo it's sort of hard to keep track of what being used and what's not being used when all I have is random comments in IRC every now and then 😄13:33
rpittauJayF: I thought we clarified the lifecycle of the bugfix branches, but apparently we haven't written anything down about that :/13:39
opendevreviewAlex Welsh proposed openstack/bifrost master: Replace Cirros references with generic descriptors  https://review.opendev.org/c/openstack/bifrost/+/88394313:41
opendevreviewAlex Welsh proposed openstack/bifrost master: Improve downloaded deployment image support  https://review.opendev.org/c/openstack/bifrost/+/88488813:41
rpittauJayF: I'm going to review the bugfix branches we still have and update the etherpad according to the 6 months support time, and since I'm there I will propose a patch to make that official since I can't find any mention of that anywhere in the docs13:47
opendevreviewAlex Welsh proposed openstack/bifrost master: Improve downloaded deployment image support  https://review.opendev.org/c/openstack/bifrost/+/88488813:52
opendevreviewAlex Welsh proposed openstack/bifrost master: Improve downloaded deployment image support  https://review.opendev.org/c/openstack/bifrost/+/88488813:53
opendevreviewRiccardo Pittau proposed openstack/ironic master: Be explicit about bugfix branches support lifetime  https://review.opendev.org/c/openstack/ironic/+/88488913:55
opendevreviewRiccardo Pittau proposed openstack/ironic master: Be explicit about bugfix branches support lifetime  https://review.opendev.org/c/openstack/ironic/+/88488913:57
rpittauJayF: I've updated the etherpad and cleaned up the supported bugfix branches14:26
JayFrpittau: thank you so much, I'll look at it when I can point my brain upstream15:00
rpittauno problem15:01
opendevreviewAlex Welsh proposed openstack/bifrost master: Improve downloaded deployment image support  https://review.opendev.org/c/openstack/bifrost/+/88488815:03
*** Continuity__ is now known as Continuity15:15
JayFI'm really confused. ilo-redfish is mentioned as a driver in the ilo docs, but I can't find reference to it in the ironic repo (git grep ilo-redfish)15:18
JayFanyone know what's up?15:18
JayFrpittau: ack. If you have time, can you email list about the removed bugfix/{} branches and banner their retirement? I can push the buttons in a couple weeks15:25
JayFif not, let me know and I'll lookup which ones you pulled and do it myself15:25
TheJuliauhh... ilo internally switches out to redfish15:27
TheJuliailo5 I think is what they mean, maybe?15:27
rpittauJayF: will try to do it before EOD15:28
JayFyeah it's very badly written15:31
JayFrpittau: thank you, no real rush. I just want to billboard at all before we retire them :D 15:31
TheJuliaJayF: the other conundrum is sone "HPE" gear, is not "Proliant" and doesn't just work with the ilo driver15:32
TheJuliain those cases, stock "redfish" is the way15:32
JayFso context: I have a bug coming in soon from my downstream15:33
JayFnode is reserved, in AVAILABLE (no tgt prov state), no maintenance15:33
TheJuliareserved as in lock is held ?15:33
JayFlast thing Ironic conductor did was power status loop, found the node was wrong power status, tried to tell the node BMC to power on to make it match15:33
JayFyes15:33
JayFand the power change timed out15:34
JayFso I'm going to dig a bit to see if we're missing err handling somewhere, because that's what it smells like15:34
TheJulia... and the lock didn't get released?15:34
JayFyep15:34
JayFit was locked for like a week until the operator restarted the service today15:34
TheJuliadid the conductor crash in that process?15:34
TheJuliaweird15:34
JayFthere was no reported crash, I asked, but I don't have direct access to the logs15:35
TheJuliaso, it *should* have released the lock regardless on task exit, unless the task never exited...15:35
TheJuliawas there any stalled sockets to the remote bmc?15:35
JayFthere is no direct access to the conductor nodes, for security reasons15:35
JayFwe only have access to logs/db15:35
JayFbut the error *was in the log* that it failed to update the power status15:35
JayFso it at least knows it failed, even if it hung at that point15:36
TheJuliayeah15:36
TheJuliaweird15:36
JayFI feel like it's either going to be something horrible around locking or someone missed an error catch/throwing wrong exception/etc15:36
JayFI'm going to dig it, but Scott is supposed to be filing an issue with redacted logs/output15:36
JayF(two folks from my downstream, Scott and Ross, will be in Vancouver too \o/)15:37
TheJuliathis may also we need to find a reproducer or something to get a little more info15:37
TheJuliait is *super* weird15:37
JayFyeah audible WTF was garnered from me15:38
JayFespecially since it seems all conducotr-internal15:38
JayFso my "rabbitmq hopped your message away" default answer failed :P15:38
TheJuliayeah15:40
TheJuliathe rabbit monster went "om nom nom"15:40
JayFoooh, I wonder if I should have Scott check15:41
JayFto see if the power status loop on that conductor died after that15:41
TheJuliathat would be even more bizar15:41
JayFit would at least be a failure mode I've seen before15:41
JayFpower status loop crash or hangs on IO, leaves one node in a bad state15:41
JayFeither way, I'll dig it and see if I get anywhere15:42
rpittauJayF: sent :)15:54
rpittausee ya all tomorrow! o/15:54
JayFthank you15:58
JayFTheJulia: heh. The plot thickens but makes sense16:10
JayFnode was flapping power state due to a reboot loop (failing to pxe)16:11
JayFwhen the power status loop comes around, it sees node as "power off"16:11
JayFby the time it tells the bmc to power on, it's already on and the iLo gets angry16:11
JayFthe nodes end state? target_power_state: power on; power_state: power on; reservation [hostname]16:11
JayFwhich makes very much sense as an edge that could happen16:11
TheJuliainteresting17:42
JayFit's written up here: https://bugs.launchpad.net/bugs/202199517:42
JayFI'll keep it updated with any interesting information I ask for and get to try and troubleshoot it17:42
JayFsadly, we can't tell if the power status loop was still running; the only node it was performing actinos on was the broken one17:43
opendevreviewIury Gregory Melo Ferreira proposed openstack/ironic master: Add DB API for Firmware and Object  https://review.opendev.org/c/openstack/ironic/+/88306217:51
iurygregoryfunny thing I noticed, the class name in models.py should match the the object class .-. (I wasn't expecting this...)17:53
iurygregoryI've decided to squash the object patch with the db api layer since they have a lot in common17:54
TheJuliaMakes sense, a common quash18:01
TheJuliasquash18:01
JayFhttps://platform9.com/docs/bare-metal/overview this is interesting20:16
JayFhosted Ironic, apparently20:16
JayFIs anyone here, or a part of the community in general, affiliated?20:16
JayFhttps://superuser.openinfra.dev/articles/ironic-bare-metal-case-study-platform9/20:23
clarkbJohn Studarous was involved in doing openstacky things at platform 9 a while back20:24
JayFjust happy to hear of another company using Ironic to do good stuff20:27
JayFI'll have to browbea^W ask them nicely to contribute back ;) 20:27
NobodyCamGood afternoon Openstack folks21:40
NobodyCamHappy hump day21:40
TheJuliagood afternoon!22:39
NobodyCamo/ howdy TheJulia 22:45
NobodyCamit shouldn't be so difficult to get Devstack running :head desk:23:59

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