Thursday, 2021-02-11

*** tosky has quit IRC00:17
*** ianychoi has joined #openstack-release02:09
*** armax has joined #openstack-release04:25
*** armax has quit IRC04:26
*** ykarel|away has joined #openstack-release04:40
*** ykarel|away is now known as ykarel04:41
ykarelReview please puppet-nova release for train/ussuri:- https://review.opendev.org/c/openstack/releases/+/77487605:00
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** whoami-rajat__ has joined #openstack-release06:03
*** vishalmanchanda has joined #openstack-release06:22
*** diablo_rojo has quit IRC06:55
*** sboyron_ has joined #openstack-release07:10
*** eolivare has joined #openstack-release07:39
*** slaweq has joined #openstack-release07:44
*** ykarel has quit IRC07:44
*** ykarel has joined #openstack-release07:46
*** rpittau|afk is now known as rpittau07:53
openstackgerritTobias Urdin proposed openstack/releases master: Release magnum-ui 5.4.0 for Train  https://review.opendev.org/c/openstack/releases/+/77507808:17
*** jbadiapa has joined #openstack-release08:26
*** ianychoi has quit IRC08:33
*** tosky has joined #openstack-release08:36
*** ianychoi has joined #openstack-release08:48
*** hberaud has quit IRC08:58
*** hberaud has joined #openstack-release08:58
*** ykarel is now known as ykarel|lunch09:33
*** dtantsur|afk is now known as dtantsur10:00
*** jbadiapa has quit IRC10:04
*** ykarel|lunch is now known as ykarel10:36
*** jbadiapa has joined #openstack-release10:49
ykarelhberaud, review please https://review.opendev.org/c/openstack/releases/+/77487610:50
hberaudykarel: done11:00
ykarelhberaud, Thanks11:01
openstackgerritMerged openstack/releases master: release new version of vitrage/vitrage-dashboard  https://review.opendev.org/c/openstack/releases/+/77478311:20
openstackgerritMerged openstack/releases master: Release oslo.metrics 0.2.1  https://review.opendev.org/c/openstack/releases/+/77475111:21
openstackgerritMerged openstack/releases master: Create new release of puppet-nova for ussuri and train  https://review.opendev.org/c/openstack/releases/+/77487611:21
openstackgerritDmitry Tantsur proposed openstack/releases master: Release metalsmith 1.2.1 for Victoria  https://review.opendev.org/c/openstack/releases/+/77512812:00
openstackgerritDmitry Tantsur proposed openstack/releases master: Release metalsmith 1.4.1 for Wallaby  https://review.opendev.org/c/openstack/releases/+/77513112:01
openstackgerritIury Gregory Melo Ferreira proposed openstack/releases master: Release bifrost bugfix/10.1.0 for wallaby  https://review.opendev.org/c/openstack/releases/+/77515013:08
*** e0ne has joined #openstack-release13:09
*** nweinber has joined #openstack-release13:38
*** stand has quit IRC13:54
*** vishalmanchanda has quit IRC14:14
*** armstrong has joined #openstack-release14:21
*** ykarel_ has joined #openstack-release14:26
*** ykarel has quit IRC14:29
openstackgerritDaniel Bengtsson proposed openstack/releases master: New bugfix and feature releases for oslo.  https://review.opendev.org/c/openstack/releases/+/77516114:30
*** ykarel_ has quit IRC14:49
openstackgerritDmitry Tantsur proposed openstack/releases master: Release ironic for stable/train  https://review.opendev.org/c/openstack/releases/+/77304914:53
*** diablo_rojo has joined #openstack-release14:56
openstackgerritHervĂ© Beraud proposed openstack/releases master: Move placement under the nova team  https://review.opendev.org/c/openstack/releases/+/77518215:05
openstackgerritDaniel Bengtsson proposed openstack/releases master: New bugfix and feature releases for oslo.  https://review.opendev.org/c/openstack/releases/+/77516115:07
*** ricolin has joined #openstack-release15:08
*** e0ne has quit IRC15:11
openstackgerritMerged openstack/releases master: Release metalsmith 1.4.1 for Wallaby  https://review.opendev.org/c/openstack/releases/+/77513115:33
-openstackstatus- NOTICE: Recent POST_FAILURE results from Zuul for builds started prior to 15:47 UTC were due to network connectivity issues reaching one of our log storage providers, and can be safely rechecked15:51
*** ricolin has quit IRC15:56
hberaudFYI we experience the same issue => http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020428.html15:56
openstackgerritMerged openstack/releases master: Add Extra ATC during R-7  https://review.opendev.org/c/openstack/releases/+/77499915:58
hberaudI think we should start to hold approval15:58
hberaudat least for a awhile. I just see => http://lists.openstack.org/pipermail/release-job-failures/2021-February/001513.html15:59
hberaudelod, smcginnis, ttx ^15:59
hberaudWe can't get the logs16:00
hberaudSo it's not possible to know if this is a legit error or just a side effect of http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020428.html16:01
elodhberaud: ack. btw, the openstackstatus above ^^^ might suggest it's over16:01
hberaudelod: yes probably16:02
elodanyway, it doesn't hurt to wait a bit :)16:03
hberaudhowever the fail ^ was after the openstackstatus16:03
hberaudI can't check the logs so I can't get precise timestamp16:04
hberaudThe mail was send at 15:53:02 UTC16:05
hberaudand the openstackstatus at 15:51:55 UTC16:05
hberaudBut maybe the job was already running before 15:5116:06
ttxyes we'll likely need to reenqueue the commit ref to retrigger post jobs /cc fungi16:24
fungiif they were caught up in the ovh dallas network problem, then they failed at the point where the build logs were being uploaded, so whatever the job itself was supposed to do it probably still did... but if there were jobs depending on that job succeeding they were likely skipped16:30
fungihberaud: the failure being after the time in the status announcement is expected if the build was enqueued before that time16:31
fungithe log upload location is decided when the build is enqueued, since it's part of thebase job16:32
fungithe base job16:32
hberaudack16:33
hberaudThe failure is related to the metalsmith patch (https://review.opendev.org/c/openstack/releases/+/775131) https://opendev.org/openstack/releases/commit/5dfeec7fe5764e01d3880c285cf0265fe2209328 https://zuul.opendev.org/t/openstack/builds?job_name=tag-releases16:42
hberaudEverything seems to have been successfully created, the tag (https://opendev.org/openstack/metalsmith/src/tag/1.4.1) and the pypi upload too (https://pypi.org/project/metalsmith/1.4.1/)16:42
hberaudHowever the docs job have been skipped16:43
hberaudfungi: Can we reenqueue for the doc part? the `tag-releases` will be ignored as already exist, isn't?16:45
clarkbhberaud: if the docs jobs run for regular merges ( I think they do for many projects) you can just land an update to the docs too16:49
clarkband I think the way the jobs are setup will produce the tagged docs too (but its been a long time since I looked at the inner workings there)16:49
hberaudclarkb: I see16:50
fungihttps://zuul.opendev.org/t/openstack/buildset/484d2f5e7b03413188b0b2b478f5e4e616:50
fungithat was the buildset16:50
fungiso the skipped docs job was for openstack/releases in the release-post pipeline16:51
fungipresumably the next time publish-tox-docs-releases runs it'll be caught up?16:51
ttxif the release is up on PyPI we can assume everything is good16:51
ttxyeah16:52
hberaudI think that yes16:52
*** ricolin has joined #openstack-release16:56
hberaud#startmeeting releaseteam17:00
openstackMeeting started Thu Feb 11 17:00:05 2021 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
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 https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda17:00
hberaudPing list: ttx armstrong elod, damani17:00
ttxo/17:00
armstrongo/17:00
elodo/17:00
hberaudWe're way down on line 324 now.17:00
hberaudWill just wait a couple minutes for folks.17:00
damanihi17:00
*** bdodd has quit IRC17: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 intermediary-released service deliverables that have not done a release in this cycle yet. => Done17:03
hberaudOnly swift met the conditions => https://review.opendev.org/c/openstack/releases/+/77468217:03
hberaudAnd vitrage-dashboard but they proposed new releases so I think we can abandon => https://review.opendev.org/c/openstack/releases/+/77468317:04
hberaudThanks armstrong17:04
ttxI'd say it's unlikely that they will change (swift)17:04
ttxsince they have always been in the release-as-needed model17:04
hberaudNo idea, I'll see that after the countdown email that will speak about17:05
hberaudLet's wait a bit about for feedback from them17:05
hberaudNext task17:05
hberaudStart a ML thread about recent release failures with tripleo deliverables on ussuri => Done thanks ttx17:06
hberaudHowever you said that we need to reenqueue os-collect-config 11.0.2 and tripleo-ipsec 9.3.1 (or release 11.0.3 and 9.3.2 on stable/ussuri)17:06
*** ricolin has quit IRC17:06
hberaudright?17:06
hberaudDo you want to handle that point?17:06
ttxI'll leave choice to fungi17:07
ttx(between reenqueuing and rereleasing)17:07
hberaudok17:08
ttxnot sure how easy it is to get those refs17:08
hberaudI would argue that releasing 11.0.3 and 9.3.2 is more straightforward17:09
ttxwell, we can do it, but that means 11.0.2 and 9.3.1 are nowhere to be found17:09
hberaudExact17:10
ttxso it's suboptimal compared to reenqueuing17:10
hberaudYes17:10
hberaudWell I added this point to the next week tasks I think we can continue for now. Let's wait a bit for fungi's feedback17:11
hberaudWe'll update the task accordingly17:11
fungiyep, sorry, also on a conference call, catching up17:12
hberaudnp17:12
fungiwhat was the failure condition?17:12
fungitags got pushed but pypi uploads didn't happen?17:13
hberaudGood question, I don't really remember17:13
ttxTag was not pushed17:13
ttxtag-release job failed before that17:13
ttxThat's the post job that runs on a openstack/releases merge17:14
hberaudI wonder why I can't retrieve the point on our previous agenda17:14
fungi#link http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020112.html17:14
fungithat's a message i had saved to look into, but have been swamped17:14
ttxSo I'd say the ref that needs reenqueing in that commit on openstack/releases17:14
ttxwhich should retrigger the post jobs17:15
hberaudIIRC It was due to a lack of stable branches17:15
ttxyeah we did fix the stable branch situation, but of course that did not retrigger those post jobs17:16
hberaudYes exact17:16
hberaudSo I think that reenqueuing could work now17:16
fungiwilling to give that a shot17:17
hberaudThanks17:17
fungiso reenqueue those two openstack/releases changes into the release-post pipeline?17:17
hberaudHm yes17:17
fungishould be able to do that once this call ends17:18
hberaudWorth trying17:18
hberaudI think we can continue, anything else about this point?17:20
ttxnope17:20
hberaudI leave the next week task to be sure to not forget that17:21
hberaud#topic Socialize `test-release-openstack` nodeset switch to focal17:21
*** openstack changes topic to "Socialize `test-release-openstack` nodeset switch to focal (Meeting topic: releaseteam)"17:21
hberaudJust a heads up about a recent change merged yesterday and related to our `test-release-openstack`17:22
hberaudnodeset have been switched to focal17:22
ttxwhat is the expected impact?17:22
fungia number of the release jobs themselves are already using an ubuntu-focal nodeset anyway, right?17:23
hberaudI don't expect issue as all our jobs are already on focal, but worth to mention it during the meeting17:23
hberaudYes17:23
hberaudAFAIK it was the last one on bionic17:23
hberaudhttps://opendev.org/openstack/project-config/commit/3310a349a4ecf8187f242b9a8fe7d62465f3e08317:23
fungiyeah, it's just that opendev is behind on scheduling a default nodeset switch from ubuntu-bionic to ubuntu-focal17:24
fungii want to start pushing on that in the next week17:24
hberaudnp17:24
fungifocal's already almost a year old, we should have done it sooner17:24
fungibut setting it explicitly in jobs now is a good way to find out whether they'll break too17:24
hberaudYes17:25
hberaudSo if you observe strange behavior then remember that topic17:25
hberaudI think that's all for this point17:26
hberaud#topic Onboarding Elod17:27
*** openstack changes topic to "Onboarding Elod (Meeting topic: releaseteam)"17:27
hberaudelod: thing promised thing due https://giphy.com/gifs/mlb-alds-2018-3Mb5hvWOLe8hq6gZHc17:27
armstrongOnboarding going on here?17:27
hberaudWelcome on board elod17:27
elod:D17:27
armstrongoh hahaha17:28
hberaudNow I need to figure it how to give you the ACLs :)17:29
elodthx :) I'll work on doing useful reviews :)17:29
hberaudttx: any idea ^17:29
ttxhttps://review.opendev.org/admin/groups/5c75219bf2ace95cdea009c82df26ca199e04d59,members17:30
ttxI guess we can do a bit of cleanup too17:30
hberaudYes17:30
hberaudThanks for the link17:30
ttxremoving inactive members... although I'd keep Doug around since he still does reno reviews17:31
hberaudElod you are now in the list let me know if that work for you => https://review.opendev.org/admin/groups/5c75219bf2ace95cdea009c82df26ca199e04d59,members17:31
ttxok that should work17:31
hberaudevrardjp had officialized is departure during last cycle17:32
elodhberaud: i have the +2, so it works \o/17:32
hberaud\o/17:32
hberaudI updated Jean Philippe17:33
hberaudttx: any idea about Kendall?17:33
hberaudAFAIK she is more or less still active17:34
ttxShe has been focusing on her TC vice-chair role17:34
ttxI'd ask her if she plans to take up core reviews again in the future, or if we can downgrade her to mere +117:35
hberaudack17:35
hberaudThen for now I think we are ok with the cleanup17:36
hberaudWFY?17:36
ttxyes17:37
hberaudOk move on17:37
hberaud#topic Review countdown email contents17:37
*** openstack changes topic to "Review countdown email contents (Meeting topic: releaseteam)"17:37
hberaudhttps://etherpad.opendev.org/p/relmgmt-weekly-emails17:37
hberaudI didn't speak about vitra-dashboard as they already gave us a response about cycle-with-rc17:38
ttxhmm, that sounds a bit aggressive17:38
ttx" In absence of answer by the end of R-10 week we'll consider17:38
ttxthat the switch to cycle-with-rc is preferable.17:38
ttx"17:38
ttxI'm not sure we can make that switch without any team feedback17:39
hberaudOk so we need to upgrade our doc17:39
hberaudtoo17:39
ttxLet me try to make it a bit sweeter17:39
hberaudFeel free17:39
ttxok taht sounds a bit less definitive17:43
hberaudDefinitelly17:43
ttxOtherwise looks good17:43
hberaudI'll propose a patch for your doc to reflect that17:43
ttxmaybe we could say that we'll approve the Xena release schedule by DATE?17:43
*** rpittau is now known as rpittau|afk17:43
hberaudYes17:44
hberaudDeadline is next week, exact?17:44
hberaud"Make sure the next development series name has been added to the data/series_status.yaml file."17:44
hberaudLooks like yes17:45
*** dtantsur is now known as dtantsur|afk17:45
hberaudYeah I agree we don't need to speak about 24w17:45
ttxok done17:46
hberaudAwesome, I'll send it tomorrow17:46
hberaud#topic Assign R-8 tasks17:46
*** openstack changes topic to "Assign R-8 tasks (Meeting topic: releaseteam)"17:46
hberauddone17:47
hberaudeverything is already assigned17:47
hberaud#topic Open floor17:47
*** openstack changes topic to "Open floor (Meeting topic: releaseteam)"17:47
hberaudAnything else to discuss today?17:47
ttxno17:47
elodnothing from me either17:48
armstrongnothing17:48
hberaudOK, thanks everyone. Almost there!17:49
ttxThanks hberaud !17:49
hberaud#endmeeting17:50
*** 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/"17:50
openstackMeeting ended Thu Feb 11 17:50:01 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:50
elodthanks o/17:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-02-11-17.00.html17:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-02-11-17.00.txt17:50
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-02-11-17.00.log.html17:50
*** bdodd has joined #openstack-release17:54
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/os-collect-config --ref=refs/tags/11.0.2 --newrev=4bd71a59bd1b7a36f868bb3203f81caab4d9cf8117:58
fungisudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/tripleo-ipsec --ref=refs/tags/9.3.1 --newrev=9bb150229efa276472fc986399240bb0186003dd17:58
fungii've done those ^ just now17:58
hberaudawesome18:01
hberaudfungi: thanks18:02
fungiany time18:02
hberaudfungi: both failed18:17
fungii'll have to have a look after my current meeting wraps up18:19
*** eolivare has quit IRC18:19
hberaudOk thanks18:19
clarkbI can try to ehlp too if you have links18:28
hberaudclarkb: our issue is the both failing jobs there => https://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-python18:46
hberaudOur original issue was that the ussuri branches doesn't existed yet for the both project however we fixed that few days ago (https://review.opendev.org/c/openstack/releases/+/772995) and we reenqueued the failing jobs18:47
hberaudI can see that the branches are now there18:47
hberaudhttps://zuul.opendev.org/t/openstack/build/63f7d32d42c74d5f8b7484d48e42541e/log/job-output.txt#20018:48
hberaudsorry => https://zuul.opendev.org/t/openstack/build/63f7d32d42c74d5f8b7484d48e42541e/log/job-output.txt#20118:48
clarkbthey both have the same issue: pbr is asserting a much larger version number is necessary based on its semantic versioning requierments18:48
hberaudyes18:49
clarkb(and consequently is refusing to build for the lower version number)18:49
hberaudWe was thinking that it was due to the missing branches18:49
clarkbthat is caused by annotations in commit messges saying there are breaking changes18:49
fungiError parsing /home/zuul/src/opendev.org/openstack/tripleo-ipsec/setup.cfg: ValueError: git history requires a target version of pbr.version.SemanticVersion(11.0.0), but target version is pbr.version.SemanticVersion(9.3.1)18:49
fungiyeah, just saw that myself too18:49
clarkbshould be able to confirm that by looking at the git log between HEAD and previous release and then simply county up the version breaks18:50
hberaudSorry I need to eject for today, ttyt18:52
* hberaud afk18:52
clarkbos-collect-config HEAD is tagged 13.0.018:53
fungithe current tip of stable/ussuri for openstack/tripleo-ipsec is tagged as 9.3.1, 10.0.0, and 11.0.0 and is also identical to stable/victoria and master18:53
clarkbso pbr won't let you release 11.0.2 from that point18:53
clarkbthe 13.0.0 tag asserts breaking changes between it and 11.0.1 and so you cannot tag 11.0.2 there and respect semantic versioning18:54
clarkbI want to say you can turn off semantic versioning in pbr? but maybe I am wrong18:54
fungiwhich can probably only be done in the setup.cfg? which means a new commit, which won't be covered by those tags...18:58
clarkbyes likely18:58
clarkbhrm I'm not finding a way to turn it off in a quick grep of pbr18:59
clarkbnaively this relaese already exists and is published here: https://pypi.org/project/os-collect-config/13.0.0/ do we need an 11.0.2?19:01
clarkb(basically pbr has encoded the answer to my question as "no do not do that")19:01
*** sboyron_ has quit IRC19:18
fungiyeah, these were in an unfortunate situation where they got their stable releases tagged on master because they never got around to branching for one or two releases in a row, was that basically it?19:21
*** bdodd has quit IRC19:29
* hberaud back20:07
hberaudyes that's it20:09
clarkbit seems that 11.0.2 is still trying to be tagged on master though20:10
clarkbI think it would work if it was tagged on ussuri and 13.0.0 and 12.0.0 were not in history20:10
hberaudso even if we propose 11.0.3 and 9.3.2 it won't help us, isn't?20:10
clarkbas long as the newer tags are in the history of those tags then that is correct20:10
hberaudwhere are new bum 11.0.3 & 9.3.220:11
clarkbthe problem is semver says you cannot have 13.0.0 and 11.0.2/11.0.3 on the same commit20:11
hberaudok I got20:11
hberaudit20:11
clarkb(and 13.0.0 can't come before 11.0.2 either)20:11
hberaudmake sense20:12
clarkbit might make sense to check for these rules being violated before tagging things in CI20:12
clarkbI expect this could be done by making the tag as proposed then attempting to build an sdist of it20:13
hberaudlocally20:13
clarkbor in pre merge ci for the tag proposal20:13
fungiyeah, so to restate, the error is effectively because we're trying to add a tag to a branch which is older than another tag already on that branch/in that branch's history?21:15
*** nweinber has quit IRC21:53
*** jbadiapa has quit IRC22:03
clarkbfungi: the position on the branch of the tags matters too but yes22:06
fungier, right, we're basically trying to add out-of-order tags in a branch history22:09
*** gmann is now known as gmann_afk22:10
*** abelur has quit IRC22:41
*** abelur has joined #openstack-release22:41
*** armstrong has quit IRC22:50
*** slaweq has quit IRC23:09
*** gmann_afk is now known as gmann23:11
*** whoami-rajat__ has quit IRC23:43

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