frickler | I found confirmation regarding my hypotheses for duplicated release notes | 07:01 |
---|---|---|
frickler | https://docs.openstack.org/releasenotes/barbican/yoga.html vs. https://review.opendev.org/c/openstack/barbican/+/796065 , that commit was tagged as 13.0.0 | 07:02 |
frickler | so not a new issue, seems just nobody noticed it before | 07:02 |
*** amoralej|off is now known as amoralej | 07:23 | |
opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Zed https://review.opendev.org/c/openstack/releases/+/878120 | 11:21 |
opendevreview | Elod Illes proposed openstack/releases master: Add 2023.2 Bobcat deliverable files https://review.opendev.org/c/openstack/releases/+/878528 | 12:29 |
ttx | elodilles: 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 update | 12:54 |
hberaud | no idea | 12:55 |
hberaud | Last time I ran it it worked as expected | 12:56 |
hberaud | maybe another issue related to the release-id | 12:56 |
hberaud | as the branch name is past, that won't surprise me if we also require the release-id here | 12:57 |
ttx | no the error I get is the same if I call a non-existent command | 12:57 |
ttx | like I get the same exit 2 FAIL calling tox -e venv -- make-pad bobcat | 12:58 |
ttx | or any other command really | 12:58 |
hberaud | ok | 12:58 |
hberaud | weird | 12:58 |
hberaud | can you share the error in a pastbin? | 12:58 |
hberaud | maybe a track https://review.opendev.org/c/openstack/releases/+/878428 | 12:59 |
ttx | https://paste.opendev.org/show/bQXiRWRyXuhshqbh81E7/ | 13:00 |
hberaud | let me check locally | 13:01 |
hberaud | that works on my side | 13:02 |
hberaud | I've no issues and the agenda seems well generated | 13:02 |
ttx | applying 878428 fixed it | 13:03 |
hberaud | ok | 13:03 |
hberaud | good | 13:03 |
hberaud | however, I've not used 878428 | 13:03 |
hberaud | so... weird | 13:03 |
hberaud | which version of tox are you using? | 13:04 |
ttx | probably depends on your toolchain | 13:04 |
ttx | 3.13.2 | 13:04 |
hberaud | 3.28.0 | 13:04 |
*** amoralej is now known as amoralej|lunch | 13:07 | |
opendevreview | Merged openstack/releases master: Remove virtualenv pinning https://review.opendev.org/c/openstack/releases/+/878428 | 13:10 |
elodilles | hberaud ttx : i'm on a downstream meeting, but I've started to setup the etherpad o:) | 13:15 |
elodilles | also I've propsed some patches yesterday, about tox, virtualenv, things like that | 13:16 |
ttx | ++ | 13:16 |
elodilles | i think one of the patch should fix your issue ttx | 13:16 |
ttx | yes it did | 13:16 |
elodilles | cool \o/ | 13:17 |
*** amoralej|lunch is now known as amoralej | 13:47 | |
ttx | #startmeeting releaseteam | 14:00 |
opendevmeet | Meeting 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 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
opendevmeet | The meeting name has been set to 'releaseteam' | 14:00 |
hberaud | o/ | 14:00 |
ttx | Ping list: hberaud armstrong elodilles | 14:00 |
elodilles | o/ | 14:00 |
ttx | #topic Review task completion / Release postmortem | 14:01 |
ttx | We did complete all the last week tasks in time for release on March 22 | 14:01 |
ttx | The only issue was that duplication of release notes that frickler spotted? | 14:01 |
elodilles | and as far as i understand that is not a new problem, | 14:02 |
elodilles | and it does not affect many deliverables | 14:02 |
fungi | also we ran a little over time waiting for the final changes to merge | 14:02 |
ttx | all in all, not bad given the impact of playing with release names in the middle of the cycle | 14:02 |
ttx | fungi: was there a change that took too long, or just us (me) not being around to push buttons? | 14:03 |
elodilles | fungi: yes, i think it took a bit longer than at zed release | 14:03 |
fungi | and there was a release name/number ordering problem in the openstack-manuals repo which clarkb uploaded a last-minute fix to correct | 14:03 |
ttx | right | 14:03 |
elodilles | and sorry, that was my fault ^^^ :/ i did not notice at proposal time that the ordering had an issue :/ | 14:04 |
ttx | Nothing that really points to an issue on our process though? | 14:04 |
fungi | rough 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 complete | 14:04 |
fungi | so as of 13z we were at the double-check, merge the openstack-manuals change and then the releases final change | 14:05 |
elodilles | as i remember the final change merge took longer than at zed case (mentioned that above) | 14:06 |
fungi | those 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:10z | 14:06 |
fungi | probably better not to have the schedule say to wait until an hour before press release for those steps | 14:06 |
ttx | ok so maybe we need to fix that | 14:07 |
fungi | starting 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 16z | 14:07 |
ttx | ok noted | 14:08 |
elodilles | i agree with fungi, maybe we don't need to wait (or we should wait less) | 14:08 |
ttx | (under things to change) | 14:08 |
fungi | related, 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 out | 14:08 |
ttx | should we add that to the process? | 14:09 |
fungi | so instead of taking all day to update release notes for projects, they were done before the packages were even finished uploading | 14:09 |
fungi | it would be a good idea to add, tes | 14:09 |
fungi | s/tes/yes/ | 14:09 |
ttx | ok notes too | 14:09 |
elodilles | +1 | 14:09 |
ttx | noted | 14:09 |
fungi | as 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 |
ttx | alright, anything else on release postmortem? | 14:10 |
fungi | fewest issues of any release i can remember, even though we had totally new release designation schema | 14:11 |
fungi | so great work everyone! | 14:11 |
ttx | yeah, let's not change that schema again please | 14:11 |
ttx | could have bitten us more deeply | 14:11 |
elodilles | :) | 14:11 |
elodilles | thanks too everyone \o/ | 14:12 |
ttx | #topic Assign next week tasks | 14:12 |
ttx | We have a new etherpad at https://etherpad.opendev.org/p/bobcat-relmgt-tracking | 14:13 |
ttx | We need to assign R-27 tasks but also chairs for meetings until milestone-1 | 14:13 |
ttx | Also confirmig meeting skips | 14:14 |
elodilles | i'll finish the etherpad today, but feel free to fix typos, missed tasks, other things later on | 14:14 |
ttx | elodilles: can you chait next week meetings? I took the one after that | 14:15 |
ttx | chair* | 14:15 |
elodilles | ttx: yepp, i can. | 14:15 |
elodilles | ttx: 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 |
ttx | Hmm I don;t think we booked a PTG session. Let me doublecheck | 14:18 |
fungi | i don't see a track for it | 14:18 |
ttx | confirmed no | 14:18 |
fungi | i can add one if you want it | 14:18 |
ttx | We could make our usual meeting a video session | 14:18 |
ttx | there is still room on the Friday | 14:19 |
elodilles | ++ | 14:19 |
ttx | OK let's turn that meetign into a PTG session | 14:19 |
fungi | book it into folsom-FriB2 since that's where os-tc is starting the next hour | 14:19 |
ttx | good idea, I will once you add the track | 14:19 |
fungi | adding now | 14:19 |
fungi | it's added, but i see you're not in #openinfra-events | 14:20 |
fungi | os-release is the track | 14:20 |
ttx | I am | 14:20 |
elodilles | usually it was relmgt or rel-mgt? | 14:21 |
fungi | the other openstack non-projects are in there as os-tc, os-security, et cetera | 14:21 |
fungi | so as not to conflict with similar tracks other non-openstack projects might want | 14:22 |
ttx | ack | 14:22 |
ttx | so that's 4pm CET next Friday | 14:22 |
fungi | also 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 confusion | 14:23 |
ttx | elodilles: I will take the PTL email task if you take the countdown task | 14:23 |
elodilles | ttx: deal! | 14:24 |
elodilles | thanks! | 14:24 |
ttx | been a while since I last took it :) | 14:24 |
ttx | #topic Review countdown email | 14:24 |
ttx | I don;t think tehre is one? | 14:25 |
elodilles | no, we don't have directly after release :) | 14:25 |
ttx | #topic Open Discussion | 14:25 |
ttx | I wanted to raise PTG, but we already discussed that | 14:25 |
elodilles | \o/ | 14:26 |
ttx | #agreed next meeting will be done as part of PTG | 14:26 |
ttx | anything else? | 14:26 |
elodilles | nothing else from me | 14:26 |
ttx | On Bobcat etherpad, do y'all agree with the meeting skips between now and milestone-1? | 14:27 |
hberaud | nope | 14:27 |
hberaud | yeah | 14:27 |
ttx | yeah release team downtime | 14:27 |
elodilles | ++ | 14:28 |
ttx | alright, all set | 14:28 |
ttx | #endmeeting | 14:28 |
opendevmeet | Meeting ended Fri Mar 24 14:28:59 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:28 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-03-24-14.00.html | 14:28 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-03-24-14.00.txt | 14:28 |
opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-03-24-14.00.log.html | 14:28 |
hberaud | thx ttx | 14:29 |
ttx | have a great weekend! | 14:29 |
elodilles | thanks o/ | 14:29 |
elodilles | yepp, have a nice weekend o/ | 14:29 |
clarkb | ya'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 timeouts | 14:48 |
clarkb | an hour timeout is a common value and I think a couple of those jobs got close | 14:49 |
fungi | oh! right, you mentioned that on wednesday and then i totally forgot by the time we were wrapped up | 14:49 |
fungi | i 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 timeline | 14:50 |
fungi | elodilles: ttx: addition for the notes ^ | 14:50 |
clarkb | I should say got close to an hour runtime. I don't know what the timeout value(s) are | 14:50 |
fungi | we'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 deadline | 14:51 |
ttx | I'll add it to things to change/check | 14:51 |
elodilles | clarkb fungi : ack, thanks for bringing this up! | 14:56 |
elodilles | and thanks again for your help on release day! \o/ | 14:56 |
fungi | happy to help! | 15:14 |
*** amoralej is now known as amoralej|off | 16:37 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!