| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-01-24 | |||
| 16:12:39 | gibi | I have no extra input to it | |
| 16:12:54 | bauzas | gibi: I've seen you updated the bug report, thanks | |
| 16:12:58 | gibi | no worries | |
| 16:13:03 | gibi | that was part of my triage round | |
| 16:13:22 | bauzas | I just triaged it to Confirmed/High fwiw | |
| 16:13:53 | gibi | ack | |
| 16:14:01 | gibi | I did not want to triage my one bug | |
| 16:14:04 | Uggla | o/ | |
| 16:14:06 | bauzas | https://zuul.openstack.org/builds?job_name=nova-tox-functional&job_name=nova-tox-functional-py310&project=openstack%2Fnova&skip=0 | |
| 16:14:13 | bauzas | this is wedgy | |
| 16:14:29 | bauzas | but at least the gate isn't hold | |
| 16:14:49 | bauzas | (assuming we have true positives in that list) | |
| 16:15:10 | gibi | filtering that to the gate pipeline is a bit better | |
| 16:15:27 | bauzas | true, it avoids the true positives | |
| 16:15:29 | gibi | but that does not show patches that are good but fail on check | |
| 16:15:36 | gibi | so meh | |
| 16:15:54 | bauzas | ideally, we should filter on the right exception :) | |
| 16:16:09 | bauzas | hence not with zuul :) | |
| 16:16:17 | bauzas | but meh, moving on | |
| 16:16:18 | gibi | yeah yeah | |
| 16:16:19 | gibi | :) | |
| 16:16:28 | bauzas | hear hear | |
| 16:16:49 | bauzas | all periodic jobs turn green this week \o/ | |
| 16:16:50 | bauzas | https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly | |
| 16:17:00 | bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status | |
| 16:17:15 | bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:17:23 | bauzas | and as a reminder | |
| 16:17:28 | bauzas | #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures | |
| 16:17:49 | bauzas | I haven't looked at the percentage number of blind rechecks since last year | |
| 16:18:06 | bauzas | but hopefully, should be super small given I say it literally everyweek, eh ? | |
| 16:18:26 | gibi | I did 0 blind one an a ton of proper one :) | |
| 16:18:39 | bauzas | :) | |
| 16:18:43 | gibi | so at least the statistic will be nice :) | |
| 16:18:49 | sean-k-mooney | maybe | |
| 16:18:58 | sean-k-mooney | you put the messasge on the next line a few times | |
| 16:19:05 | sean-k-mooney | not sure if the script takes that into account | |
| 16:19:16 | sean-k-mooney | you did provide a reason in all the ones i saw | |
| 16:19:33 | bauzas | moving on | |
| 16:19:39 | bauzas | #topic Release Planning | |
| 16:19:47 | gibi | sean-k-mooney: good point, the issue is we have multiple failed jon in a single run :) | |
| 16:19:50 | bauzas | #link https://releases.openstack.org/antelope/schedule.html | |
| 16:19:58 | bauzas | #info Antelope-3 is in 3 weeks | |
| 16:20:03 | bauzas | #link https://blueprints.launchpad.net/nova/antelope All accepted blueprints for 2023.1 | |
| 16:20:14 | bauzas | use this loudly ^ | |
| 16:20:47 | bauzas | as a reminder, not all blueprints have specs, so this is the single source of truth for the featurefreeze | |
| 16:21:03 | bauzas | and I have a question | |
| 16:21:29 | bauzas | should I somehow put something explicit against blueprints that have API impact (ie. a microversion support) ? | |
| 16:21:44 | bauzas | in order to ease people's thoughts on what to review | |
| 16:22:06 | bauzas | my proposal would be to use the Priority flag which is honestly not in use today | |
| 16:22:19 | bauzas | I can't add tags on a blueprint | |
| 16:22:21 | sean-k-mooney | i think we have 3 with api changes | |
| 16:22:31 | sean-k-mooney | im not sure we should nessisarly priortiese them by default | |
| 16:22:39 | sean-k-mooney | but we could | |
| 16:22:56 | sean-k-mooney | too basd we cant add a generic tags filed in that view | |
| 16:22:56 | bauzas | technically the priority flag would just be a 'flag' for saying this is a api change | |
| 16:23:01 | sean-k-mooney | that is what i would prefer honestly | |
| 16:23:48 | bauzas | I can modify the blueprint name | |
| 16:23:51 | sean-k-mooney | i would perhaps just not track this in launchpad | |
| 16:23:59 | bauzas | by adding some [api] prefix | |
| 16:24:05 | bauzas | if that helps | |
| 16:24:11 | sean-k-mooney | that will break the specs | |
| 16:24:19 | sean-k-mooney | what is show there is the name that is used in the url | |
| 16:24:21 | bauzas | I don't think so | |
| 16:24:22 | sean-k-mooney | not the title | |
| 16:24:41 | sean-k-mooney | we have a tox target | |
| 16:24:48 | bauzas | the link is made on the link, not on the title | |
| 16:24:52 | sean-k-mooney | to move implemtned blueprints in teh specs repot | |
| 16:25:04 | bauzas | I know, I was referring to this script | |
| 16:25:13 | sean-k-mooney | the first one in the list is https://blueprints.launchpad.net/nova/+spec/ephemeral-storage-encryption | |
| 16:25:27 | sean-k-mooney | what we see for bluepint is the bit acter spec/ | |
| 16:25:27 | bauzas | and iirc (because I used it), we map blueprints with specs using the bp link, not the bp title | |
| 16:25:42 | bauzas | we lookup the bp link in the spec file | |
| 16:25:44 | sean-k-mooney | no its based on the name of the file in the specs repo | |
| 16:25:45 | bauzas | and then we pull it | |
| 16:25:58 | sean-k-mooney | we are not parsing it out if i recall | |
| 16:26:04 | bauzas | anyway, let's not discuss that much | |
| 16:26:06 | sean-k-mooney | anyway i woudl prefer not to add [api] to it | |
| 16:26:25 | bauzas | I can do like every cycle and write an etherpad | |
| 16:26:28 | sean-k-mooney | lets just put them in an etherpad | |
| 16:26:36 | sean-k-mooney | yep | |
| 16:26:36 | bauzas | and I guess this is what I'll end up with | |
| 16:26:52 | bauzas | ok | |
| 16:27:08 | bauzas | #action bauzas to create an etherpad for tracking blueprints and their progress | |
| 16:27:15 | bauzas | there we go | |
| 16:27:49 | bauzas | #info As a reminder, Feature Freeze is in 3 weeks, be sure your patches are up to review sooner than later | |
| 16:28:11 | bauzas | moving on | |
| 16:28:18 | bauzas | #topic Review priorities | |
| 16:28:25 | 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:28:30 | bauzas | #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review | |
| 16:29:36 | bauzas | which is interesting in order to make sure we don't overlap cores's bandwidth by having the vast majority of cores looking at the same feature patches while we're so close to the feature delivery deadline | |
| 16:29:40 | bauzas | this is said. | |
| 16:30:04 | bauzas | #topic Stable Branches | |
| 16:30:14 | bauzas | elodilles: happy to pass the mic to you | |
| 16:30:22 | elodilles | #info stable branches seem to be unblocked / OK back till wallaby | |
| 16:30:30 | elodilles | #info ussuri and train might be broken ('Could not build wheels for bcrypt, cryptography' errors) | |
| 16:30:43 | elodilles | at least i saw some failures like that ^^^ | |
| 16:30:51 | zigo | Can we talk a little bit about CVE-2022-47951 / OSSA-2023-002 ? That's related: I'm trying to backport the patches up to Rocky... | |
| 16:31:37 | elodilles | rocky is End of Life already from nova perspective | |
| 16:31:44 | bauzas | zigo: if you don't mind, let's discuss this properly in the open discussion | |
| 16:31:48 | zigo | Ok. | |