Thursday, 2021-01-21

*** armax has joined #openstack-release01:11
*** dave-mccowan has quit IRC01:24
*** armax has quit IRC01:44
*** ricolin_ has joined #openstack-release02:14
*** ricolin_ has quit IRC04:20
*** ricolin has joined #openstack-release04:24
*** ykarel has joined #openstack-release04:52
*** ricolin has quit IRC05:11
*** ricolin has joined #openstack-release05:24
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** whoami-rajat__ has joined #openstack-release05:56
*** vishalmanchanda has joined #openstack-release05:58
*** ykarel_ has joined #openstack-release06:16
*** ykarel has quit IRC06:19
*** tkajinam_ has joined #openstack-release07:19
*** tkajinam has quit IRC07:20
*** ykarel_ is now known as ykarel07:27
*** sboyron has joined #openstack-release07:57
*** slaweq has joined #openstack-release07:58
*** e0ne has joined #openstack-release07:58
noonedeadpunkhberaud: we actually collect all new renos to the openstack-ansible repo. But we post them for current roles.08:11
hberaudnoonedeadpunk: Please can you give me an example08:11
*** rpittau|afk is now known as rpittau08:11
noonedeadpunkSo everything that is present for specific roles ends up being released for central repo. But the question here is that they still got published incorrectly for the specific repos as well... And they even not put into correct releases since there're no tags there which is kind of confusing08:12
*** sboyron has quit IRC08:14
hberaudCan't we simply deactivate reno on these specific repos?08:14
noonedeadpunkyeah, so we copy them with bumps. ie - haproxy-hatop reno has been copied from
noonedeadpunkyou mean not to post new release notes for this repos? and drop current ones?08:15
*** tosky has joined #openstack-release08:16
noonedeadpunkwell, techincally, we can do that. But I think that way we just won't be pushing renos when needed, since they would need to be done with a separate patch to another repo08:16
noonedeadpunkWhich I don't believe would be ever done. so we will end up without proper notes for users, which is bad08:17
hberaudI see08:19
noonedeadpunkwhat actually makes release notes being published? Maybe we can set smth in config to prevent this from happening?08:20
hberaudIndeed it seems a realistic scenario for the future if reno is deactivated on these repos08:20
openstackgerritAkihiro Motoki proposed openstack/releases master: Drop tempest-horizon from wallaby deliverables
* hberaud lemme grab some links for you08:20
noonedeadpunkor some tag/option in releases?08:21
noonedeadpunkas actually all these roles are in separate deliverable08:21
hberaudI don't think this kind of option exist in "release"08:23
*** sboyron has joined #openstack-release08:24
noonedeadpunkI just not quite understand how exactly this happens.. I guess that it's somehow related to `diff-start` from deliverables as it relies on it to distinguish releases08:24
noonedeadpunkAnd wondering if set target_name for all repos to jsut opensatck-ansible - would they result into correct url under correct releases (I guess they won't since they won't be in diff for that repo)08:25
hberaudno idea08:26
hberaudnoonedeadpunk: so here are zuul's related jobs,L25608:28
noonedeadpunkand what is build-releasenotes role ?08:35
hberaudI think that master is automatically sync to provide the unreleased changes08:36
noonedeadpunkrenos for me feels like a bit of magic tbh :)08:36
hberaudand reno is based on git branches and tags, that could explain why your roles relnotes are wrong but present even if you don't tag them08:37
*** sboyron has quit IRC08:37
hberaudI'm not sure who will trigger this build in a non tagged context08:38
hberaudmaybe this one
hberaudTBH I'm not the most skilled person of the team about reno08:39
hberaudttx: any idea? ^ (do you know how are triggered/built/published relnotes for untagged projects like with openstack-ansible roles)?08:41
ttxno idea at first glance, and no time to dive deeper right now. Will try to have a look later today...08:43
hberaudack, np08:43
ttxhberaud: weird stable/wallaby branch request in
hberaudah yes good catch08:48
hberaudI wonder how it got there08:48
ttxwould be good to double check all the others08:49
hberaudWill do08:49
ttxincluding ones that may have already made it08:49
hberaudI used these commands
hberaudmaybe I asked for a stable branch08:50
hberaudIIRC the command crashed at one point and I restarted it08:51
openstackgerritMerged openstack/releases master: Generalize usage of tools/
hberaudI surely replied yes at the stable branch question08:52
hberaudand so normally not all these patches are impacted08:52
ttxbut that seems the only with the stable branch, the others looked clean (only checked those with PTL+108:52
hberaudbut I'll double check them08:52
hberaudIIRC the command crashed more or less at the end08:53
ttxok so maybe it's the last one and you replied yes08:53
hberaudcould be08:53
openstackgerritHervĂ© Beraud proposed openstack/releases master: Wallaby-2 Release for python-tackerclient
hberauddone ^08:54
*** brinzhang has quit IRC08:55
ttxit's definitely the last in alpha order08:55
*** brinzhang has joined #openstack-release08:55
hberaudit could be useful to allow to pass params by using the CLI08:55
hberaudto avoid this case08:55
ttxprevious one (python-novaclient) is clean08:56
hberaudand not only by using an interactive mode08:56
*** brinzhang has quit IRC08:57
*** brinzhang has joined #openstack-release08:57
openstackgerritMerged openstack/releases master: Release OpenStack-Ansible Victoria
hberaudI was already thinking about this kind of new feature during my last usage so this is definitelly a good reason to propose a patch08:58
openstackgerritMerged openstack/releases master: Wallaby-2 Release for python-ironicclient
hberaudI added this topic (passing args to process_auto_release) to the "things to change" section
openstackgerritMerged openstack/releases master: Release openstacksdk 0.53.0
openstackgerritMerged openstack/releases master: Wallaby-2 Release for ironic-lib
openstackgerritMerged openstack/releases master: [Tempest] Tag stein-last
openstackgerritMerged openstack/releases master: [Tempest Plugins] Tag stein-last
*** ykarel_ has joined #openstack-release09:34
*** tosky has quit IRC09:36
*** tosky_ has joined #openstack-release09:36
*** ykarel has quit IRC09:37
*** ykarel_ is now known as ykarel09:39
*** tosky_ is now known as tosky09:43
*** sboyron has joined #openstack-release10:14
openstackgerritDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Ussuri
*** dtantsur|afk is now known as dtantsur10:58
*** e0ne has quit IRC11:28
*** ricolin has quit IRC12:06
*** tosky has quit IRC13:06
*** tosky has joined #openstack-release13:06
*** ricolin has joined #openstack-release13:08
ttxok looking into that reno mystery now13:31
ttxAFAICT for each change, the gate pipeline builds release notes (build-openstack-releasenotes job), and the promote pipeline publishes them (promote-openstack-releasenotes job)13:43
ttxnow looking into jobs defined for ansible roles repos13:43
ttxThose jobs are inherited through the release-notes-jobs-python3 template13:45
ttxas defined for example here:
ttxnoonedeadpunk: now I have no idea how the "openstack-ansible collects renos for all openstack roles" logic works, it's probably OSA-specific ?13:47
noonedeadpunkyeah, it is)13:48
ttxBut if you want to prevent promotion of release notes you will have to tweak those zuul.d/project.yaml files13:48
ttxso that they build them but do not promote them13:48
noonedeadpunkactually I think we can even avoid building them13:49
ttxbuilding them will ensure that you do not introduce a faulty reno in the mix13:49
noonedeadpunkexcept for testing purposes13:49
ttxyeah, building is just testing they build :)13:49
ttxunless you "promote" the results of that build13:49
noonedeadpunkbut not sure how from zuul prespective we should do that... create another job with the same naming?13:49
noonedeadpunkI guess infra won't be happy about that..13:50
ttxnoonedeadpunk: no, you just have to configure the set of jobs you actually want to run, instead of taking the whole release-notes-jobs-python3 template13:50
ttxThe template (defined in zuul.d/project-templates.yaml in openstack-zuul-jobs repo) has:13:51
noonedeadpunkaha, I see13:51
ttxsorry I build the link as I go so keep up with me13:52
ttxso a check, a gate, a promote and a tag job addtions13:53
noonedeadpunkI think we can use just buiuld template
ttxYou should be able to replace that template inclusion in places like
ttxby the chech and gate parts of that template, but not the other13:54
noonedeadpunkthere's a template that should suite us as well:)13:54
noonedeadpunkok, that's pretty straightforward, thanks!13:54
ttxah, yes13:55
noonedeadpunkany way to unpublish already published stuff ?:)13:55
ttxeven simper13:55
ttxunpublish, I think that will require opendev admin action13:55
noonedeadpunkok, I see, anyway I guess first of all we need to stop publishing things13:55
ttxright :)13:55
hberaudReally instructive! Thanks ttx14:00
ttxIt's good gymnastics14:00
hberaudttx: don't forget to stretch now14:01
*** ykarel is now known as ykarel|mtg14:10
*** markmcclain has quit IRC14:26
*** dave-mccowan has joined #openstack-release14:29
*** dave-mccowan has quit IRC14:34
*** vishalmanchanda has quit IRC14:38
*** dave-mccowan has joined #openstack-release14:40
*** markmcclain has joined #openstack-release14:46
*** brinzhang has quit IRC15:01
*** brinzhang has joined #openstack-release15:01
*** brinzhang has quit IRC15:04
*** brinzhang has joined #openstack-release15:04
*** ykarel|mtg is now known as ykarel15:08
*** irclogbot_3 has quit IRC15:21
*** irclogbot_2 has joined #openstack-release15:23
*** armax has joined #openstack-release15:25
openstackgerritMarios Andreou proposed openstack/releases master: Make TripleO repos wallaby-2 release
*** armax has quit IRC15:48
*** armax has joined #openstack-release16:06
*** e0ne has joined #openstack-release16:29
jokkeAnyone around to kick off the Glance M-2 release or should I drop it until next week?16:44
*** armstrong has joined #openstack-release16:51
*** armax has quit IRC16:52
hberaudjokke: done
hberaud#startmeeting releaseteam17:00
openstackMeeting started Thu Jan 21 17:00:01 2021 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: releaseteam)"17:00
openstackThe meeting name has been set to 'releaseteam'17:00
hberaud#link Agenda17:00
hberaudPing list: ttx armstrong elod17:00
hberaudWe're way down on line 261 now.17:00
fungithis cycle has flows by, seems like17:00
hberaudWill just wait a couple minutes for folks.17:00
hberaudit seems17:01
hberaudok let's go17:03
hberaud#topic Review task completion17:03
*** openstack changes topic to "Review task completion (Meeting topic: releaseteam)"17:03
hberaudGenerate a list of all cycle-with-intermediary libraries which did not release since the YYYY-MM-DD date of milestone-1. => done17:04
hberaudNobody complain for now17:04
hberaudwe don't have any exception for now17:04
hberaudI think we can go ahead17:04
hberaudttx do you want to push the final button?
ttxsure looking17:05
ttxhmm for those missing the PTL+1 we shoudl wait a bit more right17:05
hberauddeadline is today but we can wait until tomorrow17:06
hberaudor at least monday17:06
hberaudany preference?17:06
ttxwe usually give them until the Monday and then +2a then17:06
hberaudok sold17:06
hberaudNext task17:06
hberaudGenerate release requests for all cycle-with-intermediary libraries which had changes => ttx the floor is yours17:07
ttxnah that's not me17:08
ttxaclissues is me17:08
hberaudI see your name/color assigned this is why I asked you17:09
ttxI ran it and it returned nothing to fix17:09
*** ykarel has quit IRC17:09
ttxMy bullet starts at "To catch"17:09
hberaudok thanks fair enough17:09
openstackgerritMerged openstack/releases master: Release Glance wallaby m-2 (
hberaudahah sorry my bad17:09
hberaudwrong copy/past17:10
hberaudIt's exact17:10
hberaudSo I think we can move on17:10
hberaudHandle governance consistency issues => hberaud17:10
*** ykarel has joined #openstack-release17:11
hberaudso I discussed with the majority of the involved teams17:11
armstrongI am available for any task that  can help17:12
hberaudConcerning barbican, and the ansible roles, I didn't get a definitive response for now, I relaunched this subject this afternoon17:12
hberaudarmstrong: thanks17:12
hberaudAlways concerning barbican, they wait for an RFE for barbican ui, so I think we can leave that as it is for now17:13
openstackgerritMerged openstack/releases master: Release sushy 3.6.0 for Wallaby
hberaudConcerning oslo and etdc3gw osloers agreed with that so I proposed a patch to adopt the independent model17:14
openstackgerritMerged openstack/releases master: Release OpenStack-Ansible Train
ttxhberaud: yeah, it's ok if they don;t decide right now. It's good to track progress though, since those items can easily fall between the cracks and disappear17:15
hberaudConcerning tripleo and opentack tempest skiplist, tripleo chose to abandon it
hberaudSame thing for OpenStackSDK and js-openstack-lib
hberaudSame thing for monasca-*
hberaudI just see that gmann commented on it, I'll follow that17:17
hberaudand last but not the least rpm-packaging17:17
*** ykarel has quit IRC17:17
hberaudWe discussed about that today17:17
hberaudAnd I think that either we need governance/SIG model updates or something else17:18
hberaudOr our tooling should consider the SIG file too...17:19
ttxwell no17:20
hberaudTo see if projects are present in and then ignore it or give them a special status17:20
ttxsince we do not handle releases for SIGs17:20
ttxi think the simplest is just to remove the files17:20
openstackgerritMerged openstack/releases master: Wallaby-2 Release for python-tackerclient
ttxno need for a special case really17:20
hberaudI was thinking to reply on the related ML thread ( and to involve the TC to the discuss too17:21
ttxOh I was supposed to file those17:21
hberaudbut if you think that remove is enough then let's go17:21
ttxbut did not17:21
hberaudthe rpm-packaging team don't really care about this so...17:22
ttxremoving is the only way to fix it. We can't have all the history since they do not use openstack/releases anymore. So the choice is between partial history (which is blatantly misleading) and no history at all17:22
hberaudttx: do you want to handle that?17:23
ttxyes yes17:23
ttxI just need to remember to do it. Will do tomorrow17:23
ttxplease action me on next week tasks to be sure17:23
hberaudand that's all for task completion17:24
hberaudanything else before moving?17:24
hberaud#topic [TripleO] moving stable/rocky for tripleo repos to unmaintained (+ then EOL)17:24
*** openstack changes topic to "[TripleO] moving stable/rocky for tripleo repos to unmaintained (+ then EOL) (Meeting topic: releaseteam)"17:24
elodI've replied (a bit late) to the list17:25
ttxyeah I don;t have a strong opinion on that17:25
elodI think it's OK to go EOL if they want17:25
hberaudTripleo's PTL asked if we can move tripleo repos for rocky to unmaintained and elod and myself proposed to move directly to EOL17:26
elodwell, they can leave the branch in EM for 6 more months,17:26
hberaudMy goal here is to grab your opinion17:27
elodit's not a must I mean17:27
hberaudYou mean that they can't move for now?17:27
elodit's a team decision if they want to wait or go directly to EOL17:28
elodthey can17:29
hberaudOk let's wait few days for that, I'll rediscuss with Marios soon if needed to see what they chose17:29
elodit's just a buffer time (6 months - unmaintained), i would say17:29
elodso they can continue with the steps in the process ( )17:30
hberaudI see17:30
hberaudelod: thanks for your response/details on the thread and here17:30
hberaudAnything else for this topic?17:31
elodspeaking of that... we might need to ask infra to delete the old, already EOL'd branches (like ocata)17:31
*** dave-mccowan has quit IRC17:31
hberaudelod: do you want to handle that point?17:32
elodyes, I'll add that to my TODOs :)17:32
elodand look for EOL'd ocata branches17:33
elod+ ask infra to delete them17:33
elodfor a starter17:33
hberaudI added it to the next week tasks17:34
elodcool, thanks!17:34
hberaud#topic reenqueue kolla job17:34
*** openstack changes topic to "reenqueue kolla job (Meeting topic: releaseteam)"17:34
hberaudI noticed that we surely missed to reenqueue this job and I want to confirm that point with fungi17:35
hberaudYou replied on the thread but we didn't discussed together about the reenqueue part of this topic17:37
fungirelease-openstack-python succeeded there17:37
hberaudJust to be sure to unmiss something17:38
fungiwe can't reenqueue the tag, as it will try to upload a new release to pypi17:38
hberaudno the problem is not there17:39
fungifailures seem to be for kolla-publish-debian-source-aarch64, kolla-publish-ubuntu-source and kolla-publish-ubuntu-binary17:39
fungiwhich someone would need to build and manually upload i think17:39
hberaudThe problem was on a docker registry limitation IIRC17:40
hberaudWhere the job reached the new registry limitation17:40
fungiyeah, i'm not sure what can be done about that other than someone manually creating and uploading those images17:40
hberaudI see17:40
fungisomeone in the kolla team, in theory, has write access to their dockerhub org17:41
*** diablo_rojo has quit IRC17:41
fungiso they could do that if they wanted17:41
hberaudNobody complained since17:41
hberaudSo I think we can consider this point on their side17:42
*** rpittau is now known as rpittau|afk17:42
hberaudThanks for details17:42
hberaudI think we can move on17:43
hberaud#topic Assign R-11 tasks17:43
*** openstack changes topic to "Assign R-11 tasks (Meeting topic: releaseteam)"17:43
hberaudReview any remaining milestone-2 exceptions - I think this is for everybody17:43
hberaudPlan the next release cycle schedule based on the number of desired weeks - I'm already on it17:44
armstrongwant to add my name to #304 with @hberaud17:44
hberaudarmstrong: sure17:44
hberaudI think I'll work on that on Tuesday17:45
hberaudarmstrong: is it ok for you?17:45
armstrongwhat time?17:46
hberaudAround 1:30pm UTC +117:46
hberaudarmstrong: Thanks for your help17:47
armstrong@hberaud  my pleasure17:47
hberaudand the two last item was already discussed previously and assigned so I think we can skip them17:47
hberaud#topic Open Discussion17:48
*** openstack changes topic to "Open Discussion (Meeting topic: releaseteam)"17:48
hberaudAnything else?17:48
elodnothing from me17:48
hberaudSo I think we are done!17:50
hberaudThanks everyone!17:50
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at"17:50
openstackMeeting ended Thu Jan 21 17:50:48 2021 UTC.  Information about MeetBot at . (v 0.1.4)17:50
openstackMinutes (text):
elodthanks hberaud ! o/17:51
openstackgerritMerged openstack/releases master: Wallaby-2 Release for python-cyborgclient
*** dtantsur is now known as dtantsur|afk18:32
*** e0ne has quit IRC18:33
*** haleyb has quit IRC19:27
*** haleyb has joined #openstack-release19:28
openstackgerritBalazs Gibizer proposed openstack/releases master: Wallaby-2 Release for python-novaclient
*** dave-mccowan has joined #openstack-release19:53
*** slaweq has quit IRC19:55
*** sboyron has quit IRC20:09
*** irclogbot_2 has quit IRC20:14
*** tosky has quit IRC20:14
*** tosky has joined #openstack-release20:15
*** irclogbot_3 has joined #openstack-release20:17
*** whoami-rajat__ has quit IRC21:04
*** brinzhang has quit IRC23:00
*** armstrong has quit IRC23:01
*** brinzhang has joined #openstack-release23:34

Generated by 2.17.2 by Marius Gedminas - find it at!