Thursday, 2019-03-14

*** ricolin has joined #openstack-release00:57
*** mriedem_afk has quit IRC01:11
*** ricolin has quit IRC01:33
*** whoami-rajat has joined #openstack-release02:02
*** hongbin has joined #openstack-release02:15
*** ricolin has joined #openstack-release02:23
*** ricolin has quit IRC02:33
openstackgerritMohammed Naser proposed openstack/releases master: governance: release 0.4.0  https://review.openstack.org/64322002:40
openstackgerritHongbin Lu proposed openstack/releases master: Release zun-ui 3.0.0  https://review.openstack.org/64191402:46
*** dave-mccowan has joined #openstack-release02:49
*** armstrong has joined #openstack-release02:50
*** armstrong has left #openstack-release02:51
*** armstrong has quit IRC02:51
*** dave-mccowan has quit IRC02:54
openstackgerritHongbin Lu proposed openstack/releases master: Release zun-tempest-plugin 3.0.0  https://review.openstack.org/64322303:00
*** ykarel|away has joined #openstack-release03:04
*** ykarel|away has quit IRC03:22
*** hongbin has quit IRC03:36
*** diablo_rojo has quit IRC03:47
*** ricolin has joined #openstack-release04:02
*** udesale has joined #openstack-release04:22
*** ykarel|away has joined #openstack-release04:24
*** ykarel|away is now known as ykarel04:24
*** lbragstad has quit IRC05:00
*** armax has quit IRC05:35
*** jtomasek has joined #openstack-release06:15
*** witek has joined #openstack-release06:43
*** shardy has quit IRC06:44
*** witek has quit IRC06:47
*** shardy has joined #openstack-release06:52
*** tosky has joined #openstack-release07:23
*** nhbinh_ has quit IRC07:24
*** nhbinh_ has joined #openstack-release07:24
*** witek has joined #openstack-release07:30
*** ifat_afek has joined #openstack-release07:44
*** e0ne has joined #openstack-release07:45
*** tesseract has joined #openstack-release08:07
*** pcaruana has joined #openstack-release08:07
*** hberaud|gone is now known as hberaud08:09
*** pcaruana has quit IRC08:11
*** pcaruana has joined #openstack-release08:23
*** witek has quit IRC08:33
*** dtantsur|afk is now known as dtantsur08:59
*** ykarel is now known as ykarel|lunch09:09
*** jpich has joined #openstack-release09:24
dtantsurmorning folks! what's the current position of releasing anything that already got stable/stein?09:27
dtantsurhttps://github.com/openstack/rsd-lib/commit/e3a061f4d2bf70e3a2f9411f810d328c065658f1 has just been raised to my attention09:27
dtantsurit makes rsd-lib incompatible with the stein sushy, and I'd like to resolve it by issuing a new release09:28
dtantsurttx: morning, maybe you're around ^^09:28
openstackgerritDmitry Tantsur proposed openstack/releases master: Release sushy 1.8.1 for Stein  https://review.openstack.org/64325809:33
dtantsurthe request in question ^^^09:34
*** ifat_afek has quit IRC09:41
*** e0ne has quit IRC09:43
*** e0ne has joined #openstack-release09:46
*** pcaruana has quit IRC09:48
ttxdtantsur: looking09:52
*** ykarel|lunch has quit IRC09:52
ttxBug fix releases should be fine09:53
ttx+2ed, waiting for another reviewer to approve09:55
*** ykarel has joined #openstack-release09:57
dtantsurthanks!10:01
openstackgerritMerged openstack/releases master: governance: release 0.4.0  https://review.openstack.org/64322010:21
openstackgerritMerged openstack/releases master: Release openstackdocstheme 1.29.2  https://review.openstack.org/64290810:21
openstackgerritMerged openstack/releases master: Release Puppet OpenStack Stein 3  https://review.openstack.org/64247710:24
openstackgerritMerged openstack/releases master: Release solum-dashboard 2.6.0  https://review.openstack.org/64266510:24
openstackgerritMerged openstack/releases master: Release solum-tempest-plugin 1.0.0  https://review.openstack.org/64266610:24
openstackgerritMerged openstack/releases master: Release murano-tempest-plugin 1.0.0  https://review.openstack.org/64266910:27
*** nhbinh_ has quit IRC10:27
openstackgerritMerged openstack/releases master: TripleO stein-3 release  https://review.openstack.org/64247510:28
openstackgerritMerged openstack/releases master: Release murano-agent 3.6.0  https://review.openstack.org/64267010:28
*** luizbag has joined #openstack-release10:30
openstackgerritMerged openstack/releases master: Add stein cycle highlights for ironic  https://review.openstack.org/64282410:30
openstackgerritMerged openstack/releases master: TripleO: minor release for rocky  https://review.openstack.org/63785810:32
openstackgerritThierry Carrez proposed openstack/releases master: Create stable/stein branches for all libraries  https://review.openstack.org/64326810:34
ttxhmm a bunch pf release fails10:47
*** udesale has quit IRC10:56
*** udesale has joined #openstack-release10:56
*** jpich has quit IRC11:01
*** jpich has joined #openstack-release11:02
*** binh_ has joined #openstack-release11:03
ttxWe should hold on future releases until that is resolved: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003827.html11:04
*** shardy has quit IRC11:11
*** smrcascao has joined #openstack-release11:12
*** udesale has quit IRC11:15
*** udesale has joined #openstack-release11:15
*** zbr has quit IRC11:16
ttxI posted analysis for all issues on openstack-discuss. I suspect most are linked to a bionic switch /cc: fungi11:17
* ttx lunches11:17
*** udesale has quit IRC11:27
*** udesale has joined #openstack-release11:28
*** pcaruana has joined #openstack-release11:32
*** smrcascao has quit IRC11:40
*** dave-mccowan has joined #openstack-release11:44
EmilienMttx: hey, not sure what to do yet with the tripleo-ui issue11:53
EmilienMjaosorior: ^ fyi [Release-job-failures] Release of openstack/tripleo-ui failed11:54
jaosoriorEmilienM: should we poke folks from the ui team?11:54
ttxEmilienM: it's probably an issue in the job definition that makes it reliant on -xenial hosts11:54
ttxso on our side, not yours11:54
ttxEmilienM: I'll let you know if we need your help :)11:55
EmilienMjaosorior: they have no clue anyway11:55
EmilienMttx: ok, please ping me or Alex or Juan11:56
EmilienMjaosorior: I think we should retire tripleo-ui soon11:57
EmilienMjaosorior: the time we spend on releasing it isn't worth it11:57
EmilienMttx: fyi tripleo-ui is retired in our downstream product11:57
EmilienMmainteners re-shifted focus and we also lack of users11:58
*** zbr has joined #openstack-release11:59
ttxok12:13
ttxmight explain why the job is stale12:13
*** ifat_afek has joined #openstack-release12:14
jaosoriorEmilienM: ack. now we gotta consider if we retire it now, or for the next release.12:17
EmilienMhonestly I would do it now12:24
EmilienMjrist: ^ ?12:24
jristreading back12:25
jristlol EmilienM it's true12:26
jristtripleo-ui is retired from 1412:26
EmilienMtranslation: rocky12:26
jristso yeah... I think we're fine retiring now12:26
EmilienMjrist: and who is doing it?12:26
jristit was on Beth's plate12:27
EmilienMit would be great if you folks do it, it's your project ;-)12:27
jristI can submit some patches if needed12:27
EmilienMjrist: https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project12:27
openstackgerritTom Barron proposed openstack/releases master: Added Stein ycle-highlights for manila  https://review.openstack.org/64331112:28
jristEmilienM: I'll push some patches today for that12:28
EmilienMgood12:28
jristI'm not core tho :) will need some eyes12:28
*** e0ne has quit IRC12:31
*** hberaud is now known as hberaud|lunch12:33
openstackgerritTom Barron proposed openstack/releases master: Added Stein cycle-highlights for manila  https://review.openstack.org/64331112:43
openstackgerritDoug Hellmann proposed openstack/releases master: look at teams in the branch being scanned  https://review.openstack.org/64331712:45
openstackgerritMerged openstack/releases master: Put the lists under a directory  https://review.openstack.org/64286412:53
*** mriedem has joined #openstack-release13:08
fungithanks ttx, i'll see what jumps out at me but if it's a ui project then my first guess is npm13:13
ttxfungi: there are three separate issues, including one with shred. See my emails to list when you get a second :)13:14
fungion it13:14
*** smrcascao has joined #openstack-release13:15
ttxWhile I like to blame NPM for everything from Brexit to Trump, the tripleo-ui project fail is due to Ansible task failing with "hostvars['ubuntu-xenial']" is undefined -- so I'm not sure we can blame it on NPM13:15
fungiokay, so looks like the gnupg shred issue is that we try to `shred -u ~/.gnupg/*` and starting in bionic some files in that tree got moved to a subdir. i'll patch that to use find instead i guess13:24
ttxshred really needs a -r13:24
fungiyeah, that'd be nice13:25
*** lbragstad has joined #openstack-release13:26
ttxbut then shred is not very efficient on journalled filesystems anyway13:26
*** hberaud|lunch is now known as hberaud13:30
*** e0ne has joined #openstack-release13:32
fungiit's true, more of a belt-and-suspenders approach13:32
fungianyway, https://review.openstack.org/643328 should be the fix for that13:32
ttxlgtm13:36
fungii have doubts the rsync one is related to the ubuntu bionic switch13:40
fungithis looks like the executor trying to rsync files off the job node and getting surprised by a new ssh host key, which if it were related to ubuntu-bionic it would be impacting loooooots of jobs. more often when we see that behavior it's because of a rogue vm in the provider of which nova has lost track and so reassigned its ip address to our boot request, then they have an arp fight on the network13:42
fungiand some connections end up at the rogue13:42
ttxso could be transient13:43
fungiyes, my best guess is that build was simply unlucky13:44
fungii'll dig into the tripleo-ui one shortly; that sounds more complicated13:45
*** ricolin has quit IRC13:59
*** armstrong has joined #openstack-release14:02
*** ykarel is now known as ykarel|away14:05
*** ykarel|away has quit IRC14:14
*** mlavalle has joined #openstack-release14:19
*** ifat_afek has quit IRC14:23
fungiyeah, i think after staring at it a bit i'm going to see if mordred has any ideas where that hostvars reference might be cropping up, though i suspect we need to do nodeset:ubuntu-xenial on release-openstack-javascript at http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul.d/jobs.yaml#n840 for now14:24
mordredI didn't do it14:25
fungiah! here is is... http://git.openstack.org/cgit/openstack-infra/project-config/tree/playbooks/javascript/release.yaml#n1414:26
fungii guess we shouldn't be hard-coding the nodename in the playbook14:26
mordredfungi: wow. yeah14:26
mordredbut also ...14:26
mordredok. yeah. that would be teh ting- the default node_version for install_nodejs should be fine14:27
fungiahh, even the initial roles list was skipped because we hard-coded the node name there too14:27
mordredso just updating that to ubuntu-bionic should be fine14:27
mordredfungi: it's possible our decision to call the nodes teh same thing as their label might not have been the best life choice14:28
fungilooks like all the other playbooks in there use hosts:all14:28
fungiit's just release.yaml which does hosts:ubuntu-xenial14:28
ttxindeed14:29
fungiso how should the upload-npm role on localhost get the project_ver from the job node's hostvars? i'm not familiar enough with ansible variable handling14:30
fungii mean, short of just changing the hard-coded node name there14:31
mordredthikning14:32
mordredfungi: we could just re-run version-from-git on localhost and set zuul_work_dir to the src dir location on the executor14:35
fungii suppose there's no way to do an inline lookup for the name of the (in this case only) hosts entry in the inventory14:35
mordredfungi: we could also maybe set hosts: all and then do include_role: upload-npm delegate_to: localhost14:36
mnaserwe're adding support for a new service (mistral) in openstackansible and we want to bring the support ointo stable/rocky (osa doesn't follow stable policy).  i'm wondering how i can branch stable/rocky right now?  should i make a release repo change?14:37
fungioh, interesting. and that would implicitly reference the project_ver right?14:37
mordredI think so?14:37
*** armax has joined #openstack-release14:37
odyssey4memnaser you can just branch it in gerrit as far as I know14:37
mnaserhttps://review.openstack.org/#/admin/projects/openstack/openstack-ansible-os_mistral,branches14:37
fungimnaser: you don't already have a stable/rocky branch?14:38
mnaseri cant see anything there14:38
mnaserfungi: no, we made this new 'role' recently14:38
mordredfungi: https://review.openstack.org/643353 Use include_role and delegate_to for upload-npm14:38
mordredfungi: strawman14:38
mordredfungi: I have not done any testing to see if that works14:38
fungithanks mordred!14:38
fungimnaser: what odyssey4me is possible if you have create permission for refs/heads in the gerrit acl for that project, but my guess is the release team would prefer a change to openstack/releases if that project is under release management14:40
fungier, what odyssey4me says14:40
mnaseryeah, so i'm going to guess that we'll have to go through the normal release process, but i'm wondering whats the "path" to branch out much later in this case14:40
odyssey4meah yeah, so there's likely a formal release process way of doing things14:40
mnaserafaik our roles are already released as _independent so we can just create a branch now .. but i rather check with release team first to hear what they mention14:41
*** mlavalle has quit IRC14:48
ttxmnaser: we have a meeting (just after the TC office hour) we could cover that during it14:48
mnaserttx: great, thanks, ill try to be there14:48
*** mordred has quit IRC14:51
*** luizbag has quit IRC14:54
*** mordred has joined #openstack-release14:57
*** luizbag has joined #openstack-release15:08
*** luizbag has quit IRC15:10
smcginnisOh wow, much scrollback.15:14
openstackgerritKamil Sambor proposed openstack/releases master: Change 637405 - Merged  https://review.openstack.org/64336515:16
*** luizbag has joined #openstack-release15:17
smcginnis?15:18
openstackgerritSean McGinnis proposed openstack/releases master: Release tripleo-common 10.6.0  https://review.openstack.org/64336515:19
*** mordred has quit IRC15:23
*** mriedem is now known as mriedem_away15:24
*** mordred has joined #openstack-release15:30
ttxsmcginnis: summary is: release jobs are currently broken, fix in progress15:35
ttxsmcginnis: how is glass-blowing going ?15:36
*** mlavalle has joined #openstack-release15:36
smcginnisHah!15:40
smcginnisThat's tomorrow. :P15:40
ttxSchedule has it on Monday... Maybe you weren't invited.15:40
smcginnisMonday and Friday to catch the folks who come late or leave early.15:41
smcginnisI couldn't get in until Monday night.15:41
smcginnisAnd for the record, I chose the horseback riding.15:41
*** armstrong has left #openstack-release15:42
ttxhah!15:42
smcginnisI did get to have a Ridge Vineyards wine last night - https://en.wikipedia.org/wiki/Judgment_of_Paris_(wine)15:44
prometheanfiresmcginnis: did paunch get a FFE? used in heat-agents and tripleo15:45
prometheanfirehttps://review.openstack.org/64327515:45
ttxsmcginnis: that sounds like an anti-French statement15:45
smcginnisttx: Non! :)15:47
smcginnisprometheanfire: Not that I've seen.15:47
smcginnisLooks like we had a bunch of stuff go through last night. I haven't taken a look through it all yet15:48
prometheanfiresmcginnis: k, the triple-o stuff is probably fine, but technically still needs an FFE (and paunch was with that group)15:48
smcginnisjaosorior: ^^15:58
smcginnis#startmeeting releaseteam16:00
ttxmeeting time!16:00
openstackMeeting started Thu Mar 14 16:00:19 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: releaseteam)"16:00
openstackThe meeting name has been set to 'releaseteam'16:00
smcginnisPing list: smcginnis ttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong16:00
ttxo/16:00
hberaudo/16:00
smcginnis#link https://etherpad.openstack.org/p/stein-relmgt-tracking16:00
dhellmanno/16:00
diablo_rojo_phono/16:00
fungialoha16:01
smcginnisLooks like ttx has us set with a long agenda today (thanks!) so I think we can get going.16:01
smcginnis#topic Standing release automation issues16:01
*** openstack changes topic to "Standing release automation issues (Meeting topic: releaseteam)"16:01
ttxSo I approved a bunch of stuff this morning16:01
smcginnisThis is related to switching to bionic, right>16:02
ttxand then was assaulted by release-job-failures16:02
ttxsmcginnis: partially yes16:02
ttxThree issues16:02
fungiyou were our guinea pig!16:02
ttxwhich I described in several ML posts16:02
fungican't say i didn't warn you to be on the lookout ;)16:02
ttxFirst one is solved by https://review.openstack.org/#/c/643328/16:02
ttxwhich should merge asap16:03
ttxThe governance one is likely transient, we'll reenqueue when https://review.openstack.org/#/c/643328/ lands16:03
*** mlavalle has quit IRC16:03
ttxThe tripleo-ui one is due to a hardcoded host mention16:03
ttxfungi: do we ahve a fix in flight for this one?16:03
fungittx: yes, i replied to the ml with it16:04
ttxHmm https://review.openstack.org/#/c/643353/16:04
fungilet me find that16:04
ttxgot it16:04
smcginnisDoesn't look like that one is happy.16:04
fungieww, look at all the lint16:04
*** diablo_rojo has joined #openstack-release16:05
ttxAttributeError: 'AnsibleUnicode' object has no attribute 'get' eeewwwww16:05
ttxthanks for nothing ansible-lint16:05
smcginnisCan we assume mordred is on that?16:06
ttxmaybe it's its way to complain about spaces in the task name16:06
ttxif that is the case I recommend therapy16:06
fungiyeah, i'm pinging him to help figure it out16:07
fungiover in #openstack-infra16:07
ttxanyway, that one is less urgent16:07
smcginnisSo assuming that all merges, are we pretty confident that is all the issues?16:07
ttxsince it only affects tripleo-ui16:07
ttxwhich TripleO is not even sure to include in release16:07
ttxyes16:07
smcginnisOK, good.16:08
smcginnisAnd nothing to reenqueue?16:08
ttxthe governance one should be reenqueued16:08
fungiwell, it may affect other javascript-based projects trying to release too16:08
ttxopenstack/governance 0.4.016:08
fungiso getting it ironed out sooner is better16:08
fungii'll reenqueue the governance tag and make sure we don't see any recurrence but i'm pretty sure that was a random provider issue16:09
smcginnisWe have a list of horizon projects on the agenda. I would assume then we shouldn't release any of those for now.16:09
ttx++16:09
smcginnisAlright, sounds like everything is in hand. I'll move to the next topic.16:10
fungiwhen we get a fix for the observed tripleo-ui release failure merged we can try approving one js-based project release and not a large batch initially, just to see what happens16:10
smcginnis#topic Stein branch creation hold16:10
*** openstack changes topic to "Stein branch creation hold (Meeting topic: releaseteam)"16:10
smcginnisfungi: ++16:10
smcginnis#link https://review.openstack.org/#/c/643268/16:11
ttxyeah, just a quick point that while the patch has been created, apparently we should wait for tonyb to try something16:11
ttxI think we should do it sooner rather than later though16:11
smcginnisThis is related to having the upper-constraints handling updated to simplify that transition, right?16:11
ttxso do we have an ETA on that tonyb-thing?16:11
ttxsmcginnis: yes16:11
dhellmannI don't know about an eta16:12
smcginnisReally too bad this is in the middle of his night.16:12
smcginnisI think we're going to have to switch times again.16:12
ttxsomething he will have to fix as our new fearless leader16:12
smcginnisOr send Tony a heck of a lot of coffee.16:12
ttxthe release management diet16:12
smcginnisSo nothing for us to do right now, just awareness that some branching things are on hold pending Tony's update, right?16:13
ttxok, let's make sure we communicate with him later in the day / earlier in his day to see how far it is and if it's worth waiting16:13
smcginnisDoes this mean we should not process any branch creation patches until then. (assuming we can release again soon)16:14
ttxhmm, I'd say no.. but I'm not sure.. dhellmann ?16:15
dhellmannthis is the change we need: https://review.openstack.org/64338716:15
*** ykarel has joined #openstack-release16:16
smcginnisdhellmann: So we should merge that before processing any branch requests?16:16
ttxah. Probably wait then16:16
dhellmannyes, that's the idea16:16
smcginnisOK.16:17
dhellmannI just did that very quickly, so check my spelling in that URL, please :-)16:17
ttxdhellmann: note that we have a bunch that have already gone in16:17
smcginnisI do see it redirects to master for now: https://releases.openstack.org/constraints/upper/stein16:17
ttx(I list them on my commit message)16:17
dhellmannttx: it won't be the end of the world16:17
smcginnisDo those ones that have branched need to be updated? Or they are fine for now and we eventually get to where we want to down the road?16:17
dhellmannoh, we may need to update that template with the redirects after the opendev change16:17
dhellmannthey're fine for now, the patches just point to something that doesn't exist so they can't merge16:18
ttxok, I think we can safely move to next topic then16:18
dhellmannor rather they can, but they will break local development if they do16:18
dhellmannso they *shouldn't* merge16:18
dhellmannthis change was all about removing that window16:18
smcginnisAnd that's no different than how we've been for at least the last few releases, so that's fine.16:19
dhellmannoh, I wonder if that branch variable is going to contain "stable/stein" not just "stein"16:19
smcginnisWe better find out I guess.16:20
smcginnisI'll move on for now though.16:20
smcginnis#topic deliverables with no intermediary releases yet16:20
*** openstack changes topic to "deliverables with no intermediary releases yet (Meeting topic: releaseteam)"16:20
dhellmannyeah16:20
ttxThis one is more FYI16:20
smcginnisDo we need to add --type other and --type horizon-plugin to our process doc?16:21
ttxWe have a significant set of things that are cycle-with-intermediary and had no release yet16:21
ttxso we have no fall back if they do not produce anything16:21
ttxI guess we could have switched them to cycle-with-rc around FF like the service stuff16:22
smcginnisMaybe add something that at RC1 they we force them if nothing from the team?16:22
smcginnisThose types have always been a little different. I'm never sure if we should treat them as libs or services or what.16:22
ttxbut in a lot of cases (like the tempest-plugins) it's just that there is little interest in releasing them more than once (be it through RCs or intermediary releases)16:22
smcginnisWhich I guess is why they are called "other" in the first place. :)16:22
ttxI wonder if we should not have one new release type called "automatic"16:23
smcginnisHorizon ones kind of seem like they should be considered client libs though.16:23
dhellmannthe reason for making the tempest plugins -with-intermediary is that nothing can consume a pre-release of a python library in our CI system16:23
dhellmannI don't know if anything does consume those from releases, though16:23
dhellmannat least in CI16:23
ttxdhellmann: making them "cycle-automatic" we would just automatically release them on RC weel for example16:23
ttxweek*16:24
dhellmannsure, that works16:24
fungiwe certainly _could_ consume prereleases in our jobs if we want (there's a pip option to enable them)16:24
ttxnote that I would not encourage puting anything other than .. hmm.. "other" into that mode16:24
fungiit's more been a philosophical choice to prefer testing against releases16:24
dhellmannyeah16:24
ttxhorizon-plugins should proabbly be made cycle-with-rc16:25
smcginnis"automatic" would make it explicit, but would we still want to give them the option to release as needed?16:25
dhellmannttx: maybe cycle-automatic is just cycle-with-intermediary && other then?16:25
ttxmaybe16:25
ttxsmcginnis: sure16:25
ttxalthough...16:25
ttxI'd say that -automatic things would be re-released at then end16:25
ttxthe*16:25
dhellmannwe would have to update list-deliverables to let us query for the absence of a value to build the list of intermediary things that need earlier releases, so a new model might be easier16:26
smcginnisIf commits merged since last release16:26
ttxlike if you do a release around milestone-1 we would still push a new release at the end of the cycle16:26
smcginnisOr we just add to process.rst that we force release c-w-i --type other like we do for the other intermediary deliverables.16:26
dhellmannyeah16:26
dhellmannyeah, that works, too16:27
ttxanyway, that's more for next cycle16:27
ttxAdding a note at the bottom of the tracking doc to remember16:27
smcginnisYay, defer to the next PTL> :)16:27
ttxFor this cycle... I'd say force them at RC116:27
ttxor the week after16:28
smcginnisI can add a note to this week's countdown email.16:28
ttxsee the task I added to R-216:28
smcginnisGreat, was going to say that seems like the right timing to me.16:28
smcginnisI will mention it to raise awareness now though.16:29
smcginnisAnd we would create stable branches with that too?16:29
dhellmann++16:29
ttxyes16:29
smcginnisOK, moving on then.16:30
smcginnis#topic mnaser's recent question on the IRC channel16:30
*** openstack changes topic to "mnaser's recent question on the IRC channel (Meeting topic: releaseteam)"16:30
ttxSee 14:37 utc and down in the backlog16:30
smcginnis#link http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2019-03-14.log.html#t2019-03-14T14:37:1016:31
ttxwanting to create a stable/rocky branch on a recently-added deliverable16:31
mnaserHello16:31
ttxasking how to proceed16:31
ttxmnaser: oh hi sir16:31
mnaserYep. It’s necessary for us to get it to run and integrate with the rest of the repos16:31
smcginnisIt's independent, so I guess just add the branching request there?16:32
smcginnisOdd since it wasn't actually part of that cycle, but these deployment projects are different than the other ones.16:32
ttxis it independent?16:32
mnaserYep. All our roles are independent indeed so as far as I understood that should be okay?16:32
smcginnisMaybe I read through too fast.16:32
dhellmannyeah, just edit the deliverable file16:32
dhellmannmnaser : do you need to branch the role? or openstack-ansible?16:32
mnaserYes I believe all our roles are independent. I’m on mobile so I can’t double check16:32
mnaserNo, the role: specifically OpenStack-ansible-os_mistral16:33
dhellmannok, there aren't any branches at all in the deliverable file right now16:33
dhellmannI'm not sure what will happen if you try to just branch one repo16:33
dhellmannso we might need to just do this by hand16:33
mnaserYep, we added it this cycle.. so it’s a bit tricky16:33
ttxit's not cycle-independent right16:33
ttxok so16:34
ttxOne issue is that in theory we do NOT add deliverable files after a release is done16:34
dhellmannoh, there are *older* deliverable files in the independent directory so I got confused16:34
smcginnisSo it isn't independent? I think both statements have been madre.16:35
smcginnis*made16:35
dhellmannsmcginnis : it was, but is not now16:35
smcginnisAh16:35
ttxIt's an independent deliverable, as in separate16:35
mnaserYes. evrardjp worked on making that change16:35
ttxbut not cycle-independent model?16:35
mnaserWe realized roles don’t really need to be tied in16:35
mnaserLet me verify16:35
*** jtomasek has quit IRC16:35
dhellmannI see deliverables/stein/openstack-ansible-roles.yaml and deliverables/rocky/openstack-ansible-roles.yaml16:36
dhellmannand a couple of individual deliverable in _independent for 2 roles (chrony and redhat-subscription)16:36
dhellmannand deliverables/_independent/openstack-ansible.yaml16:36
dhellmannthe change evrardjp made was to stop tagging every role every time there is an OSA release16:37
dhellmannonly the main openstack-ansible repo is tagged now16:37
dhellmannthey all still need to be branched, though16:37
dhellmannhence the 2 separate deliverable files16:37
mnaserah, I miss understood then. chrony ans redhat one aren’t ansible ones16:37
dhellmannoh, those may be tripleo16:37
mnaserThey are16:37
evrardjphey16:38
mnaserok, so within the “release” infrastructure, what we’re doing isn’t necessarily possible?16:38
evrardjpI am in  a meeting, sorry I can't join this conversation16:38
mnaserall good :)16:38
dhellmannevrardjp : it's fine, I think we have it16:38
smcginnisWe can just blame it all on evrardjp16:38
mnaserI’ll happily take the blame16:38
mnaserIt’s 8 degrees Celsius outside. I’m in a happy space.16:38
*** e0ne has quit IRC16:38
dhellmannmnaser : you want to take a new deliverable and create a stable/rocky branch for it, right?16:38
dhellmannand then add that to your rocky release for openstack-ansible?16:38
ttxdhellmann: deliverables/_independent/openstack-ansible.yaml is not branched16:38
dhellmannttx: right, that's what threw me at first16:39
evrardjpit's been a long time we haven't been independent :)16:39
mnaserdhellmann: ideally.16:39
ttxvi deliverables/rocky/openstack-ansible-roles.yaml16:39
ttxoops16:39
mnaserhah :)16:39
dhellmannI think the thing to do here is to edit deliverables/rocky/openstack-ansible-roles.yaml16:39
evrardjpyeah dhellmann is right, the idea was to still tag osa repo, and stop tagging the rest.16:39
evrardjpso we had to move to a different release file, and defined branchless IIRC16:40
evrardjpsorry, tagless*16:40
dhellmannediting that file to add the new repo and a branch point for it should trigger a new branch in just that repo16:40
ttxok, so technically you are not adding a new deliverable file, so I think that should work16:40
ttxtrying to hole the principles line here16:40
ttxhold even16:40
smcginnisThis seems OK. Again, it's a deployment project, so I think it's fine to add something to rocky.16:41
dhellmannI'm willing to be pretty flexible on that for deployment tools16:41
evrardjpI agree with adding the role to osa-roles, if necessary branch manually in gerrit?16:41
dhellmannmnaser: is it clear what you need to do, now?16:41
* ttx grabs a drink16:41
dhellmannevrardjp : we shouldn't need to do anything by hand16:41
evrardjpif necessary16:41
evrardjphoping it's not16:41
smcginnisttx: A California wine?16:41
ttxsmcginnis: served in a LFOSLS glass16:42
smcginnislol16:42
mnaserdhellmann: it is and i wanted to get the “everything is alright by release team” sigh off which I seem to have.16:42
smcginnismnaser: ++16:42
mnaserI’ll push the change later today. Thank you all.16:42
ttxsigh-off is exact16:42
smcginnisThanks for bringing it up mnaser16:42
dhellmannyep, +1 from me16:42
ttxIt's been a long week, and we are only Thursday16:42
smcginnisAny other topics to cover?16:43
mnaserI need a bigger phone screen. Typing means sigh offs16:43
mnaserThanks again16:43
smcginnis#topic Open floor16:43
*** openstack changes topic to "Open floor (Meeting topic: releaseteam)"16:43
ttxsmcginnis: task review for next week?16:43
smcginnisttx: Ah, good call.16:43
smcginnis#link https://releases.openstack.org/reference/process.html#rc1-week16:44
smcginnisSo we are generating the RC1 release patches?16:44
dhellmanndo we want to paste from the process doc into the etherpad?16:44
*** ykarel has quit IRC16:44
smcginnisI'll do that.16:44
dhellmannk16:44
dhellmannsome of those devstack-gate instructions are apparently out of date. maybe gmann and fungi can help with those details.16:45
smcginnisI was going to raise that too.16:45
smcginnisWe should get the current requirements for that and get process.rst updated.16:45
ttxpoints 3 and later , we can discuss at next week meeting16:45
ttxsince they won't be ready by Thursday morning16:46
ttxI propose to push them to next week meeting agenda16:46
fungii think the only think devstack-gate needs these days is an entry in the version matrix gile16:46
fungis/gile/file/16:46
smcginnisWe can move those later, but leaving it there for now to make sure it's seen.16:47
ttxHmm, point 11 should be moved up16:47
ttxI'll do that16:48
gmannand grenade branch update also16:48
gmannwhen we cut stable branch16:48
fungidoes grenade still rely on devstack-gate for that?16:48
gmannyeah16:48
smcginnisttx: I do have the cycle-highlight mention in this weeks countdown email, but that could probably use another post of its own.16:48
ttxI'll propose the corresponding process change16:48
gmannzuulv3 job migration is in progress but not merged yet16:48
ttxyeah, around Tuesday-ish16:49
ttxI moved it up as point 216:49
smcginnisI'm wondering about our decision to propose the RC1 patches coming from us early in the week.16:49
smcginnisThere's usually a crunch for folks getting in those final patches, so us proposing one at the beginning of the week is just going to create extra zuul load that will probably need to get updated with a new hash later anyway.16:49
openstackgerritDuc Truong proposed openstack/releases master: Add Senlin release highlights  https://review.openstack.org/64339616:49
dhellmannshould we wait and do that later in the week?16:50
smcginnisMaybe later on Wednesday?16:50
dhellmannthat doesn't give a lot of time for +1 from PTLs16:51
smcginnisI would hope by that point they wouldn't need much time.16:51
ttxdone16:51
openstackgerritThierry Carrez proposed openstack/releases master: Reorder steps on RC1 week process  https://review.openstack.org/64339816:51
fungigmann: so http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/roles/test-matrix/files/features.yaml and http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n302 need updating, but that's all for devstack-gate nowadays?16:51
ttxsmcginnis: it's a balance16:51
ttxif the RC1s seem to be coming, then waiting is best16:52
gmannfungi: i think so. other part of d-g where legacy jobs rely are static one16:52
smcginnisI suppose we do have more projects now that could be ready already on Monday.16:52
ttxalso the announcements tricking down to teh ML are a great reminder16:52
ttxtrickling damn16:53
smcginnisI guess that's what we decided and wrote down, so we could just stick with it and see how it goes, then readjust for train if we find it's not optimal.16:53
ttxsmcginnis: editing the existing review means less work for ptl too16:53
smcginnisThat's true. That could be nice.16:53
ttxhmm.. did we update the ML address for RC announcements ?16:54
*** mriedem_away is now known as mriedem16:54
dhellmannwhere?16:54
ttxsmcginnis: like... one less round for 0.0.0rc1 mistakes16:54
smcginnisOh, those go to discuss and not announce, right?16:54
dhellmannoh, those go to the -dev/-discuss list16:54
ttxyes²16:54
smcginnisIs that in the job?16:54
* ttx is looking16:55
smcginnisSeems like one of the scripters using codesearch would have gotten that.16:55
dhellmann94a24d03dc818b4a23d0140863745ef9af590a8816:57
dhellmanni think that will do it?16:57
*** jaosorior has quit IRC16:57
ttxyes16:58
smcginnisYep. Great.16:58
ttxi was almost there down in that rabbit hole.16:58
ttxdhellmann: you're fast. It's almost as if you wrote all those things.16:58
dhellmannalthough I don't see anything at all sending to the release-announce list16:58
*** jaosorior has joined #openstack-release16:58
dhellmann*cough* someone should have updated the comment block at the same time16:58
* dhellmann is looking forward to having space in his head for other things16:59
smcginnisOK, so let's go with generating RC requests early next week as we had previously decided. Anything else we should cover?16:59
ttxsorry for the drill. But then it's always useful to check we still know where to look16:59
ttxsmcginnis: nope16:59
smcginnis++16:59
smcginnisNice full hour. Thanks everyone.17:00
fungithanks smcginnis!17:00
smcginnis#endmeeting17:00
*** 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:00
openstackMeeting ended Thu Mar 14 17:00:18 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-14-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-14-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-14-16.00.log.html17:00
ttxThx smcginnis !17:00
smcginnisdiablo_rojo_phon: Since you've had some experience with it now, would you be intereted in queuing up the RC1 release patches for all cycle-with-rc deliverables early next week?17:01
diablo_rojosmcginnis, yeah I could probably handle that.17:02
smcginnisdiablo_rojo: Cool, thanks!17:03
diablo_rojoI'm doing all of them? Not like waiting for PTLs and doing them if they dont?17:03
smcginnisYeah, I think we just generate them all at the beginning of the week.17:04
smcginnisThen the PTLs can either +1 if they are ready, or block them if they will have an updated sha for us to use later in the week.17:04
diablo_rojosmcginnis, sounds good. Ill generate a list today to make sure I have the right ones if youre willing to sign off on it later :)17:05
smcginnisThat'd be great17:05
diablo_rojosmcginnis, sounds good :) Will circle back later.17:06
*** udesale has quit IRC17:06
*** tesseract has quit IRC17:08
openstackgerritMerged openstack/releases master: Reorder steps on RC1 week process  https://review.openstack.org/64339817:17
*** dtantsur is now known as dtantsur|afk17:18
*** jpich has quit IRC17:38
*** e0ne has joined #openstack-release17:46
*** hberaud is now known as hberaud|gone17:52
dhellmanndiablo_rojo : bonus points if you script it ;-)18:13
openstackgerritMohammed Naser proposed openstack/releases master: openstack-ansible: add mistral role to rocky  https://review.openstack.org/64341718:18
mnaserdhellmann, smcginnis, ttx ^ as discussed!18:19
mnasero18:20
mnasera review already18:20
dhellmannmnaser : commented18:20
dhellmann:-)18:20
dhellmannyou caught me as I was flushing my inbox18:20
openstackgerritMohammed Naser proposed openstack/releases master: openstack-ansible: add mistral role to rocky  https://review.openstack.org/64341718:20
mnaservoila18:20
dhellmannlet's see what the bots have to say18:23
*** e0ne has quit IRC18:33
*** notmyname has quit IRC18:38
*** notmyname has joined #openstack-release18:39
*** e0ne has joined #openstack-release18:40
mnaserdhellmann: sorry to bother ya, just hoping to get this done today -- https://review.openstack.org/#/c/643417/ seems that gates are happy18:47
dhellmannwe probably don't need to wait for that branch script fix for this one, since the roles don't worry about upper constraints?18:48
dhellmannmnaser : ^18:48
mnaserdhellmann: double checking now18:49
dhellmanneither way, one repo won't be hard to "fix" and the value it gets won't be wrong18:49
dhellmannwe could just fix it on the patch the bot proposes18:49
mnaserdhellmann: looks like we do, even though there's not really a point 'afaik' https://opendev.org/openstack/openstack-ansible-os_mistral/src/branch/master/tox.ini18:49
mnaseryeah, i can make sure we do that18:49
dhellmannok, approved18:49
mnasertyvm18:49
* dhellmann crosses his fingers that the branch job isn't broken by the bionic update18:50
mnaserdhellmann: well better break on some small 'rocky' thing than breaking when you're branching all the stein stuff :)18:51
mnaseryou're welcome in advance for the testing :P18:51
dhellmanntrue18:51
dhellmannhaha18:51
*** gmann is now known as gmann_afk18:51
dhellmannthanks!18:51
*** mgoddard has joined #openstack-release18:51
openstackgerritMerged openstack/releases master: openstack-ansible: add mistral role to rocky  https://review.openstack.org/64341718:59
openstackgerritGraham Hayes proposed openstack/releases master: Add Designate cycle highlights for Stein  https://review.openstack.org/64345620:58
*** armax has quit IRC21:09
*** mriedem is now known as mriedem_away21:27
*** whoami-rajat has quit IRC21:31
openstackgerritMerged openstack/releases master: Add cinderlib  https://review.openstack.org/64313322:00
*** pcaruana has quit IRC22:21
*** e0ne has quit IRC22:28
diablo_rojosmcginnis, so patches for these Mondayish? http://paste.openstack.org/show/747817/22:30
*** gmann_afk is now known as gmann22:40
*** mriedem_away has quit IRC23:23
fungithe openstack/tripleo-ui 10.3.0 release jobs finally worked, so it's probably safe to try another release for a js-based project and see how that goes23:24
fungithanks for bearing with us!23:24
*** tosky has quit IRC23:26

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!