15:00:36 #startmeeting ironic 15:00:36 Meeting started Mon Jun 19 15:00:36 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:36 The meeting name has been set to 'ironic' 15:00:44 Goooood morning Ironic, who all is here for our meeting today 15:00:50 o/ 15:00:52 o/ 15:01:08 o/ 15:01:18 I would expect lower attendance than usual as some contributors may still be on holiday/travelling home from the summit. 15:01:26 #topic Announcements/Reminder 15:01:34 #note 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-dash 15:02:02 #note Please ensure to fully investigate CI failures, and especially make note of TIMED_OUT failures in unit tests, and do not spam recheck as we are trying to work the issues out. 15:02:18 #topic Review Action items from previous meetings 15:02:36 last meeting was June 5, and there were no actions. Moving on. 15:02:50 #topic Review Ironic CI Status 15:03:05 does anyone have a meaningful update on the unit test pain? 15:03:12 I lost the thread on that at summit 15:03:37 well my patches with the timeout setting are just waiting for a +W :) 15:03:46 they could maybe give us some more hints 15:03:57 can you link that here? I'll land it 15:05:03 yep, it's a chain that starts from here https://review.opendev.org/c/openstack/ironic/+/885372 15:05:08 ack 15:05:13 I will ensure that lands after the meeting 15:05:18 thanks! 15:05:27 #topic Review ongoing 2023.2 Workstreams 15:05:38 #link https://etherpad.opendev.org/p/IronicWorkstreams2023.2 15:05:48 does not look like significant progress during summit week, as expected 15:06:11 Any comments on ongoing 2023.2 work before I move on 15:07:29 #topic Open Discussion 15:07:46 looks like bug 2021995 is on the agenda 15:07:51 Nisha_Agarwal: I presume that was you? What's up! 15:08:09 #link https://bugs.launchpad.net/ironic/+bug/2021995 15:08:09 JayF, Hi 15:08:13 Yes 15:08:33 we wanted to have clarity on the bug...how the bug is reproduced 15:08:40 and which hardware it is seen 15:09:08 It's iLO Gen 10 as mentioned in the bug; I don't know the specific SKU but you can ask there and Scott or someone else shoudl be able to get it 15:09:13 as of now if it is Gen10 or gen10+ then proliantutils bank on sushy for connecting to hardware for redfish calls 15:09:20 as far as reproduction, we haven't found a tight reproducer 15:10:07 I'd prefer we keep most of the commentary in the bug though; the impacted parties are not in the Ironic meeting, and we (me/you/the impacted bug filers) are all in different timezones 15:10:19 so it'd be easier to coordinate there 15:10:46 as far as i understand, during power_state_sync ironic is trying to power on while for some reason node is getting rebooted/power off 15:10:59 so the hardware is power looping in this case 15:11:00 and probably ilo is not able to understand which one to honor 15:11:04 it's set to pxe and is failing 15:11:10 may be a race condition in ilo 15:11:16 that's exactly what I'm wondering 15:11:41 and like, I don't expect the power status loop to get a sane value out of a node with flapping power statuses 15:11:42 but to connect to hardware team we need to reproduce the issue so that we could tell them the exact reproducer 15:11:48 but we should ensure it doens't get stuck or left in a bad state 15:12:09 there was a bug in gen9 for blade enclosures 15:12:17 around 6-7 years back 15:12:29 I believe you may be able to reproduce the circumstances by: 1) setting node to pxe 2) rebooting node into environment with no pxe boot 3) see power status flap 15:12:42 where i guess it was fixed for something similar in ilo(and a workaround was provided in proliantutils for gen9) 15:12:43 but I am remote to the hardware as well, so that's as far as my insight goes 15:12:57 if you have specific advice for trying to repro the bug, if we get that into the bug text I can make sure Scott sees it. 15:13:17 I tried to reach Aaron/Scott on the launchpad but didnt get any response so far 15:13:34 Scott was at Summit 15:13:34 even on IRC i couldnt get him 15:13:37 Ohk 15:13:44 he's not usually on IRC, the bug is the best way to communicate 15:13:51 Ok 15:13:54 and we work directly together so if I see a comment has sat for a few days, I'll pass it on :) 15:14:08 Thanks Jayf, 15:14:14 That will help 15:14:21 absolutely :) Thanks for taking a look! 15:14:30 Is there anything else for the meeting? More on this bug? Another open discussion topic? 15:14:33 i will try the reproducer you have given and see if we can hit the issue 15:14:45 for now this topic is doe 15:14:49 done* 15:14:56 Thank you 15:15:08 Going to give a minute for anyone to come forward with addl. open discussion topics 15:15:29 One thing to note: I'll be looking in a day or two to email a short summart of the summit PTG sessions; there are some notes in 15:15:38 #link https://etherpad.opendev.org/ironic-openinfra-2023 15:15:49 nice, was going to ask about that :) 15:15:53 but mainly just time spent thinking about what Ironic might look like in 5/10 years 15:16:01 and some design discussion for NGS 15:16:04 I think is mostly all that happened 15:16:49 I'm going to call it, thank you for those who've been here o/ 15:16:51 #endmeeting