Friday, 2023-03-24

fricklerI found confirmation regarding my hypotheses for duplicated release notes07:01
fricklerhttps://docs.openstack.org/releasenotes/barbican/yoga.html vs. https://review.opendev.org/c/openstack/barbican/+/796065 , that commit was tagged as 13.0.007:02
fricklerso not a new issue, seems just nobody noticed it before07:02
*** amoralej|off is now known as amoralej07:23
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Zed  https://review.opendev.org/c/openstack/releases/+/87812011:21
opendevreviewElod Illes proposed openstack/releases master: Add 2023.2 Bobcat deliverable files  https://review.opendev.org/c/openstack/releases/+/87852812:29
ttxelodilles: hberaud : been trying to set up a bobcat etherpad but I get a silent error trying to run tox -e venv -- make-tracking-pad bobcat... Looks like a tox issue. It's been a while since I last ran it so I may have missed some update12:54
hberaudno idea12:55
hberaudLast time I ran it it worked as expected12:56
hberaudmaybe another issue related to the release-id12:56
hberaudas the branch name is past, that won't surprise me if we also require the release-id here12:57
ttxno the error I get is the same if I call a non-existent command12:57
ttxlike I get the same exit 2 FAIL calling tox -e venv -- make-pad bobcat12:58
ttxor any other command really12:58
hberaudok12:58
hberaudweird12:58
hberaudcan you share the error in a pastbin?12:58
hberaudmaybe a track https://review.opendev.org/c/openstack/releases/+/87842812:59
ttxhttps://paste.opendev.org/show/bQXiRWRyXuhshqbh81E7/13:00
hberaudlet me check locally13:01
hberaudthat works on my side13:02
hberaudI've no issues and the agenda seems well generated13:02
ttxapplying 878428 fixed it13:03
hberaudok13:03
hberaudgood13:03
hberaudhowever, I've not used 87842813:03
hberaudso... weird13:03
hberaudwhich version of tox are you using?13:04
ttxprobably depends on your toolchain13:04
ttx3.13.213:04
hberaud3.28.013:04
*** amoralej is now known as amoralej|lunch13:07
opendevreviewMerged openstack/releases master: Remove virtualenv pinning  https://review.opendev.org/c/openstack/releases/+/87842813:10
elodilleshberaud ttx : i'm on a downstream meeting, but I've started to setup the etherpad o:)13:15
elodillesalso I've propsed some patches yesterday, about tox, virtualenv, things like that13:16
ttx++13:16
elodillesi think one of the patch should fix your issue ttx 13:16
ttxyes it did13:16
elodillescool \o/13:17
*** amoralej|lunch is now known as amoralej13:47
ttx#startmeeting releaseteam14:00
opendevmeetMeeting started Fri Mar 24 14:00:02 2023 UTC and is due to finish in 60 minutes.  The chair is ttx. 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
hberaudo/14:00
ttxPing list: hberaud armstrong elodilles14:00
elodilleso/14:00
ttx#topic Review task completion / Release postmortem14:01
ttxWe did complete all the last week tasks in time for release on March 2214:01
ttxThe only issue was that duplication of release notes that frickler spotted?14:01
elodillesand as far as i understand that is not a new problem,14:02
elodillesand it does not affect many deliverables14:02
fungialso we ran a little over time waiting for the final changes to merge14:02
ttxall in all, not bad given the impact of playing with release names in the middle of the cycle14:02
ttxfungi: was there a change that took too long, or just us (me) not being around to push buttons?14:03
elodillesfungi: yes, i think it took a bit longer than at zed release14:03
fungiand there was a release name/number ordering problem in the openstack-manuals repo which clarkb uploaded a last-minute fix to correct14:03
ttxright14:03
elodillesand sorry, that was my fault ^^^ :/ i did not notice at proposal time that the ordering had an issue :/14:04
ttxNothing that really points to an issue on our process though?14:04
fungirough timeline is that the main releases change was approved at 11z and took an hour in the gate pipeline to validate all the new releases, then the tag-releases job started at approximately 12z and took roughly an hour to push all the tags and for the resulting tag/release pipeline jobs to complete14:04
fungiso as of 13z we were at the double-check, merge the openstack-manuals change and then the releases final change14:05
elodillesas i remember the final change merge took longer than at zed case (mentioned that above)14:06
fungithose took some time (also the schedule said not to approve them until 14z), and so the releases.o.o site didn't update until about 15:10z14:06
fungiprobably better not to have the schedule say to wait until an hour before press release for those steps14:06
ttxok so maybe we need to fix that14:07
fungistarting the whole process a little earlier would also have given us a bit more breathing room to deal with the last-minute docs site issue, but still that was corrected on the published version before 16z14:07
ttxok noted14:08
elodillesi agree with fungi, maybe we don't need to wait (or we should wait less)14:08
ttx(under things to change)14:08
fungirelated, we merged a change the day before the release to temporarily remove release publication job semaphores and then merged a revert of that once the tag pipeline cleared out14:08
ttxshould we add that to the process?14:09
fungiso instead of taking all day to update release notes for projects, they were done before the packages were even finished uploading14:09
fungiit would be a good idea to add, tes14:09
fungis/tes/yes/14:09
ttxok notes too14:09
elodilles+114:09
ttxnoted14:09
fungias for the wait-till-14z in the schedule, we did go ahead about 20 minutes early because i was worried things could run long (and they did)14:10
ttxalright, anything else on release postmortem?14:10
fungifewest issues of any release i can remember, even though we had totally new release designation schema14:11
fungiso great work everyone!14:11
ttxyeah, let's not change that schema again please14:11
ttxcould have bitten us more deeply14:11
elodilles:)14:11
elodillesthanks too everyone \o/14:12
ttx#topic Assign next week tasks14:12
ttxWe have a new etherpad at https://etherpad.opendev.org/p/bobcat-relmgt-tracking14:13
ttxWe need to assign R-27 tasks but also chairs for meetings until milestone-114:13
ttxAlso confirmig meeting skips14:14
elodillesi'll finish the etherpad today, but feel free to fix typos, missed tasks, other things later on14:14
ttxelodilles: can you chait next week meetings? I took the one after that14:15
ttxchair*14:15
elodillesttx: yepp, i can.14:15
elodillesttx: though, do we have a PTG session?14:15
elodilles(let's not mark the etherpad as 'done' as it still needs updates & reviews afterwards o:))14:16
ttxHmm I don;t think we booked a PTG session. Let me doublecheck14:18
fungii don't see a track for it14:18
ttxconfirmed no14:18
fungii can add one if you want it14:18
ttxWe could make our usual meeting a video session14:18
ttxthere is still room on the Friday14:19
elodilles++14:19
ttxOK let's turn that meetign into a PTG session14:19
fungibook it into folsom-FriB2 since that's where os-tc is starting the next hour14:19
ttxgood idea, I will once you add the track14:19
fungiadding now14:19
fungiit's added, but i see you're not in #openinfra-events14:20
fungios-release is the track14:20
ttxI am14:20
elodillesusually it was relmgt or rel-mgt?14:21
fungithe other openstack non-projects are in there as os-tc, os-security, et cetera14:21
fungiso as not to conflict with similar tracks other non-openstack projects might want14:22
ttxack14:22
ttxso that's 4pm CET next Friday14:22
fungialso i guess ttx was in the channel via a bridge, because irc wasn't showing him in there and then he suddenly joined when he sent something to the channel, hence my confusion14:23
ttxelodilles: I will take the PTL email task if you take the countdown task14:23
elodillesttx: deal!14:24
elodillesthanks!14:24
ttxbeen a while since I last took it :)14:24
ttx#topic Review countdown email14:24
ttxI don;t think tehre is one?14:25
elodillesno, we don't have directly after release :)14:25
ttx#topic Open Discussion14:25
ttxI wanted to raise PTG, but we already discussed that14:25
elodilles\o/14:26
ttx#agreed next meeting will be done as part of PTG14:26
ttxanything else?14:26
elodillesnothing else from me14:26
ttxOn Bobcat etherpad, do y'all agree with the meeting skips between now and milestone-1?14:27
hberaudnope14:27
hberaudyeah14:27
ttxyeah release team downtime14:27
elodilles++14:28
ttxalright, all set14:28
ttx#endmeeting14:28
opendevmeetMeeting ended Fri Mar 24 14:28:59 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:28
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-03-24-14.00.html14:28
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-03-24-14.00.txt14:28
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-03-24-14.00.log.html14:28
hberaudthx ttx 14:29
ttxhave a great weekend!14:29
elodillesthanks o/14:29
elodillesyepp, have a nice weekend o/14:29
clarkbya'll are done before I'm at the keyboard :) I was going to mention that you should double check the runtimes of those release jobs against their timeouts14:48
clarkban hour timeout is a common value and I think a couple of those jobs got close14:49
fungioh! right, you mentioned that on wednesday and then i totally forgot by the time we were wrapped up14:49
fungii agree it would be quite unfortunate if one of the jobs hit a timeout in the middle of trying to do a coordinated release, would almost certainly blow our timeline14:50
fungielodilles: ttx: addition for the notes ^14:50
clarkbI should say got close to an hour runtime. I don't know what the timeout value(s) are14:50
fungiwe'd be able to recover from the timeout fairly easily since the jobs are idempotent, but rerunning things would probably push us well past our deadline14:51
ttxI'll add it to things to change/check14:51
elodillesclarkb fungi : ack, thanks for bringing this up!14:56
elodillesand thanks again for your help on release day! \o/14:56
fungihappy to help!15:14
*** amoralej is now known as amoralej|off16:37

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