Friday, 2022-11-04

*** dviroel is now known as dviroel|out00:17
*** marios is now known as marios|ruck06:17
*** amoralej|off is now known as amoralej07:05
opendevreviewMerged openstack/releases master: Final Wallaby release for horizon  https://review.opendev.org/c/openstack/releases/+/86293109:11
opendevreviewMerged openstack/releases master: Release final heat for stable/wallaby  https://review.opendev.org/c/openstack/releases/+/86245209:19
opendevreviewMerged openstack/releases master: Release glance for stable/wallaby  https://review.opendev.org/c/openstack/releases/+/84790509:25
opendevreviewMerged openstack/releases master: nova: Release Wallaby 23.2.2  https://review.opendev.org/c/openstack/releases/+/86349009:51
opendevreviewMerged openstack/releases master: Release sushy 3.7.6 for Wallaby  https://review.opendev.org/c/openstack/releases/+/86350909:51
opendevreviewVishal Manchanda proposed openstack/releases master: [horizon] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86232109:59
opendevreviewDr. Jens Harbott proposed openstack/releases master: Tag monthly kolla stable releases  https://review.opendev.org/c/openstack/releases/+/86363210:25
opendevreviewHervé Beraud proposed openstack/releases master: [glance] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86231911:19
opendevreviewHervé Beraud proposed openstack/releases master: [ironic] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86232211:21
opendevreviewHervé Beraud proposed openstack/releases master: [nova] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86229811:28
*** dviroel_ is now known as dviroel11:36
opendevreviewMerged openstack/releases master: [horizon] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86232111:55
opendevreviewMerged openstack/releases master: [Telemetry] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86230911:55
opendevreviewMerged openstack/releases master: [mistral] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86232911:55
*** amoralej is now known as amoralej|lunch12:05
*** amoralej|lunch is now known as amoralej13:06
opendevreviewsean mooney proposed openstack/releases master: preform final release of os-vif  https://review.opendev.org/c/openstack/releases/+/86364413:10
opendevreviewsean mooney proposed openstack/releases master: preform final release of os-vif  https://review.opendev.org/c/openstack/releases/+/86364413:26
elodillesreminder: meeting will start at 14:00 UTC which is in less than half an hour (DST change was last weekend for some countries, hence this is a double reminder :))13:35
elodilleshberaud: some teaser for the meeting in advance, there is an interesting release patch, I've commented on it already, but we might need some decision about it, maybe on the meeting: https://review.opendev.org/c/openstack/releases/+/86364413:37
elodilleso:)13:37
hberaudelodilles: ok13:55
hberaud#startmeeting releaseteam14:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'releaseteam'14:00
hberaudPing list: hberaud armstrong elodilles14:00
elodilleso/14:00
hberaud#link https://etherpad.opendev.org/p/antelope-relmgt-tracking14:00
hberaud#chair hberaud14:00
opendevmeetCurrent chairs: hberaud14:00
hberaudWe're way down on line 61 now. Will just wait a couple minutes for folks.14:00
hberaudOk let's go14:03
hberaud#topic Tasks14:03
hberaudProcess Extended Maintenance transitioning patches for stable/wallaby14:03
hberaudSo AFAIK only a couple of patch remains unmerged, some are without feedback from teams, others are -114:03
elodillesyepp14:03
elodilleshttps://review.opendev.org/q/topic:wallaby-em+is:open14:03
hberaudI think we can close those without response14:04
elodilleshberaud: i agree14:04
elodillesif we haven't got answers yet, then probably won't get later on14:05
hberaudyes14:05
elodillesso we can proceed with them14:05
hberaudalso as you said few minutes ago we should discuss about https://review.opendev.org/c/openstack/releases/+/86229814:05
elodillesyepp14:05
elodillesbecause of this: https://review.opendev.org/c/openstack/releases/+/86364414:06
hberaudlemme check the os-vifpatch14:06
elodillesin short, we got a release request for os-vif, with 'no codechange'14:06
hberaudnothing relevant is released with the os-vif patch, but why not...14:07
hberaudyes14:07
elodillesso that tarball will contain the tox.ini with the correct upper-constraints.txt link14:07
elodillesi'd rather not release this, as I usually try to avoid14:07
hberaudwho is the nova PTL this cycle?14:07
elodillesbauzas14:07
hberaudbauzas: any opinion? ^14:08
elodillesSean is release liaison14:08
hberaudok14:08
hberaudI haven't a strong opinion...14:09
hberaudboth LGTM14:09
elodilleswell, from my side i wanted to follow the way we handle these release requests, but i can accept if the decision is to release14:10
hberaudif Sean is the release liaison then I think we can merge it and then rebase the wallaby em patch once merged14:10
elodillesack14:11
hberaudthe tox.ini update helped me to solve downstream issues months ago so I won't block it14:11
elodilleshberaud: i see :) so that's definitely good for some folk :)14:12
hberaudeven if no significant changes are merged14:12
hberaudok14:12
hberaudsol14:12
hberaudd14:12
hberaudsold14:12
elodillesmy concern is only those who see the new release but are confused with no code changes o:)14:12
hberaudyeah14:12
hberaudbut this is a bugfix release so...14:13
elodillesyes, i can accept :)14:13
hberaudI left a +214:13
hberaudon https://review.opendev.org/c/openstack/releases/+/86364414:13
elodilleswill do the same after the meeting14:14
hberaudok14:14
elodillesi'll update the nova wallaby-em patch as well after it got merged14:14
hberaudthans14:15
hberaudk14:15
hberaudlemme check those with 6114:15
hberaud-114:15
hberaudthe tripleo topic seems a bit complex https://review.opendev.org/c/openstack/releases/+/86234114:17
elodillesi checked OpenStackAnsible and they want to be the last to transition, to be able to consume latest releases from other deliverables14:18
hberaudmake sense14:18
elodilleshmmm, tripleo, i haven't checked it yet, i thought it is the same14:18
elodillesapparently not...14:18
hberaudapparently they disagree to move tripleo to em14:19
elodilleshmmm, i remember we had this talk before14:19
elodillesand as i remember we expressed that this is 'mandatory'14:19
elodillesas this is the point when release managers won't have any tasks for an old stable branch afterwards14:20
elodillesbut downstream releases are possible14:21
hberaudramishra: o/ the deadline is over for the Extended Maintenance transition and tripleo is one of the latest team that remains not transitioned14:21
elodillesespecially as tripleo is RH specific14:21
hberaudextended maintenance allow you to merge patches14:21
* Guest53 sneaks in late14:21
elodilleswelcome Guest53 o/ :)14:22
hberaudthat only means that we won't make upstream release anymore14:22
hberaudGuest53: o/14:22
hberaudramishra: we will be forced to merge this patch.14:23
elodillesso, EOL'ing is mostly up to the teams, but Extended Maintenance transition is a common process with a planned date14:23
elodillesfor every projects14:24
hberaudand it won't really impact you14:24
elodillesyes, as i understand it won't impact tripleo14:25
hberaudelodilles: that could be worth to copy our current discussion over the patch and to leave our votes14:25
elodilles++14:26
elodillesi can do that after the meeting if that's OK14:27
hberaudWFM14:27
hberaudand so we only need to rebase the heat patch14:27
elodilleson the other hand the tripleo patch needs an update (too) as it has some issue, i'll try to figure out (validator fails)14:28
opendevreviewHervé Beraud proposed openstack/releases master: [heat] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86232014:29
hberaudok14:29
elodillesthanks!14:29
hberaudThe heat patch is now up-to-date ^14:29
elodilleslet's wait for the jobs to finish and we'll see14:30
hberaudok14:30
hberaudI asked news to tkajinam about the puppet patch14:30
elodillesthat is actually a bit problematic14:31
elodillesas they have a proposed release patch which is failing: https://review.opendev.org/c/openstack/releases/+/86319814:31
hberaudah i see, I missed this one14:32
elodillesdue to some missing fix to 'disable auto discovery' for pypi14:32
elodilles* for pip14:32
hberaudthe fixes are missing on the puppet side?14:32
elodillestheir setup.py needs to contain the fix14:33
hberaudok14:33
hberaudthat means more 28 patchesare needed to fix that14:33
elodillesso it needs to be fixed/backported then the (release) jobs should pass14:34
hberaudouch14:34
elodilleshberaud: around that :S14:34
elodillesi'd rather merge the transition patch14:34
elodillesbut needs some reply from the team14:34
hberaudwell I think we need to add a line dedicted to EM for next week14:34
hberaud(meeting)14:35
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
hberaudagree14:35
elodilleshberaud: ack14:35
hberaudbut I don't think we will finish that early next weel14:36
hberaudweek14:36
hberaudso I think we can skip the next task14:36
elodillesnot for Puppet Openstack if they stick to do another release :S14:37
hberaudI copied line 67 and 68 to our next week meeting agenda14:37
elodilleshberaud: ++14:37
elodillesthanks14:37
hberaudok move on14:37
hberaud#topic Assign next week tasks14:37
elodilleswe said that the count down mail can be sent by the person who chair the meeting14:38
hberaudI won't by there next friday, so I won't send the email14:39
hberaudso we need to decide who will be the next chair14:39
elodillessince ttx is not here, i add my name then :)14:39
hberaudok14:39
hberaudI took the trailing project task14:39
elodillesthanks o/14:39
hberaudand the 2 tasks related to EM are for all14:40
elodilles++14:40
hberaudWell I think we are good14:40
hberaud#topic Release job failures14:40
hberaudI seen 2 release job failures today14:40
hberaudOne for nova https://zuul.opendev.org/t/openstack/buildset/0eb9fb7a92604fbbb4b7835b5b051c69 14:41
hberaudand the other for heat https://zuul.opendev.org/t/openstack/buildset/aab7d855ddf54698b6f08a21189952b7 14:41
hberaudboth are related to wallaby14:41
hberaud(their last releases before EM)14:42
elodillesoh, the same "No package matching 'python-dev' is available"14:42
elodillesso if this is wallaby, then we won't see these problems in the future :)14:42
hberaudTo avoid the bystanders effect I prefer to check them during the meeting14:42
elodillesunless...14:42
hberaudlol14:42
elodillesthe python-dev is still there on some newer branches...14:43
hberaudput them under the carpet14:43
hberaudI don't now14:43
hberaudknow14:43
elodilleswe had this issue some days ago for one of the deliverables (on master maybe)14:44
hberauddid we fixed that?14:44
elodillesit was virtualbmc release14:45
hberaudthis one https://review.opendev.org/c/openstack/releases/+/862642 ?14:46
elodillesand the problem is that deliverables bindep is installed for the announce job14:46
elodillesand the announce job's nodeset changed to jammy from focal14:46
hberaudI see14:46
elodilleswhere we see now missing packages14:46
elodillesyepp, that was it14:47
Clark[m]Did we determine why the bindep packages are needed by the announce job?14:47
elodilleslet me search a bit14:48
elodilleshttps://opendev.org/openstack/releases/src/branch/master/tools/announce.sh#L176-L17914:49
elodillesthis is the part ^^^14:49
elodillesand the comment above has some details14:49
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:50
elodillesi thought that maybe it is enough if projects fixes their errors, but that would mean a lot of backporting as well probably14:52
hberaudyeah14:52
elodilleswhich is not even correct, as pre-jammy releases can still hold the python-dev (and other) package that is still there but not in jammy14:53
hberaudhow to fix that?14:53
elodillesso the easiest workaround for now is to pin the announce job to focal14:53
hberaudok14:53
hberaudon project-config?14:54
elodillesbut that could break similarly in the future, if there are packages that are there in jammy but not exist in focal...14:54
hberaudyeah probably14:54
elodillesso probably focal + jammy for master branch14:54
elodillesor something like this14:54
hberaudLGTM14:54
hberaudlet's add that as a task for next week14:55
elodillesi'll try to figure out what works14:55
elodilleshberaud: ++14:55
hberaudis it ok for you if I assign this task to you?14:56
hberaudelodilles: ^14:56
elodilleshberaud: i'd say: for 'older than antelope' series14:56
elodillesno, as I've added my name already :)14:57
hberaudthanks elodilles 14:57
hberaudSo I think we can move on14:57
elodilles++14:57
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 dropped14:57
hberaud#topic Open Discussion14:57
elodillesClark[m]: oh, i see, then that's another option then! cool \o/14:58
hberaudClark[m]: ++14:59
hberaudAny thing else?14:59
hberauds/ //14:59
elodillesi'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 :S15:00
hberaudThanks elodilles 15:00
hberaudThanks everyone for joining the meeting15:00
elodillesand for last resort there is the option to add release specific bindep :)15:00
elodillesthanks hberaud o/15:01
hberaudLet's wrap up15:01
elodilles++15:01
hberaud#endmeeting15:01
opendevmeetMeeting ended Fri Nov  4 15:01:30 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2022/releaseteam.2022-11-04-14.00.html15:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2022/releaseteam.2022-11-04-14.00.txt15:01
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2022/releaseteam.2022-11-04-14.00.log.html15:01
Clark[m]Just looking at virtualbmc its setup.cfg says it is python 3 only. Which to me means the bug is having python-dev at all. python-devel should also be removed15:03
elodillesClark[m]: yepp, that's definitely a problem and hopefully projects will fix their master branch to make their gate pass15:06
elodillesClark[m]: the problem is when they have the same on an older branch, and would need to backport it, but they won't notice the failure as the gate is running on focal or bionic15:08
elodillesClark[m]: releases can be made from zed, yoga, xena (and Wallaby is turning to EM now), these branches don't have python 2, but don't even fail because of having python-dev in bindep :-/15:10
elodillesbut yes, that would be the best if all old bindeps were removed from all of the above branches :/15:12
opendevreviewMerged openstack/releases master: preform final release of os-vif  https://review.opendev.org/c/openstack/releases/+/86364415:12
Clark[m]Right so the bug is just as valid on those branches too. But mostly I'm calling this as incomplete cleanup because maybe we can learn from it and do better in the future. Though hopefully python 4 isn't anything to deal with soon :)15:12
elodilles:)15:18
elodillesClark[m]: yepp, incomplete cleanup after py215:18
opendevreviewElod Illes proposed openstack/releases master: [nova] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86229815:26
*** dviroel is now known as dviroel|lunch15:26
*** dviroel|lunch is now known as dviroel16:43
opendevreviewElod Illes proposed openstack/releases master: [tripleo] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86234116:50
opendevreviewMerged openstack/releases master: [nova] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86229816:54
*** marios|ruck is now known as marios|out16:55
*** dtantsur_ is now known as dtantsur17:56
*** dtantsur_ is now known as dtantsur18:29
opendevreviewDouglas Mendizábal proposed openstack/releases master: Add missing stable branches for pycadf  https://review.opendev.org/c/openstack/releases/+/86368818:39
opendevreviewDouglas Mendizábal proposed openstack/releases master: Release pycadf for Wallaby  https://review.opendev.org/c/openstack/releases/+/86369219:05
opendevreviewDouglas Mendizábal proposed openstack/releases master: Release pycadf for Wallaby  https://review.opendev.org/c/openstack/releases/+/86369219:06
opendevreviewDouglas Mendizábal proposed openstack/releases master: Add stable/wallaby branch for pycadf  https://review.opendev.org/c/openstack/releases/+/86369419:08
opendevreviewDouglas Mendizábal proposed openstack/releases master: Move stable/wallaby in pycadf to EM  https://review.opendev.org/c/openstack/releases/+/86369519:09
opendevreviewMerged openstack/releases master: [watcher] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86234419:17
opendevreviewMerged openstack/releases master: [sahara] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86233519:33
opendevreviewMerged openstack/releases master: [senlin] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86233619:33
opendevreviewMerged openstack/releases master: [oslo] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86230119:35
*** amoralej is now known as amoralej|off19:41
opendevreviewDavid Wilde proposed openstack/releases master: Release pycadf for xena  https://review.opendev.org/c/openstack/releases/+/86369819:45
opendevreviewDavid Wilde proposed openstack/releases master: Release pycadf for xena  https://review.opendev.org/c/openstack/releases/+/86369819:46
opendevreviewDavid Wilde proposed openstack/releases master: Release pycadf for xena  https://review.opendev.org/c/openstack/releases/+/86369819:47
opendevreviewDavid Wilde proposed openstack/releases master: Add stable/xena branch for pycadf  https://review.opendev.org/c/openstack/releases/+/86370019:48
opendevreviewElod Illes proposed openstack/releases master: Release and branch cut test for 2023.1 Antelope  https://review.opendev.org/c/openstack/releases/+/86086919:50
opendevreviewDavid Wilde proposed openstack/releases master: Release pycadf for yoga  https://review.opendev.org/c/openstack/releases/+/86370319:51
*** dviroel is now known as dviroel|out19:52
opendevreviewDavid Wilde proposed openstack/releases master: Add stable/xena branch for pycadf  https://review.opendev.org/c/openstack/releases/+/86370419:52
opendevreviewDavid Wilde proposed openstack/releases master: Add stable/yoga branch for pycadf  https://review.opendev.org/c/openstack/releases/+/86370419:53
opendevreviewDavid Wilde proposed openstack/releases master: Release pycadf for zed  https://review.opendev.org/c/openstack/releases/+/86370619:55
opendevreviewDavid Wilde proposed openstack/releases master: Add stable/zed branch for pycadf  https://review.opendev.org/c/openstack/releases/+/86370719:57
opendevreviewDavid Wilde proposed openstack/releases master: Add stable/yoga branch for pycadf  https://review.opendev.org/c/openstack/releases/+/86370419:58
opendevreviewDavid Wilde proposed openstack/releases master: Add stable/yoga branch for pycadf  https://review.opendev.org/c/openstack/releases/+/86370420:00
opendevreviewDavid Wilde proposed openstack/releases master: Add stable/xena branch for pycadf  https://review.opendev.org/c/openstack/releases/+/86370020:02

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!