| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-02-28 | |||
| 16:37:16 | auniyal | o/ I can ! | |
| 16:37:21 | sean-k-mooney | we are not in rush | |
| 16:37:47 | bauzas | auniyal: ack, noted. | |
| 16:37:58 | bauzas | I'll discuss this with you later | |
| 16:38:02 | auniyal | ack | |
| 16:38:26 | bauzas | thanks for the offer | |
| 16:40:01 | bauzas | moving on | |
| 16:40:15 | bauzas | #topic vPTG Planning | |
| 16:40:23 | bauzas | the usual now reminder | |
| 16:40:25 | bauzas | #link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-483971570997 Register your free ticket | |
| 16:40:30 | bauzas | and | |
| 16:40:32 | bauzas | #link https://etherpad.opendev.org/p/nova-bobcat-ptg Draft PTG etherpad | |
| 16:40:40 | bauzas | the etherpad starts to grow | |
| 16:41:00 | bauzas | I haven't yet been asked how many slots we gonna want for the vPTG | |
| 16:41:11 | bauzas | be sure I'll tell you once I'm reachend | |
| 16:41:17 | bauzas | reached* | |
| 16:41:27 | bauzas | #topic Review priorities | |
| 16:41:32 | bauzas | #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2) | |
| 16:41:36 | bauzas | #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review | |
| 16:42:43 | bauzas | #topic Stable Branches | |
| 16:42:52 | bauzas | elodilles: your time | |
| 16:42:54 | elodilles | thanks | |
| 16:43:03 | elodilles | actually, nothing special to report, | |
| 16:43:14 | elodilles | #info stable gates seem to be OK | |
| 16:43:26 | elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | |
| 16:43:44 | elodilles | use this if you see any new errors ^^^ | |
| 16:43:49 | elodilles | that's all from me | |
| 16:44:12 | bauzas | all good | |
| 16:44:26 | bauzas | no news is good news | |
| 16:44:34 | bauzas | #topic Open discussion | |
| 16:44:40 | bauzas | nothing on the agenda | |
| 16:45:06 | bauzas | I guess we can call it a wrap ? | |
| 16:45:23 | auniyal | o/ | |
| 16:45:29 | auniyal | There are some bugs that are either fixed but not closed for some reason or do not have much information so people can work on them (IMO), which makes our backlog big. | |
| 16:45:43 | auniyal | Os-vif: | |
| 16:45:43 | auniyal | https://bugs.launchpad.net/os-vif/+bug/1654117 | |
| 16:45:43 | auniyal | https://bugs.launchpad.net/os-vif/+bug/1670628 | |
| 16:45:43 | auniyal | https://bugs.launchpad.net/os-vif/+bug/1702262 | |
| 16:45:43 | auniyal | fixed here: https://review.opendev.org/c/openstack/os-vif/+/479861/ | |
| 16:45:47 | bauzas | that's a topic I added for the vPTG | |
| 16:46:02 | auniyal | okay | |
| 16:46:11 | bauzas | I'd like us to scrub our bug number by abandoning very old reports | |
| 16:46:21 | bauzas | but I'd prefer to discuss it at the PTG | |
| 16:46:38 | auniyal | ack bauzas | |
| 16:46:58 | bauzas | and yeah, some bug reports may not be automatically closed if the gerrit patch forgot to correctly write the commit msg tag | |
| 16:47:14 | bauzas | so the launchpad sync is not automatically done | |
| 16:48:13 | bauzas | auniyal: feel free to close the bug report with a comment | |
| 16:48:27 | bauzas | the status is then Fixed Released in LP | |
| 16:48:49 | bauzas | any other questions ? | |
| 16:48:55 | bauzas | I have to go errand in a sec | |
| 16:49:52 | bauzas | looks not | |
| 16:49:54 | bauzas | if so | |
| 16:49:56 | bauzas | thanks all | |
| 16:50:02 | bauzas | #endmeeting | |
| 16:50:02 | opendevmeet | Meeting ended Tue Feb 28 16:50:02 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:50:02 | opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-28-16.02.html | |
| 16:50:02 | opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-28-16.02.txt | |
| 16:50:02 | opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-28-16.02.log.html | |
| 16:50:12 | elodilles | thanks o/ | |
| 17:21:12 | stephenfin | Weird one. Anyone have any idea why this doesn't work as expected? https://paste.opendev.org/show/bpzDcEI75QIIb9QuGFb8/ | |
| 17:21:45 | stephenfin | If I run that, it prints out "Exception: Method 'baz' is not allowed" instead of "Exception: Method 'foo' is not allowed" as expected (baz instead of foo) | |
| 17:22:23 | stephenfin | It's a reproducer for bug in Keystone tests. I've fixed the tests but I can't yet grok why it was happening. | |
| 17:31:15 | gmann | dansmith: sean-k-mooney bauzas : on skip-level job. as 2023.2 is NON_SLURP so we will not run skip-level job right | |
| 17:31:37 | gmann | in 2023.3 cycle we will run it from 2023.1 to 2023.3 upgrade on jammy | |
| 17:31:41 | dansmith | gmann: I want nova to stick to testing N-2->N even in non-slurp releases | |
| 17:32:06 | dansmith | gmann: perhaps I should just clone grenade-skip-level to grenade-skip-level-continuous and update that to be z->b ? | |
| 17:32:11 | dansmith | or z->master | |
| 17:32:26 | gmann | dansmith: ohk | |
| 17:32:48 | gmann | so that will be on focal right as zed is tested on focal as testing runtime | |
| 17:33:04 | gmann | zed (focal) -> 2023.2 (focal ?) | |
| 17:33:17 | gmann | but 2023.2 on focal is not tested | |
| 17:33:24 | dansmith | I thought zed was both? | |
| 17:33:42 | dansmith | ah, I see, it wasn't.. dang | |
| 17:33:43 | gmann | 2023.1 was both, let me check | |
| 17:34:04 | dansmith | yeah, zed was just 20.04 | |
| 17:34:16 | dansmith | well, I can try it and if it doesn't work I guess we can pung | |
| 17:34:17 | gmann | https://governance.openstack.org/tc/reference/runtimes/zed.html | |
| 17:34:18 | dansmith | *punt | |
| 17:34:18 | gmann | yeah | |
| 17:34:28 | dansmith | because sean-k-mooney wants to bump the minimum libvirt version | |
| 17:34:41 | gmann | as 2023.1 starting was tested ion jammy so zed might work | |
| 17:34:46 | gmann | ohk | |
| 17:35:18 | gmann | in 2023.2 right? or bump in 2023.1 ? | |
| 17:35:54 | dansmith | sean-k-mooney: wants to bump in 2023.2, but presumably to still include what would be needed for 2023.1 | |
| 17:36:08 | dansmith | i.e. jammy | |
| 17:39:31 | gmann | but is not that will be covered in normal grenade job from 2023.1 to 2023.2 ? or we want N-2 thing also due to libvirt bump ? and so does zed on jammy just because of grenade testing but main purpose is to check zed->2023.2 libvirt bump work fine or not? | |
| 17:40:38 | dansmith | not to test the libvirt bump specifically | |
| 17:40:53 | dansmith | but rather to keep us with a working N-2->N even though we don't *have* to support it | |
| 17:41:11 | dansmith | if we end up breaking something and have to drop the job, then fine, but I would rather highlight what breaks N-2 upgrades if we can | |
| 17:41:33 | gmann | ok | |
| 17:42:27 | gmann | i think it should work as zed was the edge when we move to jammy | |
| 17:42:38 | dansmith | yeah, will see | |
| 17:43:06 | opendevreview | Dan Smith proposed openstack/nova master: Add continuous skip-level job for nova https://review.opendev.org/c/openstack/nova/+/875773 | |
| 17:43:46 | gmann | so for that I will not filter out the 2023.2 from here (we filter out NON-SLURP here) which I do while release time https://github.com/openstack/grenade/blob/master/.zuul.yaml#L392 | |
| 17:44:16 | opendevreview | Dan Smith proposed openstack/nova master: Add continuous skip-level job for nova https://review.opendev.org/c/openstack/nova/+/875773 | |
| 17:44:31 | stephenfin | Got it. It's late binding https://stackoverflow.com/q/3431676/ Sigh, TIL | |
| 17:45:02 | dansmith | gmann: oh hmm, that's just the thing that prevents it from running on stable right? | |
| 17:45:20 | gmann | yeah | |
| 17:45:42 | gmann | because it is in integrated gate template also | |
| 17:45:54 | dansmith | yeah, so that's okay for now right? we only care about master | |