Wednesday, 2021-10-06

*** diablo_rojo is now known as Guest194100:58
*** ykarel|away is now known as ykarel04:18
*** ysandeep|out is now known as ysandeep05:27
opendevreviewHervĂ© Beraud proposed openstack/releases master: add missing release notes  https://review.opendev.org/c/openstack/releases/+/81263607:30
hberaudttx, elodilles o/ How are you? This cycle I would suggest to start by merging the missing release notes patch ^ . To avoid to be late on our annoucement as during wallaby. 07:32
elodilleshi hberaud , will review shortly07:34
hberaudty07:34
hberaudelodilles, ttx also please don't forget to hold all our stable branch release validations while coordinated release is underway #today.07:40
*** amoralej|off is now known as amoralej07:42
elodilleshberaud: oh, right, thanks for the reminder. actually just wanted to ask for reviews for nova stable release patches (wallaby, victoria, ussuri) from ttx o:) it is long waiting there, but maybe one more day is not a big deal07:43
hberaud:)07:44
ttxok07:45
ttxI hope it will not break your final release patch07:46
hberaudttx: I think we will have some conflict once this one will be merged 07:48
elodilleshberaud: among the release notes there are empty pages (like https://docs.openstack.org/releasenotes/automaton/xena.html ) is it still OK & required to add?07:48
hberaudelodilles: I think it's ok07:49
hberaudhowever, the files modified by the relnote patch aren't really the same than those modified by the final rc patch07:50
hberaudso, I would argue that the conflicts will be minor conflicts07:51
elodillesdo you mean that there won't be big conflicts?07:54
hberaudexact07:54
elodillesok, +2+W'd07:54
ttxwe'll soon see07:55
hberauda big part of the missing relnote pages are with python-* or oslo projects07:56
hberaudor with cwi projects07:56
opendevreviewMerged openstack/releases master: add missing release notes  https://review.opendev.org/c/openstack/releases/+/81263608:06
hberaud\o/ no conflict08:07
elodilles~o~08:13
hberaudttx: Do you know what's the exact time for the xena press release?08:14
*** ykarel is now known as ykarel|lunch08:15
*** ysandeep is now known as ysandeep|lunch08:28
ttxhberaud: yes 1500UTC08:52
hberaudack08:52
ttxso we need to finish and announce it just before that08:53
ttxbetween 1400 and 1500utc ideally08:53
hberaudack08:54
hberaudlgtm08:54
*** ykarel|lunch is now known as ykarel09:45
*** ysandeep|lunch is now known as ysandeep09:46
fungiwhat's button-pushing time for the main releases change?10:05
fungii guess that's change 81225110:07
hberaudfungi: I think we will start pushing it in ~30 minutes10:07
fungicool, i'm around in case anything breaks10:08
hberaudthanks10:08
hberauduntil now the infras (pypi/warehouse, and openstack infra (AFAIK)) seems fully functional10:13
hberaudfungi: Before we start pushing the button please can you confirm that our openstack infra is OK?10:25
fungiyeah, i've been looking over everything10:27
fungithere's a bit more of a test backlog than is common this time of day, but tripleo and osa have approved quite a bit of stuff10:28
hberaudok 10:29
hberaudThen, let's go!10:30
ttxyay!10:30
hberaudelodilles, ttx FYI ^ I start merging the final patch10:30
elodilleshberaud: \o/10:31
hberaudhere we go10:31
fungiseems like check-release-approval takes a long time to run for changes which create lots of tags10:32
fungibut that's not a problem as far as i can tell10:32
hberaudindeed10:32
fungiwe consider the final release pre-approved by the ptls et cetera10:32
hberaudhttps://zuul.opendev.org/t/openstack/builds?job_name=openstack-upload-github-mirror10:34
hberaudhttps://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-python10:34
hberaudhttps://zuul.opendev.org/t/openstack/builds?job_name=announce-release10:35
hberaudhttps://zuul.opendev.org/t/openstack/builds?job_name=propose-update-constraints10:35
fungiwe're not backlogged on executors any longer, as of a few minutes ago, but still have a bit of a node request backlog10:38
fungiand the releases change has all of its node assignments now10:39
fungizuul estimates 10 minutes until the show starts10:39
hberaudack10:39
elodillesi guess it estimates based on the 'general' job run time and for this release patch we can expect some extra time, right?10:47
fungipossibly10:48
fungiit does base its time estimates on the average completion time for a particluar job10:48
fungiit's already pretty far along though assuming it goes in alpha order (jus finished checking neutron and on to nova)10:52
hberaudsahara seems underway10:53
hberaudzaqar10:55
hberauddone10:55
elodilles81225110:55
elodillesi mean: 0 errors found10:56
hberaud\o/10:56
elodillesnow the post tasks10:56
opendevreviewMerged openstack/releases master: Xena final releases for cycle-with-rc projects  https://review.opendev.org/c/openstack/releases/+/81225110:57
fungiand now the fun begins10:58
* hberaud grab popconr10:58
hberaudcorn10:58
elodilles:]10:58
fungiit's enqueued in the release-post pipeline now10:58
*** ysandeep is now known as ysandeep|away11:00
fungitaking a while for a node to come available for tag-releases, looks like11:03
fungibut it finally got one11:03
fungiand tags are getting enqueued!11:08
fungibarbican's got a release-openstack-python build underway now11:10
fungiand i see them starting for other tags as well11:11
fungiso far, so good11:11
fungihttps://pypi.org/project/barbican/ shows 13.0.0 as current since a few minutes ago11:18
funginova tag is being created now11:18
hberaudexcellent11:20
fungiinstead of cloning nova fresh, the script could clone from the copy already cached on disk and then just fetch available refs, would speed things up and put less load on our git servers11:21
fungiall tags have been pushed, now for the long tail of waiting for all their builds complete11:25
hberaudhm we get a docker image failure with  monasca-notification11:27
hberaud(publish failure)11:27
fungirelease pipeline length peaked at 82 refs, though some had already completed their builds by the time the last ones were being enqueued11:27
ttxhberaud: link?11:27
hberaudhttps://zuul.opendev.org/t/openstack/build/2b6170b63871409a8ef296bca3883896/log/job-output.txt11:28
hberaudapparently it seems related to a non existing local image 11:29
fungi"error: can't find Rust compiler"11:29
hberaudand I seen failure related to rust compiler11:30
hberaudyes this one11:30
hberaudI suppose the both are linked11:30
fungiit's trying to build pyca/cryptography from source, yeah11:30
ttxthat job seems to have a complicated history https://zuul.opendev.org/t/openstack/builds?job_name=publish-monasca-notification-docker-image&project=openstack/monasca-notification11:31
fungilog says "/usr/local/lib/python3.6/..."11:32
hberaudonly with xena at least11:32
fungidid monasca not move their jobs to focal?11:33
hberaudU, V, W looks ok11:33
hberaudI don't know11:33
fungithough it's a focal node where that was running11:34
ttxcomparing logs from successful run vs. failed one11:34
opendevreviewBrian Rosmaita proposed openstack/releases master: Add Cinder-specific dates for Yoga schedule  https://review.opendev.org/c/openstack/releases/+/81266611:35
ttxYeah it seems to be where the fail occurs:  Building wheel for cryptography (PEP 517): finished with status 'done'11:36
ttxvs.   Building wheel for cryptography (PEP 517): finished with status 'error'11:36
fungii'm struggling to figure out how they ended up with python 3.6 on an ubuntu-focal node, its default python3 is 3.811:36
fungii suspect the underlying problem is that there's no cp36 wheel for the version of cryptography in upper-constraints.txt11:37
ttx(comparing with https://zuul.opendev.org/t/openstack/build/d44b9b892e744917b9c76f62ab6996e5 which was a successful run)11:37
ttxfungi: how do you see it's running 3.6?11:38
ttxhah /usr/local/lib/python3.6/11:38
fungii bet that's inside a container11:39
ttxfungi: the successful run also has that 3.6 line11:40
fungiyep, it's a docker build, so their base image is probably 3.611:40
fungittx: different version of cryptography?11:40
fungiyep11:42
fungifailure: Collecting cryptography===35.0.0 (from -c /app/upper-constraints.txt (line 189))11:42
fungisuccess: Collecting cryptography===3.4.8 (from -c /app/upper-constraints.txt (line 189))11:42
ttxhah11:42
hberaudweird11:42
ttxhmm some change in the underlying Docker image probably11:43
hberaudI don't think that reenqueuing it will help us11:45
fungiyeah, likely they need to update something about their monasca:base image11:47
hberaudyes I think they need to fix the root cause first11:48
ttxlooks like one of the "fs layer" is different, yielding a different sha256 digest in the end11:48
ttxthis one is in both, but below that it looks different: 7cfa6613f80e: Pulling fs layer11:48
hberaudApparently it didn't seems to disturb them previously because this error seems present since a while now11:49
fungiand we're now at the long tail of releasenotes jobs11:53
fungialso seem to be basically caught up on the node backlog11:55
*** amoralej is now known as amoralej|lunch11:55
ttxso on the monasca thing, my understanding is that it ends up installing Monasca inside some docker image that resolves cryptography to two different versions, one of which can't be built under python 3.611:58
hberaud+111:59
fungii'm curious why it's trying to build cryptography from sdist anyway, there are cp36-abi3 manylinux wheels for it12:00
ttxactually12:01
ttxhttps://opendev.org/openstack/requirements/commit/1fa22ce584ef8a5f5ec0c0e606e5e0daf38de14812:01
fungibut maybe the pip in those docker images is too old to look for abi3 wheels12:01
ttx18 hours ago we went to 35.0.012:01
hberaudah good catch12:01
fungibut on master, not stable/xena12:02
ttxthat sounds like a bad idea12:02
ttxhah12:02
fungiso monasca's using master constraints list in their stable/xena image build12:03
ttx"Cloning monasca-common in version: master"12:05
hberaudIf I take an old build (https://zuul.opendev.org/t/openstack/build/6f647ab90b3040b08683c3f640154131/log/job-output.txt) the error are differents, they don't match this current case. So the both error don't seems related. But even by fixing it I'm not sure this job will be fixed12:05
ttxat least for that ref refs/tags/5.0.0 it does consider it's master12:05
hberaudthis build ^ is older than the req update12:06
ttxhberaud: I would not consider that publication to be part of "the release", so i would defer the fix12:06
hberaud+112:06
ttxwe don;t do docker images12:06
ttxthat is an additional release job, not one of ours :)12:07
hberaudI'll simply send an email to the team to inform them12:07
ttx(it's clearly way too flaky for one of ours)12:07
ttxyep12:07
hberaudI'm not fan to spend time to repair a light during a landing step :) ( https://en.wikipedia.org/wiki/Eastern_Air_Lines_Flight_401 )12:10
hberaudElse for now all jobs seems green12:11
hberaudI think we are ready to run the check to find the missing tarballs 12:18
hberaudttx, fungi did you noticed other issues until now?12:19
ttxchecking12:21
ttxall clear for me12:22
hberaud+112:22
hberaudelodilles: I think you can start your verification12:24
fungii haven't seen any problems12:26
hberaudthanks12:26
elodilleshberaud: actually i've started 'tox -e venv -- missing-releases --series xena' more than half an hour ago and it succeded: did not find any errors12:26
fungithe release notes jobs will still be going for a while12:26
fungibut otherwise i think it's all clear12:26
elodillesthe only interesting print outs were these: https://paste.opendev.org/12:27
elodillesi mean these: https://paste.opendev.org/show/809811/12:28
elodilles(sorry, captcha tricked me :P12:28
hberaudelodilles: if I'm right the latest job finished around 11:56UTC so I think your run is ok12:28
elodilleshberaud: ack12:31
elodillesthe missing-releases command did not consider those 'missing python 3 tarballs' as errors12:33
elodillesarmstrong: fyi ^^^12:35
hberaudyes12:36
hberaudI think that we could ignore them12:36
armstrongHello elodilles12:37
elodilleshi12:37
armstrongelodilles:  are you working on the task yet?12:38
elodillesarmstrong: i've run already: 'tox -e venv -- missing-releases --series xena'12:38
armstrongok12:39
elodillesand fortunately it did not show any missing things12:39
armstronggreat!12:39
elodilles(actually I did a test run prior the final release patch merge, just to have a comparison what should I look for)12:40
elodillesbut the command gives clear output anyway12:41
armstrongelodilles:  After the release merge shall we run another test?12:41
elodillesarmstrong: I ran it after the release merge and when I saw that relevant post jobs have finished12:42
elodillesarmstrong: but feel free to run it by yourself as well as a doublecheck12:42
armstrongOh I did know that the final release is merged :) 12:43
*** ysandeep|away is now known as ysandeep12:44
elodillesif you read back the channel you'll see what happened as we were discussing the things here :)12:45
hberaudelodilles, ttx: please can you review the drafts or our next announcements https://etherpad.opendev.org/p/relmgmt-weekly-emails13:00
hberaudhttps://www.openstack.org/software/xena/ LGTM13:13
armstronghberaud: the draft LGTM13:16
elodilleshberaud: both mail looks good \o/13:16
hberaudty!13:17
*** amoralej|lunch is now known as amoralej13:17
ttxall tarballs checked out?13:23
ttxLooking into emails13:23
ttxLGTM, I just made it clear you need to adjust URL by slpashing color13:25
clarkbI've done some napkin math and I think the tag pipeline will need about 5 hours to finish clearing its queued entries. These entries appear to be publishing release notes13:26
clarkbThey are running one by one due to a semaphore and take about 5 minutes each13:26
hberaudttx: yeah all the tarballs seems there13:26
hberaudttx: thanks for the splashing color13:27
ttxThat shall not block the release but we may think about improvements there13:27
ttx(the tag pipeline backlog)13:27
hberaudI agree13:28
hberaudI propose to mark xena as released in ~ 45 minutes (by merging https://review.opendev.org/c/openstack/releases/+/812454 ), it will be 2:15pm UTC, is it ok for you?13:30
hberaudand we could send the announcements emails around 2:30pm UTC13:31
ttxhberaud: works for me13:31
ttxhttps://www.openstack.org/software/xena/ is ready13:31
hberaudyepp13:32
hberaud-p13:32
fungithe reason we ended up doing a semaphore on the release notes job is that if it gets enqueued twice for different branches of the same project, the publication rsync can collide13:34
fungiclarkb: ^ worth pondering alternative solutions to that problem i suppose13:34
fungirelease notes builds for different projects can run fine in parallel, just not for different branches of the same project13:35
clarkbfungi: my first thought on that is maybe zuul needs a semaphore that only mutexes the same project13:35
clarkbor maybe we need to configure variants that use a different semaphore per project13:35
hberaudclarkb: here is the original discussion https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-release.2020-10-07.log.html#t2020-10-07T14:42:4913:38
clarkbya I remember the issue. It isn't actually fatal but causes the jobs to fail which we don't want from a user sanity perspective13:42
opendevreviewHervĂ© Beraud proposed openstack/releases master: Mark Xena as released  https://review.opendev.org/c/openstack/releases/+/81245413:46
stephenfinCan I merge the docs changes to add Xena index pages so?14:03
hberaudstephenfin: which change?14:03
hberaudI guess yes14:03
stephenfinhttps://review.opendev.org/c/openstack/openstack-manuals/+/81212114:04
stephenfinAlso, is Train in extended maintenance now? What about Ussuri?14:04
hberaudconcerning xena will we officialize it by merging https://review.opendev.org/c/openstack/releases/+/812454 in ~10 minutes14:05
elodillesstephenfin: ussuri will transition to EM in a month14:05
elodillesstephenfin: see https://releases.openstack.org/14:05
stephenfinaight, I'll merge the two patches to mark Train as EM and release Xena so14:06
hberaudand train is already EM14:06
stephenfinbut will hold off one for Ussuri14:06
hberaudLGTM14:06
ykarelReviews please https://review.opendev.org/c/openstack/releases/+/81227514:13
ykarelelodilles, ttx ^14:13
hberaudykarel: Today is the final release for Xena. We scheduled it for 3pm UTC. We will defer this patch after the official announce.14:15
hberaudpuppet is a trailing project, it won't hurt if we merge it in awhile14:16
hberaudIt's time to go with https://review.opendev.org/c/openstack/releases/+/81245414:17
elodillesstephenfin: have you seen Andreas' comment on https://review.opendev.org/c/openstack/openstack-manuals/+/812121 ?14:17
stephenfinI have. I pulled the patch and am trying to fix the previous one now14:17
elodillesstephenfin: unfortunately it's still on gate queue14:17
stephenfinIt won't merge without the second +W14:17
stephenfin*without the +W14:18
elodillesstephenfin: ok, sorry, then never mind :X14:18
stephenfinNope, all good :) I should have it fixed shortly14:18
stephenfinAs an aside, these are the disadvantages of not having anyone else to look over patches now /o\14:19
elodilles:/14:19
hberaudfungi: FYI release announce sent at openstack-announce@list.openstack.org14:27
fungithanks!14:27
fungiaprice: ^14:27
apriceyay!! 14:28
ttxwoohoo!14:28
ykarelhberaud, okk in past it used to be merged before14:28
ykarelbut ok after announcement too14:28
fungiapproving it now14:28
hberaudykarel: not a big deal14:28
apricecongrats everyone! 14:29
hberaudCongrats everyone!14:29
fungihttp://lists.openstack.org/pipermail/openstack-announce/2021-October/002056.html14:29
hberaudWell, now it's time to send it to openstack-discuss14:31
opendevreviewMerged openstack/releases master: Mark Xena as released  https://review.opendev.org/c/openstack/releases/+/81245414:32
hberaudtwitted https://twitter.com/4383hberaud/status/144575900704659456914:33
hberaudand sent http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025214.html14:33
hberaudhttps://releases.openstack.org/ will be updated in few minutes14:35
hberaudjob is running yet14:36
*** diablo_rojo__ is now known as diablo_rojo14:39
hberaudpublish-tox-docs-releases is queued14:39
diablo_rojowhoop whoop!14:39
ttxNot for future releases, we should probably wait until releases.o.o shows the release as "released" before sending announcement14:44
ttxNote*14:44
hberaudnote14:44
diablo_rojolol14:44
hberaudyes that what I was thinking too14:45
hberaudThe mail could be queued at least but we should wait before approving it. I forgot to check this point before :\14:47
fungilooks like it's done now14:48
hberaudHm the page isn't updated14:48
fungithat volume gets released every 5 minutes14:49
hberaudok14:49
fungiso should show up in a minute assuming nothing else delays that14:49
fungiit's going now14:50
* hberaud hberaud restrein him to frantically reload the page14:50
fungiand done!14:50
hberauddrum roll => https://releases.openstack.org/14:51
hberaudAnd yes!14:51
diablo_rojoWell done everyone!14:52
hberaudThank you all for all your helps during this cycle and congrats for your works14:52
diablo_rojoThank you for leading us!14:52
hberaudMy pleasure :)14:52
hberaudThen now that announces are made and that xena is out, I'm honored to pass the PTL baton to elodilles :)14:53
hberaudHail to elodilles our fearless leader!14:53
ttxyay!14:53
johnsomThank you release team for making the Xena release nice and smooth for the Designate/Octavia teams! We appreciate the work.14:58
*** ykarel is now known as ykarel|away15:38
*** ysandeep is now known as ysandeep|out16:15
*** amoralej is now known as amoralej|off17:01
*** ysandeep|out is now known as ysandeep18:03
*** ysandeep is now known as ysandeep|out19:24
clarkbmy tag pipelien estimates appear to be a bit off. Still 20 queued entries to go (from about 58 when I first brought it up)19:37
clarkbbut it continues to make steady progress19:38

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