Thursday, 2021-06-17

*** ykarel|away is now known as ykarel04:14
*** marios is now known as marios|ruck05:44
opendevreviewTakashi Kajinami proposed openstack/releases master: [Puppet OpenStack] Fix some bugs in the last train release  https://review.opendev.org/c/openstack/releases/+/79677007:05
opendevreviewTakashi Kajinami proposed openstack/releases master: [Puppet OpenStack] Fix some bugs in the last train release  https://review.opendev.org/c/openstack/releases/+/79677007:06
*** rpittau|afk is now known as rpittau07:22
*** akekane__ is now known as abhishekk08:04
*** ykarel is now known as ykarel|lunch08:38
*** ykarel|lunch is now known as ykarel09:45
opendevreviewHervé Beraud proposed openstack/releases master: retire puppet-panko  https://review.opendev.org/c/openstack/releases/+/79669011:32
opendevreviewHervé Beraud proposed openstack/releases master: Fix validation to ensure that first release of series isn't a bugfix  https://review.opendev.org/c/openstack/releases/+/79645611:36
opendevreviewHervé Beraud proposed openstack/releases master: Fix validation to ensure that first release of series isn't a bugfix  https://review.opendev.org/c/openstack/releases/+/79645611:40
opendevreviewMerged openstack/releases master: Release rally 3.3.0  https://review.opendev.org/c/openstack/releases/+/79663411:41
opendevreviewHervé Beraud proposed openstack/releases master: Fix validation to ensure that first release of series isn't a bugfix  https://review.opendev.org/c/openstack/releases/+/79645611:48
opendevreviewMerged openstack/releases master: Push validations-libs 1.2.0 version  https://review.opendev.org/c/openstack/releases/+/79624211:56
opendevreviewMerged openstack/releases master: ovsdbapp 1.11.0  https://review.opendev.org/c/openstack/releases/+/79647311:56
hberaudttx, elodilles: Just to make it explicit, the latest job failure is related to puppet-panko, so, we face again the same problem of retired repo with reno. Worth ignoring it.12:19
elodilleshberaud: ack12:23
elodilleshberaud, another question (regarding ocata-eol): i don't know how many similar repositories are, but there is for example dragonflow, that is 'abandoned' but has stable/ocata branch seemingly: https://opendev.org/openstack/dragonflow12:49
elodillesand the question is: what should we do with it?12:49
elodillesit's not even listed in deliverables/ocata/12:50
elodillesso it's a bit strange12:50
hberaudGood question, I would suggest to transition it to eol if the stable branch exist12:50
elodilleshberaud: but how? :) there is no deliverable/ocata/dragonflow :)12:51
elodillesor should we create a yaml there?12:51
hberaudAh I see, sorry12:51
hberaud:)12:51
hberaudReally good question12:51
hberaudmaybe we could simply drop the existing branch12:52
hberaudand ignore the rest12:52
hberaudThoughts?12:52
elodillesactually, as it seems, even stable/newton branch still exists for dragonflow12:53
elodillesthe question is whether someone consumes dragonflow's ocata branches...12:54
hberaudDo we want to spend time on it? if the project is abandoned I don't expect lot of people complaining about the remaining branches12:55
elodilleslet's ask noonedeadpunk as he asked me about what to do with dragonflow12:55
elodillesnoonedeadpunk: opinion? ^^^12:55
hberaudMaybe we could simply trigger a ML thread to warn about the deletion and if nobody complain then start removing these stale branches12:56
noonedeadpunkBut I think we would need to drop them sooner or later anyway?12:56
noonedeadpunkOr at least have some workflow to follow?12:56
hberaudRight time to drop them12:56
noonedeadpunkas it's not single project that has been deprecated12:56
elodillesnoonedeadpunk: + a comment: retired projects are usually also listed under deliverables/ , and those are treated the same way when EOL'ing as active projects12:57
elodillesnoonedeadpunk: so here the problem seems that it is not even listed under deliverables/12:57
noonedeadpunkyes, retired, not deprecatred, sorry12:58
noonedeadpunkyeah, got it, so em can't be set without it being in deliverables.13:00
noonedeadpunkwhich means that the code will eventually be just droped without ability to track down progress between releases...13:01
noonedeadpunkbut I can imagine it's being used in some P or Q deployment easily...13:02
elodilleswell... hmmm... maybe we could tag the latest state of those branches as '$series-eol' (by adding them now to deliverables/$series/dragonflow.yaml) and then delete13:03
elodilleshberaud: what do you think about this ^^^ ?13:03
noonedeadpunkI like this plan13:03
elodillesso that we won't lose history13:04
hberaud+113:04
hberaudCan't hurt13:05
elodilleshberaud: cool, then I'll try to propose a patch :)13:05
elodillesnoonedeadpunk: by the way, do you need that to OSA, or why did you asked about dragonflow in the first place? :)13:06
elodilles* ask13:06
noonedeadpunkI needed to set some sha/branch/tag to EOL patch so it would be a valid one13:07
noonedeadpunkie https://review.opendev.org/c/openstack/openstack-ansible/+/795690/2/playbooks/defaults/repo_packages/openstack_services.yml13:07
hberaudelodilles: thanks13:08
elodillesnoonedeadpunk: I see. Do you see other than dragonflow that has ocata branch but not listed under deliverables/ocata/ ?13:11
noonedeadpunkneutron-lbaas-dashboard ?13:13
noonedeadpunkalso not sure about nova-powervm, nova-lxd13:15
noonedeadpunkand swift313:15
noonedeadpunkbut we didn't have all projects available for deployement, so there might be more13:16
elodillesI'll check those, thanks13:16
opendevreviewElod Illes proposed openstack/releases master: WIP: Set eol to Dragonflow  https://review.opendev.org/c/openstack/releases/+/79684113:36
elodilleshberaud: meanwhile, I've checked neutron-lbaas-dashboard, it has similar (but not the same!) situation: it has stable/ocata, but has only neutron-lbaas-dashboard.yaml under pike-queens (and branches up till stable/stein)13:38
elodilleshberaud: and now I'm a bit confused :/13:38
elodilleshberaud: whether we really need to add this kind of 'fake' deliverables for all of these (maybe there are even more repos like this?)13:39
hberaudelodilles: AFAIK until now nobody complained, maybe we could continue to live with them13:41
hberaudif it's not an isolated case, then I would suggest to not add these deliverables files13:41
hberaudand maybe go straight to branch deletion by warning before13:42
hberaudStable branches seems to be the poor parent of our release management process13:44
hberaudI don't know if we faced similar use case during previous series (oldest than ocata)13:45
elodilleshberaud: the 1st part is OK with me: to live with them :) but in that case I would not even delete those branches as who knows whether those are consumed downstream and we would lose 'history' o:)13:45
hberaudLGTM13:46
elodillesdefinitely there is stable/newton still open (at least for dragonflow)13:46
elodillesand there can be others as well13:46
hberaudI see13:47
hberaudI think that you're right we should leave these branches opened13:47
elodillesmaybe smcginnis and ttx have some historical knowledge :)13:48
toskyor maybe just people forgot to close them and they should be deleted...13:50
elodillestosky: i'm not sure it's simply just forgotten.13:51
elodillestosky: and deleting without tagging them would mean losing history13:51
toskysure, so just tag the latest13:52
toskyor just ask again the people responsible for that project (I'm 99% sure they will say to kill anything <=ocata)13:52
elodilleswell, maybe they are not even around, so no answers will come :) (I know, in that case we could simply delete them... and what if we delete them and someone comes with the question 'where is it?' later on :))13:54
elodillesmaybe I'm overthinking it, but.... :)13:55
elodillesanyway, if we just simply leave those stable/ocata branches open, then OSA should use hashes for them, as there won't be ocata-eol tag13:57
elodillesand I will go back to approve the nice and clean ocata-eol patches... (and think more about this later on)13:59
*** marios|ruck is now known as marios|call14:02
opendevreviewMerged openstack/releases master: [watcher] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79568414:31
opendevreviewMerged openstack/releases master: [winstackers] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79568514:36
opendevreviewMerged openstack/releases master: [horizon] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79565514:43
*** marios|call is now known as marios|ruck14:44
opendevreviewMerged openstack/releases master: [magnum] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79565814:46
opendevreviewMerged openstack/releases master: [monasca] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79566114:56
opendevreviewMerged openstack/releases master: [glance] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79565315:01
hberaud+1 to leave the branches opened for now. I think that they just have been forgotten but in the doubt that can't hurt to leave them opened. The checks against old branches have been introduced with Wallaby, so, it doesn't shock me if they have been forgotten. Also EM have been introduced around the ocata period too and so ocata have been surely impcated by the grey area around the15:05
opendevreviewMerged openstack/releases master: [neutron] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79566315:05
hberaudstable branch deletion policy brought by EM.15:05
*** ykarel is now known as ykarel|away15:10
opendevreviewMerged openstack/releases master: [ironic] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79565615:14
elodilleswell, these old open branches are not related to EM. It's more like repositories without deliverables, I think.15:17
opendevreviewMerged openstack/releases master: [nova] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79566415:18
elodilleshmmm, and there is a release job failure: https://zuul.opendev.org/t/openstack/build/cbeed3bf86b749c49ddac9ae708a4c3615:18
elodillesrelated to this patch: https://review.opendev.org/c/openstack/releases/+/79565515:20
elodilles"No '.gitreview' file found in this repository. We don't know where15:20
elodillesyour gerrit is."15:21
elodilles(but .gitreview is there: https://opendev.org/openstack/django_openstack_auth/src/branch/stable/ocata/.gitreview )15:22
opendevreviewMerged openstack/releases master: [Telemetry] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79567915:26
*** rpittau is now known as rpittau|afk16:09
*** marios|ruck is now known as marios|out16:28
*** akekane_ is now known as abhishekk16:44
opendevreviewJeremy Stanley proposed openstack/releases master: Correct the tox option for skipping sdist generation  https://review.opendev.org/c/openstack/releases/+/79691617:09
elodillesand a 2nd release job failure, this time it's the SSH connection timeout again: https://zuul.opendev.org/t/openstack/build/69fc52bff367468f9de9ad4713baf33917:47
hberaudThe tag have been create https://opendev.org/openstack/django_openstack_auth/src/tag/ocata-eol17:58
hberauds/has/have/17:58
hberaudI would argue that we can ignore it18:00
opendevreviewElod Illes proposed openstack/releases master: [Puppet OpenStack] Transition Train to EM  https://review.opendev.org/c/openstack/releases/+/79076718:37

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