| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2024-01-16 | |||
| 14:56:10 | opendevreview | Amit Uniyal proposed openstack/nova master: Fixes bug 2048184 https://review.opendev.org/c/openstack/nova/+/904817 | |
| 14:56:10 | opendevreview | Amit Uniyal proposed openstack/nova master: WIP: snapshot tests https://review.opendev.org/c/openstack/nova/+/905685 | |
| 15:12:02 | bauzas | SvenKieske: that sounds a new feature request, if you want to use it with nova | |
| 15:13:18 | gibi | dansmith melwitt bauzas : a fresh kernel panic on master https://review.opendev.org/c/openstack/nova/+/905671 | |
| 15:23:28 | dansmith | gibi: that's similar to the one that we opened against the ubuntu team and they asked us to repro on a newer kernel, so that's ... "good" | |
| 15:31:49 | SvenKieske | bauzas: yeah sure, I'm just a little baffled that I seem to be the first person to mention this feature request, as this is a rather useful feature, from a security perspective. | |
| 15:47:10 | kashyap | gibi: Hi, dansmith tells me you've ran into another kernel panic. Got a log link? | |
| 15:47:25 | dansmith | kashyap: https://review.opendev.org/c/openstack/nova/+/905671 | |
| 15:48:01 | dansmith | kashyap: also for future reference: https://meetings.opendev.org/irclogs/ | |
| 15:48:20 | kashyap | dansmith: Hi; thanks! | |
| 15:48:43 | kashyap | dansmith: Oh, yeah; I know we log upstream stuff; forgot for a min :) | |
| 15:48:59 | dansmith | oh, okay | |
| 15:49:01 | kashyap | Now the challenge is find the elusive local reproducer :-( | |
| 15:49:27 | kashyap | Interesting, this was discovered by a power-management related patch | |
| 15:50:04 | dansmith | I doubt it's related, and I also doubt we're going to find a local reproducer | |
| 15:52:09 | gibi | kashyap: power management is disable by default in our upstream CI | |
| 15:52:19 | kashyap | Hm, I see. | |
| 15:52:31 | gibi | so the patch itself is not related | |
| 15:53:50 | kashyap | dansmith: Hm, if we can't figure out a way get a local reproducer, it throws a wrench in our communication with kernel maintainers (whether it be distro or upstream). I'm sure you know this | |
| 15:54:09 | kashyap | I'm wondering how we can unjam this "deadlock" situation. | |
| 15:54:38 | dansmith | there's still information in the stack traces to provide hints on where to go from here | |
| 15:55:19 | bauzas | nova meeting in 5 mins | |
| 15:55:23 | bauzas | *here | |
| 15:55:29 | dansmith | and also, kernel developers are (IME) used to working on issues they can't reproduce because they're related to hardware and/or deadlocks where we can't get forensics out | |
| 15:56:28 | dansmith | a kernel developer might also have a better idea about how to force a repro from the details of what was happening when it faulted | |
| 15:57:43 | kashyap | dansmith: Yeah; that's a fair point; at least _some_ of the traces should lead us somewhere | |
| 15:59:14 | kashyap | And to your previous point, from a recent experience one kernel trace, I did see at least one kernel maintainer immediately say "it's a known issue due to a hardware bug" | |
| 15:59:20 | dansmith | it's also in very early boot of a kernel and userspace they have good access to | |
| 16:00:02 | bauzas | #startmeeting nova | |
| 16:00:02 | opendevmeet | Meeting started Tue Jan 16 16:00:02 2024 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 16:00:02 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 16:00:02 | opendevmeet | The meeting name has been set to 'nova' | |
| 16:00:23 | elodilles | o/ | |
| 16:00:31 | grandchild | o/ | |
| 16:00:37 | bauzas | heya | |
| 16:00:41 | dansmith | o/ (kinda) | |
| 16:00:44 | bauzas | #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | |
| 16:00:52 | bauzas | let's try to have a short meeting | |
| 16:01:02 | bauzas | some folks have another meeting in 15 mins | |
| 16:01:07 | bauzas | #topic Bugs (stuck/critical) | |
| 16:01:11 | bauzas | #info No Critical bug | |
| 16:01:15 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 46 new untriaged bugs (+3 since the last meeting) | |
| 16:01:19 | bauzas | #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster | |
| 16:01:35 | bauzas | Uggla worked a lot on the bugs | |
| 16:01:57 | bauzas | Uggla: have you modified the status for all of the ones you looked at ? | |
| 16:02:50 | fwiesel | o/ | |
| 16:03:02 | bauzas | anyway, moving on | |
| 16:03:16 | bauzas | elodilles: are you okay if you could look at the bugs next week ? | |
| 16:03:18 | elodilles | sure o/ | |
| 16:04:04 | gibi | o/ | |
| 16:04:35 | bauzas | cool | |
| 16:04:39 | bauzas | #info bug baton is elodilles | |
| 16:04:44 | bauzas | #info bug baton is elodilles | |
| 16:04:46 | bauzas | shit | |
| 16:04:50 | bauzas | #topic Gate status | |
| 16:04:54 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | |
| 16:04:58 | bauzas | #link https://etherpad.opendev.org/p/nova-ci-failures-minimal | |
| 16:05:02 | bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status | |
| 16:05:07 | bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:05:31 | bauzas | do guys want to discuss about the guest kernel issues ? | |
| 16:05:46 | bauzas | (periodic runs are all ok) | |
| 16:06:30 | bauzas | looks not, moving on then | |
| 16:06:35 | bauzas | #topic Release Planning | |
| 16:06:39 | bauzas | #link https://releases.openstack.org/caracal/schedule.html#nova | |
| 16:06:42 | bauzas | #info Caracal-3 (and feature freeze) milestone in 6 weeks | |
| 16:06:46 | bauzas | #topic Review priorities | |
| 16:07:06 | bauzas | as a reminder, please look at this etherpad if you want to review our implementations :)= | |
| 16:07:10 | bauzas | #link https://etherpad.opendev.org/p/nova-caracal-status | |
| 16:07:17 | bauzas | #topic Stable Branches | |
| 16:07:21 | bauzas | elodilles: your time | |
| 16:07:25 | elodilles | o/ | |
| 16:07:32 | elodilles | nothing to report actually | |
| 16:07:37 | elodilles | state is the same as last week | |
| 16:07:57 | elodilles | (i've pinged release cores to approve Nova's Zed release) | |
| 16:08:02 | bauzas | ++ | |
| 16:08:02 | elodilles | that's all | |
| 16:08:13 | bauzas | I think I did +1 for the zed release | |
| 16:08:21 | elodilles | yepp, you did | |
| 16:08:25 | bauzas | cool | |
| 16:08:36 | bauzas | elodilles: thanks | |
| 16:08:39 | elodilles | thanks too :) | |
| 16:08:40 | bauzas | #topic vmwareapi 3rd-party CI efforts Highlights | |
| 16:08:50 | bauzas | grandchild: fwiesel: your time :) | |
| 16:09:01 | fwiesel | #Info ETA on exemption for public access by end of week. Hopefully under DNS name: openstack-ci-logs.global.cloud.sap | |
| 16:09:12 | bauzas | <3 | |
| 16:09:14 | fwiesel | So, not much happened. Still wrapped in red tape. But at least I have a dns name. | |
| 16:09:35 | bauzas | so we'll wait :) | |
| 16:09:36 | fwiesel | That's it from my side. Any questions? | |
| 16:09:41 | bauzas | thanks a lot | |
| 16:09:44 | bauzas | nope from me | |
| 16:09:50 | fwiesel | You're welcome. | |
| 16:10:27 | bauzas | I think we said we should wait until milestone-2 for seeing whether we would remove vmwareapi, but given what you did and what you continue, of course we won't | |
| 16:10:45 | bauzas | so let's continue to see what things happen | |
| 16:11:01 | fwiesel | Thanks. Much appreciated. | |
| 16:11:08 | bauzas | thanks folks for the work, definitely nice | |
| 16:11:21 | bauzas | #topic Open discussion | |
| 16:11:32 | bauzas | nothing in the agenda, anything anyone ? | |
| 16:12:18 | bauzas | looks not, | |
| 16:12:23 | bauzas | thanks all, was a quick one | |
| 16:12:27 | bauzas | #endmeeting | |