14:00:07 <hberaud> #startmeeting releaseteam
14:00:07 <opendevmeet> Meeting started Fri Nov  4 14:00:07 2022 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:07 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:07 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:12 <hberaud> Ping list: hberaud armstrong elodilles
14:00:13 <elodilles> o/
14:00:18 <hberaud> #link https://etherpad.opendev.org/p/antelope-relmgt-tracking
14:00:24 <hberaud> #chair hberaud
14:00:24 <opendevmeet> Current chairs: hberaud
14:00:33 <hberaud> We're way down on line 61 now. Will just wait a couple minutes for folks.
14:03:02 <hberaud> Ok let's go
14:03:08 <hberaud> #topic Tasks
14:03:12 <hberaud> Process Extended Maintenance transitioning patches for stable/wallaby
14:03:45 <hberaud> So AFAIK only a couple of patch remains unmerged, some are without feedback from teams, others are -1
14:03:53 <elodilles> yepp
14:03:56 <elodilles> https://review.opendev.org/q/topic:wallaby-em+is:open
14:04:16 <hberaud> I think we can close those without response
14:04:30 <elodilles> hberaud: i agree
14:05:01 <elodilles> if we haven't got answers yet, then probably won't get later on
14:05:14 <hberaud> yes
14:05:18 <elodilles> so we can proceed with them
14:05:32 <hberaud> also as you said few minutes ago we should discuss about https://review.opendev.org/c/openstack/releases/+/862298
14:05:47 <elodilles> yepp
14:06:16 <elodilles> because of this: https://review.opendev.org/c/openstack/releases/+/863644
14:06:18 <hberaud> lemme check the os-vifpatch
14:06:53 <elodilles> in short, we got a release request for os-vif, with 'no codechange'
14:07:00 <hberaud> nothing relevant is released with the os-vif patch, but why not...
14:07:08 <hberaud> yes
14:07:18 <elodilles> so that tarball will contain the tox.ini with the correct upper-constraints.txt link
14:07:41 <elodilles> i'd rather not release this, as I usually try to avoid
14:07:48 <hberaud> who is the nova PTL this cycle?
14:07:57 <elodilles> bauzas
14:08:17 <hberaud> bauzas: any opinion? ^
14:08:17 <elodilles> Sean is release liaison
14:08:23 <hberaud> ok
14:09:04 <hberaud> I haven't a strong opinion...
14:09:08 <hberaud> both LGTM
14:10:22 <elodilles> well, from my side i wanted to follow the way we handle these release requests, but i can accept if the decision is to release
14:10:43 <hberaud> if Sean is the release liaison then I think we can merge it and then rebase the wallaby em patch once merged
14:11:22 <elodilles> ack
14:11:42 <hberaud> the tox.ini update helped me to solve downstream issues months ago so I won't block it
14:12:06 <elodilles> hberaud: i see :) so that's definitely good for some folk :)
14:12:11 <hberaud> even if no significant changes are merged
14:12:17 <hberaud> ok
14:12:19 <hberaud> sol
14:12:21 <hberaud> d
14:12:23 <hberaud> sold
14:12:42 <elodilles> my concern is only those who see the new release but are confused with no code changes o:)
14:12:52 <hberaud> yeah
14:13:06 <hberaud> but this is a bugfix release so...
14:13:22 <elodilles> yes, i can accept :)
14:13:33 <hberaud> I left a +2
14:13:43 <hberaud> on https://review.opendev.org/c/openstack/releases/+/863644
14:14:16 <elodilles> will do the same after the meeting
14:14:23 <hberaud> ok
14:14:55 <elodilles> i'll update the nova wallaby-em patch as well after it got merged
14:15:04 <hberaud> thans
14:15:06 <hberaud> k
14:15:14 <hberaud> lemme check those with 61
14:15:16 <hberaud> -1
14:17:12 <hberaud> the tripleo topic seems a bit complex https://review.opendev.org/c/openstack/releases/+/862341
14:18:01 <elodilles> i checked OpenStackAnsible and they want to be the last to transition, to be able to consume latest releases from other deliverables
14:18:25 <hberaud> make sense
14:18:29 <elodilles> hmmm, tripleo, i haven't checked it yet, i thought it is the same
14:18:42 <elodilles> apparently not...
14:19:06 <hberaud> apparently they disagree to move tripleo to em
14:19:32 <elodilles> hmmm, i remember we had this talk before
14:19:59 <elodilles> and as i remember we expressed that this is 'mandatory'
14:20:38 <elodilles> as this is the point when release managers won't have any tasks for an old stable branch afterwards
14:21:24 <elodilles> but downstream releases are possible
14:21:30 <hberaud> ramishra: o/ the deadline is over for the Extended Maintenance transition and tripleo is one of the latest team that remains not transitioned
14:21:36 <elodilles> especially as tripleo is RH specific
14:21:46 <hberaud> extended maintenance allow you to merge patches
14:21:55 * Guest53 sneaks in late
14:22:10 <elodilles> welcome Guest53 o/ :)
14:22:26 <hberaud> that only means that we won't make upstream release anymore
14:22:40 <hberaud> Guest53: o/
14:23:42 <hberaud> ramishra: we will be forced to merge this patch.
14:23:59 <elodilles> so, EOL'ing is mostly up to the teams, but Extended Maintenance transition is a common process with a planned date
14:24:27 <elodilles> for every projects
14:24:34 <hberaud> and it won't really impact you
14:25:13 <elodilles> yes, as i understand it won't impact tripleo
14:25:34 <hberaud> elodilles: that could be worth to copy our current discussion over the patch and to leave our votes
14:26:43 <elodilles> ++
14:27:08 <elodilles> i can do that after the meeting if that's OK
14:27:16 <hberaud> WFM
14:27:33 <hberaud> and so we only need to rebase the heat patch
14:28:27 <elodilles> on the other hand the tripleo patch needs an update (too) as it has some issue, i'll try to figure out (validator fails)
14:29:13 <opendevreview> Hervé Beraud proposed openstack/releases master: [heat] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/862320
14:29:15 <hberaud> ok
14:29:23 <elodilles> thanks!
14:29:33 <hberaud> The heat patch is now up-to-date ^
14:30:09 <elodilles> let's wait for the jobs to finish and we'll see
14:30:15 <hberaud> ok
14:30:54 <hberaud> I asked news to tkajinam about the puppet patch
14:31:31 <elodilles> that is actually a bit problematic
14:31:50 <elodilles> as they have a proposed release patch which is failing: https://review.opendev.org/c/openstack/releases/+/863198
14:32:08 <hberaud> ah i see, I missed this one
14:32:26 <elodilles> due to some missing fix to 'disable auto discovery' for pypi
14:32:34 <elodilles> * for pip
14:32:58 <hberaud> the fixes are missing on the puppet side?
14:33:17 <elodilles> their setup.py needs to contain the fix
14:33:21 <hberaud> ok
14:33:49 <hberaud> that means more 28 patchesare needed to fix that
14:34:00 <elodilles> so it needs to be fixed/backported then the (release) jobs should pass
14:34:10 <hberaud> ouch
14:34:14 <elodilles> hberaud: around that :S
14:34:40 <elodilles> i'd rather merge the transition patch
14:34:51 <elodilles> but needs some reply from the team
14:34:53 <hberaud> well I think we need to add a line dedicted to EM for next week
14:35:05 <hberaud> (meeting)
14:35:44 <elodilles> (EM transition deadline is not as strick as the releases at the end of development cycles, but we should try to stick to the planned date as close as possible)
14:35:54 <hberaud> agree
14:35:56 <elodilles> hberaud: ack
14:36:19 <hberaud> but I don't think we will finish that early next weel
14:36:21 <hberaud> week
14:36:47 <hberaud> so I think we can skip the next task
14:37:06 <elodilles> not for Puppet Openstack if they stick to do another release :S
14:37:16 <hberaud> I copied line 67 and 68 to our next week meeting agenda
14:37:17 <elodilles> hberaud: ++
14:37:28 <elodilles> thanks
14:37:48 <hberaud> ok move on
14:37:52 <hberaud> #topic Assign next week tasks
14:38:42 <elodilles> we said that the count down mail can be sent by the person who chair the meeting
14:39:00 <hberaud> I won't by there next friday, so I won't send the email
14:39:13 <hberaud> so we need to decide who will be the next chair
14:39:17 <elodilles> since ttx is not here, i add my name then :)
14:39:23 <hberaud> ok
14:39:37 <hberaud> I took the trailing project task
14:39:59 <elodilles> thanks o/
14:40:00 <hberaud> and the 2 tasks related to EM are for all
14:40:10 <elodilles> ++
14:40:33 <hberaud> Well I think we are good
14:40:45 <hberaud> #topic Release job failures
14:40:57 <hberaud> I seen 2 release job failures today
14:41:13 <hberaud> One for nova https://zuul.opendev.org/t/openstack/buildset/0eb9fb7a92604fbbb4b7835b5b051c69
14:41:28 <hberaud> and the other for heat https://zuul.opendev.org/t/openstack/buildset/aab7d855ddf54698b6f08a21189952b7
14:41:39 <hberaud> both are related to wallaby
14:42:01 <hberaud> (their last releases before EM)
14:42:02 <elodilles> oh, the same "No package matching 'python-dev' is available"
14:42:41 <elodilles> so if this is wallaby, then we won't see these problems in the future :)
14:42:43 <hberaud> To avoid the bystanders effect I prefer to check them during the meeting
14:42:46 <elodilles> unless...
14:42:57 <hberaud> lol
14:43:01 <elodilles> the python-dev is still there on some newer branches...
14:43:08 <hberaud> put them under the carpet
14:43:23 <hberaud> I don't now
14:43:34 <hberaud> know
14:44:00 <elodilles> we had this issue some days ago for one of the deliverables (on master maybe)
14:44:28 <hberaud> did we fixed that?
14:45:34 <elodilles> it was virtualbmc release
14:46:10 <hberaud> this one https://review.opendev.org/c/openstack/releases/+/862642 ?
14:46:13 <elodilles> and the problem is that deliverables bindep is installed for the announce job
14:46:35 <elodilles> and the announce job's nodeset changed to jammy from focal
14:46:44 <hberaud> I see
14:46:48 <elodilles> where we see now missing packages
14:47:09 <elodilles> yepp, that was it
14:47:50 <Clark[m]> Did we determine why the bindep packages are needed by the announce job?
14:48:19 <elodilles> let me search a bit
14:49:17 <elodilles> https://opendev.org/openstack/releases/src/branch/master/tools/announce.sh#L176-L179
14:49:24 <elodilles> this is the part ^^^
14:49:44 <elodilles> and the comment above has some details
14:50:33 <elodilles> (this was the discussion: https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-release.2022-10-26.log.html#t2022-10-26T12:59:01 )
14:52:09 <elodilles> i thought that maybe it is enough if projects fixes their errors, but that would mean a lot of backporting as well probably
14:52:48 <hberaud> yeah
14:53:01 <elodilles> which is not even correct, as pre-jammy releases can still hold the python-dev (and other) package that is still there but not in jammy
14:53:37 <hberaud> how to fix that?
14:53:38 <elodilles> so the easiest workaround for now is to pin the announce job to focal
14:53:54 <hberaud> ok
14:54:04 <hberaud> on project-config?
14:54:27 <elodilles> but that could break similarly in the future, if there are packages that are there in jammy but not exist in focal...
14:54:41 <hberaud> yeah probably
14:54:43 <elodilles> so probably focal + jammy for master branch
14:54:48 <elodilles> or something like this
14:54:52 <hberaud> LGTM
14:55:27 <hberaud> let's add that as a task for next week
14:55:28 <elodilles> i'll try to figure out what works
14:55:34 <elodilles> hberaud: ++
14:56:51 <hberaud> is it ok for you if I assign this task to you?
14:56:55 <hberaud> elodilles: ^
14:56:55 <elodilles> hberaud: i'd say: for 'older than antelope' series
14:57:18 <elodilles> no, as I've added my name already :)
14:57:26 <hberaud> thanks elodilles
14:57:43 <hberaud> So I think we can move on
14:57:50 <elodilles> ++
14:57:51 <Clark[m]> You can specify release specific dependencies in your bindep file. And python2-dev is available on jammy. I think the underlying problem here is that python-dev wasnt dropped when python2 was dropped
14:57:52 <hberaud> #topic Open Discussion
14:58:54 <elodilles> Clark[m]: oh, i see, then that's another option then! cool \o/
14:59:03 <hberaud> Clark[m]: ++
14:59:07 <hberaud> Any thing else?
14:59:40 <hberaud> s/ //
15:00:07 <elodilles> i'll try to do the focal-or-jammy 'pinning' anyway, as I'm not sure projects would fix all their bindeps on all their branches :S
15:00:17 <hberaud> Thanks elodilles
15:00:45 <hberaud> Thanks everyone for joining the meeting
15:00:53 <elodilles> and for last resort there is the option to add release specific bindep :)
15:01:04 <elodilles> thanks hberaud o/
15:01:09 <hberaud> Let's wrap up
15:01:21 <elodilles> ++
15:01:30 <hberaud> #endmeeting