13:59:47 #startmeeting glance 13:59:47 Meeting started Thu Feb 2 13:59:47 2023 UTC and is due to finish in 60 minutes. The chair is pdeore. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:59:47 The meeting name has been set to 'glance' 13:59:47 #topic roll call 13:59:47 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 13:59:52 o/ 14:00:07 o/ 14:00:30 lets wait few minutes for others to join 14:00:59 o/ 14:00:59 o/ 14:01:12 o/ 14:01:24 I think everyone is here, lets start :) 14:01:31 #topic release/periodic jobs updates 14:01:38 Milestone 3 is in 2 weeks 14:01:47 So it's review party time next week 14:02:00 and as usual, next week we will have video meeting instead of irc meeting on thursday at same time 14:02:26 I hope everyone is ok with the review party plan next week :) 14:02:43 when we decided to have video meeting? 14:03:09 it's a review party 14:03:12 aah 14:03:15 when meaning ? time ? 14:03:17 :D 14:03:25 the only way to avoid the video meeting is to close *all* open patches 14:03:28 may be I will be out next week :/ 14:03:35 haha 14:03:38 ohh 14:03:46 o/ 14:03:59 abhishekk: PTO request denied 14:04:07 But I will try to join atleast for 30 mins 14:04:13 croelandt, ack :D 14:04:49 croelandt: i will endeavor to participate at my usual level at the review parties 14:05:09 rosmaita++ 14:06:20 ok, let's move ahead 14:06:32 Periodic job all green except TIME_OUT for fips jobs 14:06:47 #topic Catching up with reviews 14:07:12 Update Migration Constant #link https://review.opendev.org/c/openstack/glance/+/861752/ 14:07:26 does anyone know what's the deal with the FIPS jobs? i thought they were fixed 14:08:02 So is this our final approach for the migration constant? 14:08:04 i don't recollect when they were working 14:08:13 croelandt, there is no other way 14:08:28 unless we revisit entire glance migration stuff 14:08:29 me neither, but i thought they were going to run them on ubuntu and then everything would work 14:08:56 yeah, but we didn't got any update about it later 14:09:09 ok, thanks, sorry for interrupting 14:09:12 abhishekk: ok will review the patch after the meeting then 14:09:40 pdeore, could you please try to reach out to concern person about fips? 14:09:42 I will try to get the update after the meeting 14:09:48 croelandt, thanks 14:09:49 abhishekk, yes 14:09:52 cool 14:10:30 also we still have some backports which needs to be merged 14:10:46 those are failing with grenade/docs/infra related issue 14:10:55 wallaby/ussuri and train 14:11:30 abhishekk: so I thikn the fixes by gmann are not backported all the way to train 14:11:33 i think wallaby gate may be cleard up? 14:11:34 should we backport these as well? 14:11:37 My vote goes to EOL those branches as their gate seems to need way too much maintenance 14:11:49 they are already -em, can we EOL them even more? :) 14:12:17 yes, but i think we need to keep train open 14:12:23 croelandt: yes, EOL would be tagging the current state of the branch and then removing it killin all the jobs etc. 14:12:47 croelandt, I think there are still some failures in wallaby 14:13:13 gmann, has pointed those out on ML (docs job is failing on wallaby) and grenade job is still failing on ussuri 14:13:48 i must have slipped one past before the docs job broke 14:13:59 and for train neutron-grenade job is failing :. 14:14:04 abhishekk: yeah but he's not patching stable/train 14:14:14 so the failures there are likely not going away, are they? 14:14:19 right 14:14:28 well, there is no obligation to run grenade in EM branches 14:14:55 so can we drop that 14:14:59 and actually, no obligation to have the gate working at all, unless the project team wants to merge stuff there 14:15:36 ok 14:15:55 from the release docs: "Without regular comprehensive maintenance, it is quite possible that someone proposing a backport to an EM branch will find that tests 14:16:02 nce, it is quite possible that someone proposing a backport to an EM branch will find that tests 14:16:09 bad paste 14:16:14 let me start over 14:16:31 "Without regular comprehensive maintenance, it is quite possible that someone proposing a backport to an EM branch will find that tests have broken since the last 14:16:50 successful merge. This means that tests (or test configuration) might need to be fixed, reduced, or reconfigured before the backport itself can be evaluated and merged. 14:17:02 The onus for that falls on the backporter or the group of people looking after a specific release." 14:17:11 https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance 14:17:30 so we can keep basic jobs like unit/functional and docs on em branches ? 14:17:46 right 14:18:04 cool, that will sort out train issue 14:18:19 we will wait for wallaby to be fixed properly 14:18:22 so jokke_ has some complaints about removing jobs :) 14:18:29 from the TC meeting yesterday, a primary reason to keep EM branches non-deleted is just so the community can post patches and have a public place to review them 14:18:54 abhishekk: oh for wallaby it's the docs that fail now 14:19:02 correct 14:19:07 always a new failure 14:19:13 :P 14:19:49 I can push a patch to train to remove unnecessary jobs 14:20:22 abhishekk, Thanks ! 14:20:26 i would keep at least one tempest job, though 14:20:33 ack 14:20:47 my ocncern is, why do we bother to keep the branches, if we don't test them 14:20:54 concern 14:21:10 well, we do test them 14:21:23 i think grenade doesn't make sense, but tempest does 14:21:28 (if it wouldn't break so much) 14:21:43 Ok so why don't we remove those excessive jobs from all branches then? ;) 14:21:50 :P 14:21:56 but the main reason is that you can't post reviews of patches to a deleted branch in gerrit 14:21:58 This is probably something the whole OpenStack community should discuss with packagers 14:22:11 ++ 14:22:11 Who uses these branches? How useful are they? 14:22:22 Get people from Debian, Fedora, Ubuntu etc. 14:22:27 see how they use them 14:22:53 well, zigo was on the ML, just repackaged rocky for debian to include a CVE fix 14:23:33 and from comments on that bug, looks like a lot of interest in rocky currently 14:23:58 damn, Debian stable truly is in the past 14:23:59 "that bug" == https://bugs.launchpad.net/cinder/+bug/1996188 14:24:00 no further arguments 14:24:46 I'm not saying that the -em branches are not useful for anyone, but the deal was that those folks takes the responsibility of keeping the tests etc running and if that does not happen it's better to just EOL the branch and let them backport in downstream 14:25:42 They were supposed to be 0 effort for the project teams, which clearly is not the case 14:26:08 i don't think *anything* is supposed to be 0 effort for project teams! 14:26:11 yeah so maybe we could discuss having a reduced set of tests 14:26:21 the CI is always failing for some reason 14:26:28 and usually that reason is not an issue with the actual code 14:26:36 but rather infrastructure-related issues 14:27:41 +1 14:27:58 reduced tests is fine, though eventually you get to the point where like jokke_ says, why bother 14:28:13 so i think reduce tests, and when we get to that point, have the EOL discussion 14:28:34 rosmaita: how would we start that conversation? I think it needs to be an Openstack-wide policy 14:28:41 it already is 14:28:42 I think its better to take this topic in upcoming PTG either in TC or glance schedule 14:29:18 read the EM policy ... it is clear that it's up to the project team when to go EOL and what the team's obligations are while a branch is in EM 14:29:29 https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance 14:29:44 abhishekk++ 14:30:08 rosmaita, ack 14:30:09 cinder can EOL all the way up to wallaby if it wants to 14:30:19 ok 14:30:32 though i think some peoples' employers would have issue with that 14:30:53 (if you know what i mean) 14:30:58 :D 14:32:06 Let's move ahead, keep watch on ussuri and wallaby fixes and then get the patches merged 14:32:32 thanks :) moving ahead 14:32:39 Train we can decide what to drop and what to keep on the review itself 14:32:39 #topic Glance cinder store changes 14:33:43 so glance store release is in a week (10th Feb last date), so kindly please have a look at below patches on priority 14:34:25 Refactor: https://review.opendev.org/c/openstack/glance_store/+/843103, this one is required for extending attched volumes support patch 14:34:40 Extend attached volumes: #link https://review.opendev.org/c/openstack/glance_store/+/868742 14:34:57 Glance test fix: #link https://review.opendev.org/c/openstack/glance/+/869021 14:36:07 ack 14:36:16 That's it from me for today, let's move to Open discussion 14:36:26 #topic Open Discussions 14:36:46 I don't have anything 14:37:02 just fyi, PTL nomination is open 14:37:16 yeah :) 14:37:31 till 15th feb 14:37:50 pdeore! pdeore! pdeore! 14:38:30 no choice :P 14:39:28 anyone has anythhing else to discuss or we are good to wrap up early? 14:39:59 thank you all! 14:40:12 I'm good, thanks! 14:40:14 thanks! 14:40:22 cool, thanks everyone !! 14:40:25 #endmeeting