| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-03-07 | |||
| 16:07:15 | sean-k-mooney | we can adress it and backprot after the offical relase is done | |
| 16:07:15 | bauzas | sean-k-mooney: I agree, disabling the whole feature seems to me easier and less errorprone | |
| 16:07:43 | bauzas | sean-k-mooney: putting the bug importance as High | |
| 16:07:56 | bauzas | it's basically blocking a nova boot on windows images if AMD-based | |
| 16:08:03 | sean-k-mooney | ack | |
| 16:08:04 | bauzas | that's quite a large impact | |
| 16:08:08 | sean-k-mooney | if you set the image property | |
| 16:08:25 | sean-k-mooney | but i was debating between medium and high so im ok with high | |
| 16:08:32 | bauzas | true, but how many production-level clouds are not setting the property ? :) | |
| 16:08:47 | bauzas | note : it was an open question :d | |
| 16:09:13 | sean-k-mooney | hehe i dont know but i think in either case we shoudl fix and backport it sonner rather then later | |
| 16:09:45 | sean-k-mooney | i might try and write a ptch for it but if other want to go ahead | |
| 16:10:01 | sean-k-mooney | i think we can move on for today | |
| 16:10:06 | bauzas | cool | |
| 16:10:10 | bauzas | and thanks | |
| 16:10:32 | bauzas | for the MIG bug, let's discuss this off the meeting, but upstream support on nvidia is very limited | |
| 16:11:01 | bauzas | unless the bug is reproducable on another hardware, I would tend to mark it Invalid either way | |
| 16:11:09 | sean-k-mooney | ya it borderlien a feature but i think it need some discussion outside the meeting | |
| 16:11:22 | bauzas | cool, I don't disagree | |
| 16:11:25 | bauzas | moving on | |
| 16:11:33 | bauzas | #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster | |
| 16:11:46 | bauzas | elodilles: well, this is your turn this week | |
| 16:11:56 | elodilles | bauzas: ack | |
| 16:11:57 | bauzas | how do you feel with all the releases patches coming up ? | |
| 16:12:05 | bauzas | + the reno ugly bug | |
| 16:12:22 | elodilles | bauzas: let's not postpone it now, i'll take the baton | |
| 16:12:25 | bauzas | (well, technically not a bug, but rather an unexpected lack of support) | |
| 16:12:38 | bauzas | cool cool | |
| 16:12:40 | bauzas | and thanks | |
| 16:12:49 | bauzas | elodilles: don't feel pressured | |
| 16:12:54 | bauzas | #info bug baton is being passed to elodilles | |
| 16:12:59 | bauzas | next topic | |
| 16:13:04 | bauzas | #topic Gate status | |
| 16:13:10 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | |
| 16:13:15 | bauzas | #link https://etherpad.opendev.org/p/nova-ci-failures | |
| 16:13:29 | bauzas | so, we have less oom issues, which is good | |
| 16:13:41 | bauzas | mysql is less a noisy neighbor | |
| 16:13:55 | bauzas | but we only touched a few jobs | |
| 16:15:12 | bauzas | if you see other jobs that oom-kill mysql but nova-next and nova-ceph-multistore, let us know | |
| 16:15:57 | bauzas | apart from that, I've seen other failures, but I hadn't a lot of time of digging | |
| 16:16:13 | bauzas | unless anyone wants to address a specific failure, we may need to move on | |
| 16:16:37 | bauzas | looks so | |
| 16:16:50 | bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status | |
| 16:17:17 | bauzas | so we had periodic tempest-integrated-placement on stable/yoga that timed out | |
| 16:18:14 | bauzas | I checked the log and it was just a slow job run | |
| 16:18:26 | bauzas | so hopefully things will order back at the next run | |
| 16:18:38 | bauzas | (and zed and master runs are OK) | |
| 16:18:56 | bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:19:00 | bauzas | #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures | |
| 16:19:06 | bauzas | #topic Release Planning | |
| 16:19:13 | bauzas | #link https://releases.openstack.org/antelope/schedule.html | |
| 16:19:19 | bauzas | #info Antelope-rc1 was this Monday | |
| 16:19:40 | bauzas | so, we're now in a duplicity period, where we are both on Bobcat and Antelope timeframes :) | |
| 16:20:01 | bauzas | if you've seen Tenet, you got it | |
| 16:20:08 | bauzas | (the movie) | |
| 16:20:19 | bauzas | now, we have a 2023.1 branch | |
| 16:20:43 | elodilles | ~o~ | |
| 16:20:53 | bauzas | #info as a reminder, no backports are possible on the 2023.1 branch *unless* they are regression bugfixes | |
| 16:21:27 | bauzas | and accordingly all stable branches go on a quiet period since they're now dependent on the antelope branch | |
| 16:22:23 | bauzas | #link https://etherpad.opendev.org/p/nova-antelope-rc-potential | |
| 16:22:46 | bauzas | fwiw, our release notes are currently broken to be shown | |
| 16:22:51 | bauzas | for Antelope | |
| 16:23:19 | sean-k-mooney | we can still merge exsting backport but noting to 2023.1 | |
| 16:23:22 | bauzas | context : https://review.opendev.org/c/openstack/nova/+/876553 | |
| 16:23:24 | sean-k-mooney | that is not for an rc | |
| 16:23:56 | bauzas | sean-k-mooney: well, if the original patch is on Antelope, sure | |
| 16:24:35 | sean-k-mooney | we have plent of open backport on exsting stable branch that coudl use review | |
| 16:24:36 | bauzas | elodilles: iiuc, we'll need to enable the new reno ordering in our releasenotes ? | |
| 16:24:49 | bauzas | once the reno patch got landed | |
| 16:24:50 | elodilles | bauzas: fyi, reno workaround has landed, but not yet released | |
| 16:24:59 | bauzas | oh, missed that | |
| 16:25:08 | elodilles | bauzas: and we don't need to do anything, but use the new reno release | |
| 16:25:10 | bauzas | sean-k-mooney: yup, don't disagree | |
| 16:25:11 | sean-k-mooney | do we need to do any changes once its released | |
| 16:25:22 | sean-k-mooney | or will the release notes get rebuilt automatically | |
| 16:25:27 | bauzas | elodilles: ah, right, so dhellmann's proposition was accepted | |
| 16:25:36 | sean-k-mooney | ok cool | |
| 16:25:43 | sean-k-mooney | if we dont need to do anything great | |
| 16:25:54 | bauzas | sean-k-mooney: yeah, so there was a patch up for opting-in to the new reno ordering | |
| 16:26:05 | sean-k-mooney | by use the new reno does that mean increase the min version in requirements | |
| 16:26:09 | bauzas | but doug said he was ok with having it by default | |
| 16:26:24 | sean-k-mooney | or just realy on upper-constratis | |
| 16:26:28 | bauzas | sean-k-mooney: reno isn't part of our requirements | |
| 16:26:36 | bauzas | (unless I'm wrong) | |
| 16:26:38 | sean-k-mooney | its in our doc requirements i think | |
| 16:26:47 | bauzas | that's a specific target, which isn't docs | |
| 16:26:54 | elodilles | actually, it is part of upper-constraints | |
| 16:26:59 | sean-k-mooney | https://github.com/openstack/nova/blob/master/doc/requirements.txt#L13 | |
| 16:27:06 | bauzas | https://github.com/openstack/nova/blob/master/tox.ini#L238 | |
| 16:27:15 | elodilles | but for master branch (bobcat) I think it will be soon possible to bump | |
| 16:27:36 | sean-k-mooney | https://github.com/openstack/nova/blob/master/tox.ini#L238-L242 | |
| 16:27:43 | sean-k-mooney | the release notes use the docs requirements file | |
| 16:27:47 | bauzas | sean-k-mooney: snap | |
| 16:28:01 | sean-k-mooney | so ya it will automatically get picked up from uc | |
| 16:28:12 | sean-k-mooney | but im wonderign if we want to block the older releases or not | |
| 16:28:19 | sean-k-mooney | we dont have too but we could | |
| 16:28:30 | bauzas | it's backwards-compatible | |
| 16:28:44 | bauzas | so I don't think we need | |
| 16:28:57 | sean-k-mooney | yep i was more thinking of a signal to packages | |
| 16:29:06 | sean-k-mooney | but im fine with not bumping the min version | |