Thursday, 2020-10-01

*** ricolin_ has joined #openstack-release01:14
*** diablo_rojo has joined #openstack-release02:33
*** ricolin_ has quit IRC03:10
*** ykarel|away has joined #openstack-release04:12
*** ykarel|away is now known as ykare04:12
*** ykare is now known as ykarel04:12
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-release04:33
*** ykarel_ has joined #openstack-release04:34
*** ykarel has quit IRC04:36
*** diablo_rojo has quit IRC04:50
*** olivierbourdon38 has quit IRC05:01
*** ykarel_ is now known as ykarel05:10
*** sboyron has joined #openstack-release05:43
*** ricolin_ has joined #openstack-release06:07
*** ykarel_ has joined #openstack-release06:27
*** ykarel has quit IRC06:29
*** slaweq has joined #openstack-release06:30
*** jhesketh has quit IRC06:35
*** haleyb has quit IRC06:54
*** rosmaita has quit IRC06:54
*** jtomasek has joined #openstack-release06:57
*** ykarel_ is now known as ykarel07:07
*** jhesketh has joined #openstack-release07:10
*** ricolin_ has quit IRC07:10
*** zigo has joined #openstack-release07:12
ykarelrelease-openstack-python jobs getting post failures https://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-python07:29
ykarelwould be better to get it clear before releasing more projects else they would also face same07:30
ykarelit's failing while building cmarkgfm, while in passing job i see wheel is used07:34
*** tosky has joined #openstack-release07:39
*** e0ne has joined #openstack-release07:42
*** jbadiapa has joined #openstack-release07:47
*** rosmaita has joined #openstack-release08:07
*** haleyb has joined #openstack-release08:07
*** tkajinam has quit IRC08:47
ttxykarel: yes, known issue with the switch to focal and some PyPI uploads missing py38 wheels08:50
*** strigazi has quit IRC08:51
ttxreleases are frozen until we fix it08:51
*** strigazi has joined #openstack-release08:51
ykarelttx, ack but from job logs it's seem those jobs running in ubuntu-bionic08:51
ykarelhttps://0dc6dce67e17cc56cbee-22a46b7f7ce23fe9b2117d76fd7c738d.ssl.cf5.rackcdn.com/afd1906b3638a5fdb981947f11a245a79fec9985/release/release-openstack-python/5ae1e14/job-output.txt08:51
*** haleyb has quit IRC08:52
*** rosmaita has quit IRC08:52
ttxhmm, looking08:53
ttxthe post playbook seems to be running on localhost08:54
ttxand that's the part failing (uploading to pypi)08:55
ttx(haven't looked too deep, but that may explain it)08:58
*** e0ne_ has joined #openstack-release09:02
*** e0ne has quit IRC09:05
*** rosmaita has joined #openstack-release09:10
*** haleyb has joined #openstack-release09:10
*** priteau has joined #openstack-release09:48
ykarelttx, Thanks, yes you are right10:07
ykarelit's localhost and there py38 is there10:07
*** smcginnis has quit IRC10:22
*** smcginnis has joined #openstack-release10:22
openstackgerritMerged openstack/releases master: Create stable/victoria for grenade  https://review.opendev.org/75533310:25
openstackgerritThierry Carrez proposed openstack/releases master: Add release notes links for Victoria release  https://review.opendev.org/75547610:27
openstackgerritDaniel Bengtsson proposed openstack/releases master: New bugfix release oslo.privsep for ussuri.  https://review.opendev.org/75548510:52
openstackgerritDaniel Bengtsson proposed openstack/releases master: New major release for tripleo-upgrade.  https://review.opendev.org/75549011:31
*** e0ne has joined #openstack-release11:45
*** e0ne_ has quit IRC11:48
ttxfungi: we need to unblock releases, what are our various options and what do they entail?12:13
ttxI see... revert executors to bionic (less disruptive fro releases, most disruptive for opendev)12:14
ttx- add a couple packages on the executor so that it survives absence of py38 wheels12:14
ttx(I suspect that's done by tweaking bindep somewhere)12:15
ttxfungi: was there another option12:15
ttx?12:15
*** haleyb has quit IRC12:22
*** haleyb has joined #openstack-release12:24
rosmaitattx: (05:02:25 PM) fungi: also if we had it in the openstack constraints list we'd build wheels for it which jobs could access12:28
ttxhah, so just adding twine to, say, test-requirements could do it?12:29
rosmaitattx: i don't really know, just repeating what i heard12:31
slaweqsmcginnis: ttx: hi, can You check https://review.opendev.org/#/c/753230/ ?12:56
slaweqsmcginnis: ttx: and also one more question12:56
slaweqI just found out that in neutron-lib-stable-maint group there is nobody12:56
slaweqcan we maybe include neutron-stable-maint group there too?12:57
slaweqor that isn't possible/easy to do by irc discussion?12:57
ttxhmm, is that group even used? Let me check12:57
ttxslaweq: is there value for neutron-lib to have its own ACL, distinct from neutron?12:58
ttxlike is neutron-lib-core ≠ neutron-core?12:58
slaweqttx: IMHO, at least currently there is no real value for that12:58
ttxslaweq: three solutions... we can populate neutron-lib-stable-maint, we can fix neutron-lib ACL so that it uses neutron-stable-maint, or we can just make neutron-lib use the neutron ACL12:59
ttxdepending on how distinct you want it to be13:00
ttx(from more distinct to less distinct from neutron)13:00
ttxyour call, really13:02
slaweqneutron-lib-core is different than neutron-core13:02
slaweqbut changing acl of neutron-lib for stable branches to allow neutron-stable-core to +2 there would be good13:03
slaweqor adding neutron-stable-core in neutron-lib-stable-core,13:04
slaweqboth those would be ok for me TBH13:04
smcginnisttx: We may just need to add gcc to our bindep file. Assuming that is all that is needed to be able to successfully install twine now.13:04
ttxslaweq: I'll just add it into the other group. A half-ACL would be confusing imho13:04
slaweqttx: sounds good for me, thx a lot13:05
ttxslaweq: actually can't fix it, but I bet fungi can13:05
slaweqttx: thx for taking care of it :)13:06
ttxsmcginnis: our bindep... where is that one again?13:08
smcginnisttx: There should be a bindep.txt in the root of the repo.13:08
smcginnisYep, there is.13:08
ttxthe releases repo? How would that help13:09
smcginnisCould just try adding gcc there and merge that, then do a release test. Even though that's c-w-i, it should exercise the job in question.13:09
ttxthe job that's failing is a publication job, ran from teh published repo, not releases?13:09
ttxor is there some artificial provision that makes the executor also apply the releases bindep?13:10
smcginnisHmm, right. I was thinking it would start in releases and get the environment set up based on our bindep file, but for this job that is not the case.13:10
smcginnisSo I guess we maybe need some suggestions from fungi or others in infra.13:10
ttxIn tat case I feel like we'll need the executor to have those two extra packages installed13:10
*** ricolin_ has joined #openstack-release13:11
ttxand with half the things being dockerized today I'm not sure where that lives13:13
smcginnisI wonder if we can update the job to specify it needs bionic? But if it runs on the executor, I guess that doesn't really work.13:14
ttxI might have been nisinterpreting what I saw in the logs, but it seems to be a localhost post-job13:15
ttxbetter wait for fungi's answer, no need to speculate13:15
smcginnisWhere's the fun in not coming up with elaborate solutions based on pure speculation? :)13:16
ttxI know, I'm on it13:17
ttxhttps://opendev.org/opendev/puppet-zuul/src/branch/master/manifests/executor.pp#L42 maybe?13:18
openstackgerritJulia Kreger proposed openstack/releases master: Release ironic 16.0.0 for victoria  https://review.opendev.org/75539213:18
ttxor https://opendev.org/opendev/puppet-zuul/src/branch/master/manifests/init.pp#L11513:19
*** ricolin_ has quit IRC13:21
smcginnisI wonder if it would be better if the ensure-twine role took care of it.13:24
*** slaweq has quit IRC13:36
fungicatching back up on the discussion13:39
fungithe executors aren't any particular distro (if anything they're a very stripped down debian container)13:41
fungibut yes, if we're running twine on the executors then it's possible none of our mirrors are accessed for installing that13:42
fungii'll have to look at one of the failures and confirm13:42
*** slaweq has joined #openstack-release13:42
fungiwe don't use that puppet module to install zuul any longer, just the ansible service playbooks in system-config deploying docker container images with docker-compose13:43
fungiwhen did the error start appearing? just in the last day?13:44
fungiyes, i confirm, ensure-twine is getting run on the executor according to the "localhost" in this playbook: https://opendev.org/openstack/project-config/src/branch/master/playbooks/publish/pypi.yaml13:47
fungitwine hasn't been updated since june, and cmarkgfm hasn't had a new release in two years, so it's neither of those which have triggered it. the executor container must have updated to a new python interpreter version13:49
ttxI guess the fails started when executors started to potentially run py38?13:49
fungihttps://review.opendev.org/727374 merged two days ago13:51
fungi"Update images to use python 3.8"13:51
ttxthat sounds like it could explain it :)13:51
fungiso it was upstream zuul switching to python 3.8 for its image builds which trickled down to start showing this13:51
ttxI guess we could fix it at ensure-twine level... it could install a couple extra packages to make sure twine works properly13:52
ttxor it could be fixed at image level but that sounds more intrusive13:52
fungiwell, it would need root permissions to add compiler packages13:53
* ttx goes on the hunt to find where the hell ensure-twine role is defined, always fun13:55
ttxzuul/zuul-jobs apparently13:57
ttxhmm not sure how we'd fix it a job level withuot root rights13:59
fungitrying to talk through the options in #zuul since it's really an upstream zuul issue (the ensure-twine role in zuul's stdlib is no longer usable on its latest container images)14:00
*** diablo_rojo has joined #openstack-release14:02
ttxhah, true that14:02
ttxI'd recommend a revert until a more elaborate/elegant solution can be designed14:02
ttxif only to unblock the regression14:02
fungiyeah, once the revert merges and updated images appear on dockerhub i can work on restarting our executors14:11
fungii expect it was an executor restart (after the images updated to 3.8) which marked the start of seeing this failure mode14:11
ttx++14:12
openstackgerritHervé Beraud proposed openstack/releases master: release renderspec 2.1.0  https://review.opendev.org/75552114:12
openstackgerritThomas Bechtold proposed openstack/releases master: renderspec: Release 3.0.0  https://review.opendev.org/75552214:13
openstackgerritThomas Bechtold proposed openstack/releases master: pymod2pkg: Release 1.0.0  https://review.opendev.org/75552414:15
*** ricolin_ has joined #openstack-release14:31
*** armstrong has joined #openstack-release14:35
*** ricolin has quit IRC14:37
evrardjpthanks ttx and fungi for tackling this!14:38
slaweqttx: smcginnis can You also check https://review.opendev.org/#/c/752380/ ? it is needed to merge in neutron-lib patch which will unblock nova's gate14:51
smcginnisslaweq: Done14:51
slaweqsmcginnis: thx a lot14:52
openstackgerritThomas Bechtold proposed openstack/releases master: pymod2pkg: Release 1.0.0  https://review.opendev.org/75552415:05
*** ricolin_ has quit IRC15:17
*** e0ne has quit IRC15:32
openstackgerritHervé Beraud proposed openstack/releases master: Adding a new tools to search topic on the ML  https://review.opendev.org/75536215:39
*** ykarel is now known as ykarel|away15:48
*** ykarel|away has quit IRC15:53
*** diablo_rojo has quit IRC15:57
ttxo/16:02
smcginnisOops...16:02
smcginnisSorry, distractions.16:02
armstrongo/16:02
smcginnis#startmeeting releaseteam16:03
openstackMeeting started Thu Oct  1 16:03:10 2020 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: releaseteam)"16:03
openstackThe meeting name has been set to 'releaseteam'16:03
smcginnisPing list: ttx armstrong sboyron16:03
smcginnis#link https://etherpad.opendev.org/p/victoria-relmgt-tracking Agenda16:03
smcginnis#topic Review tasks completion16:03
*** openstack changes topic to "Review tasks completion (Meeting topic: releaseteam)"16:03
hberaudo/16:03
smcginnisSo tasks for the week...16:04
smcginnisForce RCs on Monday - those are all done.16:04
smcginnisRC1 deadline exceptions - I don't believe we have any left over.16:04
hberaudagreed16:04
smcginnisMissing stable branches - looked like from the paste that there were only the trailing ones, so that's great.16:05
smcginnisI saw hberaud reminded QA about the various tasks. Another topic later to talk about that some more.16:05
smcginnisAnd ttx ran the script to add the release notes links for the projects that have merged their patches for a victoria landing page.16:06
smcginnisIt's not in the process doc, but I've usually run that script randomly over the next several weeks to see if there are more.16:06
smcginnisSome projects are really good about landing those patches right away. Others can take a long time to get any attention.16:06
smcginnisSo good to run it again occasionally to pick up those late ones.16:07
smcginnisNext task is really just a note to the team to allow new RCs as needed.16:07
hberauddo we want everybody to +1 on this patch or it's more an highlight?16:07
smcginnisWe don't need to get acks from everyone. We can just approve it.16:08
hberaudack16:08
smcginnisFor new RCs, we want to encourage teams to do new ones to pick up things like translations or important bugs.16:08
smcginnisWe just don't want to do them too frequently. It seems to work well to do the RC1, then wait until close to the final RC deadline to pick up those things for a final RC.16:09
smcginnisBut we can allow them to do more as needed depending on each teams situation.16:09
smcginnisFinal task, I will send the countdown email. I'll try harder to do that more timely this time. :)16:10
hberaud:)16:10
smcginnis#topic Review countdown email content16:10
*** openstack changes topic to "Review countdown email content (Meeting topic: releaseteam)"16:10
smcginnis#link https://etherpad.opendev.org/p/relmgmt-weekly-emails16:10
smcginnisI think I updated the content but not the subject line. Let me double check that.16:10
smcginnisYeah, content looks right. Just missed the subject line.16:11
hberaudLGTM16:11
smcginnisGood. Rereading it looks fine to me too.16:12
smcginnis#topic Assign R-1 tasks16:12
*** openstack changes topic to "Assign R-1 tasks (Meeting topic: releaseteam)"16:12
smcginnisProcess remaining stable branch exceptions.16:12
smcginnisSince everyone had their stable branches, I think that first task is a noop this time around. \o/16:12
smcginnisNotify the docs team. Thanks for grabbing that hberaud.16:13
smcginnisSince we don't actually have a docs team anymore, not sure what we need to do there.16:13
smcginnisIt generally gets taken care of. Kind of like the QA tasks, they know what needs to be done.16:13
hberaudah16:13
smcginnisIIRC, AJaeger usually updates the docs things, so might be good to check in with him.16:13
hberaudack16:14
gmannI am doing for d-g and grenade16:14
smcginnisTest the release process. release-test is now c-w-i instead of c-w-rc, but that still works to make sure our jobs all pass. Like it could have caught this current breakage.16:14
smcginnisgmann: Thanks!16:14
fungiyou could say "technical writing sig" instead of "docs team" i guess?16:14
openstackgerritThomas Bechtold proposed openstack/releases master: pymod2pkg: Release 0.26.0  https://review.opendev.org/75552416:15
smcginnisYeah, I guess so.16:15
armstrong+1 fungi16:15
smcginnisNext tasks - on Wednesday we should run tools/list_rc_updates.sh to see if there are any important but not yet released commits.16:15
openstackgerritThomas Bechtold proposed openstack/releases master: renderspec: Release 2.1.0  https://review.opendev.org/75552216:16
smcginnisThis is a little subjective, but in general we want to look for anything that looks like it might be good to get in the initial coordinated release.16:16
smcginnisThings can be merged, but it's fine if the team wants to wait until after the coordinated release date to do a stable release.16:16
smcginnisAnyone want to take that? I can assist with giving feedback on any repos in question.16:17
armstrongI am available16:17
armstrongif the result is not too difficult to interpret16:17
hberaudarmstrong: do not hesitate to ask questions if you need help :)16:18
smcginnisarmstrong: Great, thanks. Just let me know if there are any questions with the output. Or I guess just ask this channel in general, then any one of us can help provide input on that.16:18
armstrongok16:18
smcginnisI will finish out the victoria countdown emails.16:18
ttxThe trick is to try to spot things that cannot be added after release as stable updates16:18
armstrongSo, I should run the script on Wednesday right?16:18
ttxand that are highly desirable16:18
smcginnisAnd I can run the propose-final-releases script to get the final releases.16:19
ttxLike... something that fixes the upgrade from the previous version16:19
smcginnisarmstrong: Yep.16:19
smcginnis#topic Review process for cycle-automatic deliverables16:19
*** openstack changes topic to "Review process for cycle-automatic deliverables (Meeting topic: releaseteam)"16:19
smcginnisThis came up this week because one of the tasks in the process doc is to propose releases for the cycle-automatic deliverables.16:20
smcginnisBut we don't have cycle-automatic deliverables anymore. :)16:20
smcginnisSo I don't _think_ our process should change, but we should update the doc to be more specific/accurate now.16:20
hberaud+116:20
smcginnisI wanted to raise it here to see if there are any other thoughts or questions about that.16:21
smcginnisttx: You led the charge to get rid of the model, so was also curious if you had any thoughts about it.16:21
ttxlet me gather my thoughts16:21
hberaudFWIW I agreed with the removal I don't see much value to keep an outdated process in our doc16:22
ttxwe should probably doublecheck that nothing fell in the cracks16:22
smcginnisHmm, now I am not seeing that model specifically mentioned in the doc. We may have dropped that.16:22
smcginnisI was reminded by someone asking in-channel when the tempest plugins would be tagged.16:23
ttxbasically, cycle-automatic was about us proposing releass at the very last moment for a number of deliverables16:23
ttxbut we are supposed to catch them all before, now16:23
ttxso checking that we have a deliverable for everything, including "type:other" cwi things, would be good16:24
*** diablo_rojo has joined #openstack-release16:25
smcginnisWe may want to put a reminder in the process docs about tempest plugins and how they need to be tagged but not branched.16:25
smcginnisWhat was cycle-auto is now mostly the ones that are cwi with stable-branch-type: none16:25
ttxbecause afaict those tempest-plugins have been falling through the cracks16:26
smcginnisWe tagged them all last cycle at the end. But then this cycle, I'm guessing they may have been excluded from the normal checking for proposing releases since they need to tag at the end, not during any of the milestones.16:27
ttxbarbican-tempest-plugin16:27
ttxdesignate-tempest-plugin16:27
ttxfreezer-tempest-plugin16:27
ttxheat-tempest-plugin16:27
ttxkeystone-tempest-plugin16:27
ttxmistral-tempest-plugin16:27
hberaudhttps://github.com/openstack/releases/commit/309e95eaad04f76c260e8645967f2d58f85dc7d916:27
ttxmonasca-tempest-plugin16:27
ttxmurano-tempest-plugin16:27
ttxrequirements16:28
ttxsahara-tests16:28
ttxsolum-tempest-plugin16:28
ttxtelemetry-tempest-plugin16:28
ttxrequirements is probably off16:28
ttxbut sahara-tests probably in16:28
ttxhberaud: maybe we catch "type:other" explicitly but not "type:tempest-plugin"16:29
ttxanyway that means we need to do it now :)16:29
smcginnis#link https://review.opendev.org/#/q/project:openstack/releases+branch:master+topic:victoria-c-a16:29
smcginnisJust a few outstanding.16:29
ttxah, so you covered those16:30
hberaudnice16:30
smcginnisYeah, after the ping in the channel, I noticed we didn't call those out anywhere so I ran the handy script to get them proposed.16:30
smcginnisBut I wanted to make sure we captured this in the process doc somehow so we didn't rely on someone asking about it again next cycle.16:31
ttxthe other missing ones are all trailing16:31
hberaudI was wondering why I didn't find victoria-c-a in our schedule16:31
smcginnis;)16:31
hberaudso could be worth to add it to the wallaby schedule too16:31
smcginnisNot necessarily in the schedule, but it should be in process doc to make sure we don't skip the step.16:32
hberaudat least yes16:32
smcginnisAnyone want to take that as an action to do?16:32
hberaudfire16:32
ttx(now multiplexing with another meeting, may answer slowly)16:32
smcginnis#action hberaud to add step for tagging cwi branchless (tempest) deliverables to process doc16:33
smcginnisThat's probably good enough for now.16:33
smcginnis#topic Discuss about QA release steps16:33
*** openstack changes topic to "Discuss about QA release steps (Meeting topic: releaseteam)"16:33
smcginnisI think it's useful to have at least something in our process doc, at least as a safety to remind QA.16:34
hberaudI added this topic to discuss a bit about https://wiki.openstack.org/wiki/QA/releases16:34
hberaudI agreed we should keep a track about this16:34
smcginnisAll of those tasks could probably be similified though, and just have a single note in the process stating "Remind QA team about end of cycle tasks"16:34
hberaudbut I don't think we need all these steps16:34
smcginnishberaud: Since you are updating the process doc aleardy, want to also take care of that?16:35
hberaudlet's go16:35
smcginnis#action hberaud to simplify process doc steps to just remind QA about end of cycle steps16:35
smcginnis#topic Open floor16:36
*** openstack changes topic to "Open floor (Meeting topic: releaseteam)"16:36
hberaudnothing on my end16:36
smcginnisNothing else from me.16:36
smcginnisttx is in another meeting now.16:36
ttxnothing else16:36
smcginnisAnyone else have anything for the meeting?16:36
armstrongnothing16:36
smcginnisGreat, we can wrap up then.16:37
hberaudsmcginnis: ah just one think16:37
smcginnisThanks everyone!16:37
smcginnisOk16:37
armstrongthanks16:37
hberaudI started to initialize an etherpad for wallaby, I will surely ping you soon to double check this one if you are ok with that16:37
smcginnisOh, I should quickly point out, we've been the de facto maintainers for reno. There is a bug out there that could use some attenion if anyone has some time:16:37
smcginnis#link https://storyboard.openstack.org/#!/story/200813916:37
fungibtw, the ensure-twine role should work again as of a few minutes ago, if someone has a concise list of failures i'm happy to reenqueue where possible16:38
sboyronhberaud: I'd like to understand a bit more your tasks, will it be possible to explain me more ?16:38
smcginnishberaud: Sounds good. Hopefully you've seen the script to help create that etherpad.16:38
smcginnisfungi: Awesome!16:38
hberaudsmcginnis: oh snap no...16:38
fungii can also just go through the failures ml archive if there's no list yet16:38
smcginnisfungi: The failures all happened after the tag was pushed. Are we going to need to do some manual steps?16:38
hberaudsmcginnis: I did that at manually16:38
smcginnisfungi: They are all listed in the tracking etherpad.16:39
fungismcginnis: we shouldn't, it would be reenqueuing of the tag ref16:39
fungiso specifically the things which happen after the tag has been pushed16:39
smcginnisfungi: Line 440 in the etherpad.16:39
fungithanks16:39
ttxhttps://etherpad.opendev.org/p/victoria-relmgt-tracking lines 440+16:39
hberaudsboyron: sure, I'll ping you on monday to discuss a bit about that16:39
smcginnishberaud: See bullet 4 under https://releases.openstack.org/reference/process.html#week-after-previous-release16:40
smcginnisfungi: Let us know if you need anything from us on those. Otherwise I will assume you've got the failures covered?16:40
fungiyeah, i'll report in here once they're all reenqueued16:41
fungii'll try one first just to make sure16:41
smcginnisfungi: Thanks!16:41
smcginnisOK, that was a lot of stuff after saying there wasn't anything else to talk about. :D16:41
smcginnisAnything else?16:41
* fungi refrains from doing his columbo impersonation16:42
smcginnisOnly if we had video.16:42
hberaudsmcginnis: thanks16:42
smcginnisOK, thanks everyone! Almost time to hand the reigns over to our new fearless leader. We're getting close to the end of victoria. Thank you all for a good cycle!16:43
smcginnis#endmeeting16:43
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/"16:43
openstackMeeting ended Thu Oct  1 16:43:19 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-01-16.03.html16:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-01-16.03.txt16:43
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-01-16.03.log.html16:43
hberaudsmcginnis: thanks!!!16:43
ttxsmcginnis: thanks, but you're not done yet!16:43
smcginnis:)16:43
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/cinder --ref=refs/tags/16.2.0 --newrev=ade880dcdd3b80bb90cb5b7f277dbc5983c76c3a16:44
fungithat's what i've reenqueued to confirm16:45
gmannsmcginnis: hberaud +1, I have added almost all the steps with example in qa release page, so 'QA reminder from release team' will be simple one - https://wiki.openstack.org/wiki/QA/releases16:48
hberaudgmann++16:48
sboyronhberaud: thx !16:49
openstackgerritHervé Beraud proposed openstack/releases master: Branch rpm-packaging for Victoria  https://review.opendev.org/75559316:49
* hberaud eject16:53
*** jtomasek has quit IRC16:57
fungihttps://pypi.org/project/cinder/16.2.0/17:00
fungii think we're in the clear. i'll start enqueuing the rest now17:00
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/cinder --ref=refs/tags/15.4.0 --newrev=8e8a0bc1112d897223b17b15ea02307457dde4d517:12
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/cinder --ref=refs/tags/14.3.0 --newrev=5dd35b6dedb8116323f4db6a9eb9b464bcd29c8817:13
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/watcher-tempest-plugin --ref=refs/tags/2.1.0 --newrev=4a47194b58ad9854a7097d550fca4895c81a7ebe17:14
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/zaqar-tempest-plugin --ref=refs/tags/1.1.0 --newrev=04b2a14dc2e4a3efb0917a8a9557e01e314a156017:18
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/kuryr-tempest-plugin --ref=refs/tags/0.7.0 --newrev=4fb20533e978880d595be08eb2bce1675722080a17:19
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/magnum-tempest-plugin --ref=refs/tags/1.1.0 --newrev=888ff32eb361e0bd1bcd9a082becec63843d9fc017:20
openstackgerritIury Gregory Melo Ferreira proposed openstack/releases master: Release Bifrost 8.4.0 and create stable/victoria  https://review.opendev.org/75559817:21
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/oswin-tempest-plugin --ref=refs/tags/1.1.0 --newrev=afd1906b3638a5fdb981947f11a245a79fec998517:21
fungii think that's all of them17:21
openstackgerritJulia Kreger proposed openstack/releases master: Release Bifrost 8.4.0 and create stable/victoria  https://review.opendev.org/75559817:41
*** ykarel|away has joined #openstack-release17:43
openstackgerritJulia Kreger proposed openstack/releases master: Release Bifrost 9.0.0 and create stable/victoria  https://review.opendev.org/75559817:45
smcginnisThanks fungi. I'm going to try processing one of the other templest plugins now.17:46
smcginnisI did see multiple attempts on some of the jobs in the queue right now for kuryr-tempest-plugin. I didn't catch the console output to see what happened.17:46
smcginnisHoping nothing serious17:46
fungiplease keep me updated if you see any other problems17:46
smcginnisWill do17:47
*** rosmaita has quit IRC18:00
openstackgerritMerged openstack/releases master: Release manila-tempest-plugin for victoria  https://review.opendev.org/75503218:02
openstackgerritMerged openstack/releases master: Add release notes links for Victoria release  https://review.opendev.org/75547618:08
openstackgerritMerged openstack/releases master: New bugfix release oslo.privsep for ussuri.  https://review.opendev.org/75548518:08
*** ykarel|away has quit IRC18:20
openstackgerritMerged openstack/releases master: Release ironic-inspector 10.4.0 for victoria  https://review.opendev.org/75534018:34
openstackgerritMerged openstack/releases master: Release ironic-ui 4.2.0 for Victoria  https://review.opendev.org/75536618:34
openstackgerritMerged openstack/releases master: Release IPE 2.1.1 and create stable/victoria  https://review.opendev.org/75539718:34
openstackgerritMerged openstack/releases master: Release ironic-python-agent 6.4.0 for victoria  https://review.opendev.org/75539118:39
openstackgerritMerged openstack/releases master: Release Bifrost 9.0.0 and create stable/victoria  https://review.opendev.org/75559818:39
*** rosmaita has joined #openstack-release18:47
*** iurygregory has quit IRC18:55
openstackgerritMerged openstack/releases master: Release ironic 16.0.0 for victoria  https://review.opendev.org/75539219:03
*** priteau has quit IRC19:11
openstackgerritJeremy Stanley proposed openstack/releases master: Release governance 0.7.0 for October elections  https://review.opendev.org/75563619:32
*** iurygregory has joined #openstack-release19:43
*** rosmaita has left #openstack-release19:50
smcginnisfungi: Looks like it wasn't happy with the commit sha on that ^20:05
smcginnisNot sure why yet, just pulled it up.20:05
smcginnisfungi: Oh! 0.7.0 already exists.20:06
smcginnisHmm, now how did that get there?20:07
smcginnisttx: Did it manually?20:08
fungii'll push up a revision for 0.8.0 then20:08
openstackgerritJeremy Stanley proposed openstack/releases master: Release governance 0.8.0 for October elections  https://review.opendev.org/75563620:10
openstackgerritLuigi Toscano proposed openstack/releases master: Release sahara-tests for victoria  https://review.opendev.org/75503820:18
openstackgerritMerged openstack/releases master: Release sahara-tests for victoria  https://review.opendev.org/75503820:45
openstackgerritMerged openstack/releases master: Release governance 0.8.0 for October elections  https://review.opendev.org/75563620:45
*** slaweq has quit IRC21:15
fungithanks smcginnis and hberaud for the quick turn-around!21:18
fungiapparently i already knew that 0.8.0 should be the correct version since that's what i put in the election config21:18
fungiso that was a good catch regardless21:18
smcginnisYay for automation!21:20
fungii was likely checking the actual tags in the governance repo for that21:21
*** mgoddard has quit IRC21:30
*** mgoddard has joined #openstack-release21:36
openstackgerritPrithvi Patel proposed openstack/releases master: Add examples of previous highlights  https://review.opendev.org/75566522:32
diablo_rojoGrace Hopper mentee patch ^22:33
diablo_rojosmcginnis, if you have a sec :)22:33
*** tosky has quit IRC22:45
*** tkajinam has joined #openstack-release23:00
*** redrobot has quit IRC23:59

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