| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-01-31 | |||
| 16:02:21 | bauzas | bug baton can be passed over to artom if he wants | |
| 16:02:30 | artom | Sure | |
| 16:02:38 | artom | I feel like I've skipped.... many weeks | |
| 16:02:43 | artom | (unintentionally) | |
| 16:03:24 | bauzas | thanks | |
| 16:03:36 | bauzas | #info bug baton is being passed to artom | |
| 16:03:46 | bauzas | artom: again, this is just a temptative | |
| 16:03:52 | bauzas | don't feel that much obliged | |
| 16:04:04 | artom | Well don't say that | |
| 16:04:30 | bauzas | ok, so, before we move on, do people want to discuss about some , per say, CVE bugfix or everything is OK since we're on track ? | |
| 16:04:46 | bauzas | we know we need to progress with wallaby | |
| 16:05:06 | bauzas | but I wanted to know whether people wanted to discuss it by now ? | |
| 16:06:24 | bauzas | crickets ? ok, so, let's move on | |
| 16:06:43 | bauzas | #topic Gate status | |
| 16:06:47 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | |
| 16:06:52 | bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status | |
| 16:07:18 | bauzas | gate is still wedgy, but tbh, I had to focus on other priorities last week and this week :( | |
| 16:07:38 | gibi | same here, I made no progress on the functional test instability | |
| 16:07:39 | bauzas | from what I see, the gate is quite difficult but still mergeable | |
| 16:07:47 | dansmith | it's better | |
| 16:07:57 | dansmith | I've been unable to reproduce any of the problems locally, unfortunately | |
| 16:07:59 | bauzas | on the functest sage ? | |
| 16:08:02 | bauzas | saga* | |
| 16:08:07 | bauzas | dansmith: that's the problem, I tried too | |
| 16:08:26 | bauzas | dansmith: running the exact same way than the gate using the testr subunits | |
| 16:08:36 | bauzas | but got nothing | |
| 16:09:13 | bauzas | hence me having pivoted, and tbh, there were people afraid of some security bug last week that diverted my attention | |
| 16:09:32 | bauzas | but ok, if things are better, that's cool | |
| 16:10:01 | bauzas | either way, I'll try to go looking at it back when I'm done with my own prios (including some feature implementation I promised) | |
| 16:10:15 | bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:10:19 | bauzas | #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures | |
| 16:11:21 | bauzas | ok, let's move on thenb | |
| 16:11:28 | bauzas | #topic Release Planning | |
| 16:11:32 | bauzas | #link https://releases.openstack.org/antelope/schedule.html | |
| 16:11:36 | bauzas | #info Antelope-3 is in 2 weeks | |
| 16:11:43 | bauzas | /o\ | |
| 16:12:01 | bauzas | #link https://etherpad.opendev.org/p/nova-antelope-blueprint-status Blueprint status for 2023.1 | |
| 16:12:06 | bauzas | so I created a tracking etherpad | |
| 16:12:18 | bauzas | most of the blueprints are in the 'unknown' territory | |
| 16:12:37 | bauzas | I need to investigate the crime scene and see whether the owner created some changes | |
| 16:13:20 | bauzas | so, use that etherpad as you want | |
| 16:13:41 | bauzas | ideally, blueprint owners are more than welcome to amend the etherpad with their comments, including patches to review | |
| 16:14:01 | bauzas | and cores are welcome to add comments on things they want to review or already did | |
| 16:14:58 | bauzas | I tried to add a 'API Impact' bullet on the blueprints that were actually touching the API, not exclusively by a microversion | |
| 16:15:31 | bauzas | ok, if anything else, moving on ? | |
| 16:15:43 | bauzas | if not* | |
| 16:16:30 | sean-k-mooney | sure | |
| 16:16:34 | sean-k-mooney | lets proceed | |
| 16:17:43 | bauzas | #topic Review priorities | |
| 16:17:50 | 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:17:59 | bauzas | #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review | |
| 16:18:09 | bauzas | nothing to mention here | |
| 16:18:12 | bauzas | moving on | |
| 16:18:17 | bauzas | #topic Stable Branches | |
| 16:18:25 | bauzas | passing the mic to elodilles | |
| 16:18:41 | elodilles | #info stable releases from last week: nova 26.1.0 (zed); nova 25.1.0 (yoga) nova 24.2.0 (xena) -- with CVE fix | |
| 16:18:54 | elodilles | #info stable branches seem to be unblocked / OK back till xena | |
| 16:19:05 | elodilles | #info wallaby branch is blocked by tempest (thanks gmann for working on it - https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031941.html ) | |
| 16:19:16 | elodilles | #info ussuri and train gates are broken broken ('Could not build wheels for bcrypt, cryptography' errors) | |
| 16:19:36 | gmann | stable/wallaby fix is not merged yet #link https://review.opendev.org/c/openstack/devstack/+/871782 | |
| 16:19:51 | gmann | sdk job started failing which I need to make non voting to get first fix merged | |
| 16:19:51 | bauzas | gmann: thanks for having worked hardly on that | |
| 16:19:51 | elodilles | ussuri/train might work with newer pip version | |
| 16:20:03 | bauzas | gmann: what a pile of cards | |
| 16:20:22 | gmann | yeah tempest pin on stable EM is always like this :) | |
| 16:20:31 | elodilles | gmann: openstacksdk got released some hrs ago, isn't that fixing the gate? | |
| 16:20:57 | elodilles | just asking | |
| 16:21:01 | gmann | elodilles: need to check, it is failing on <=stable/xena only | |
| 16:21:07 | elodilles | ack | |
| 16:21:17 | gmann | #link https://zuul.openstack.org/builds?job_name=openstacksdk-functional-devstack&branch=stable%2Fxena&branch=stable%2Fwallaby&skip=0 | |
| 16:21:53 | elodilles | anyway, last item from me: | |
| 16:21:57 | elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | |
| 16:22:07 | elodilles | EOM | |
| 16:22:22 | bauzas | cool | |
| 16:22:34 | bauzas | well, not so cool, but moving on | |
| 16:22:42 | bauzas | #topic Open discussion | |
| 16:22:47 | bauzas | (gmann) PyPi additional maintainers audit for Nova repo | |
| 16:22:54 | bauzas | gmann: I've seen your email | |
| 16:22:58 | gmann | ok | |
| 16:23:01 | bauzas | and I looked at nova | |
| 16:23:10 | bauzas | os-vif is impacted | |
| 16:23:53 | bauzas | os-resource-classes too | |
| 16:24:04 | bauzas | os-traits | |
| 16:24:28 | bauzas | and that's it IIRC | |
| 16:24:31 | gmann | osc-placement also i think | |
| 16:25:30 | bauzas | oh, actually placement too | |
| 16:26:00 | gmann | ah yes. its 'openstack-placement' | |
| 16:26:07 | bauzas | gmann: can you summarize the issue and what's requested for each of the projects ? | |
| 16:26:13 | bauzas | not for me, but for others | |
| 16:26:18 | gmann | sure | |
| 16:27:04 | gmann | TC discussed about those additional maintainers in PyPi which can get released without OpenStack knowing about it or more additional maintainers can be added | |
| 16:27:15 | gmann | which is nothing but security issue | |
| 16:28:14 | gmann | TC decided to clean that but wanted projects to audit their additional maintained first to check if they can be removed (if they are inactive or agreed to) or the package maintenance can be handover to them (then retire it from openstack) | |
| 16:28:56 | gmann | xstatic-font-awesome repo from horizon is one example of handing over maintenance to additional external maintainers and use it in horizon as one of the user | |
| 16:29:59 | bauzas | gmann: so I amended the tracking etherpad https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L141 | |
| 16:30:02 | gmann | but mostly packages are openstack initiated one and who setup the PyPi initially are in additional maintainers list which should be easy to clean up | |
| 16:30:19 | bauzas | I'm personnally OK with removing all marked people on those | |
| 16:30:36 | bauzas | they are no longer active contributors on the projects | |
| 16:30:48 | bauzas | do people disagree with this ? | |
| 16:30:58 | bauzas | pasting it | |