Friday, 2021-02-12

*** tosky has quit IRC00:36
*** diablo_rojo has quit IRC00:47
*** ykarel_ has joined #openstack-release04:51
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** ykarel_ is now known as ykarel05:59
*** eolivare has joined #openstack-release06:55
*** slaweq has joined #openstack-release07:11
*** sboyron_ has joined #openstack-release07:45
*** ykarel_ has joined #openstack-release07:47
*** ykarel has quit IRC07:50
*** rpittau|afk is now known as rpittau08:02
*** jbadiapa has joined #openstack-release08:21
*** tosky has joined #openstack-release08:24
*** e0ne has joined #openstack-release09:56
*** strigazi has joined #openstack-release10:30
*** ykarel_ is now known as ykarel10:37
*** e0ne has quit IRC11:04
*** e0ne has joined #openstack-release11:05
*** e0ne has quit IRC11:06
*** e0ne has joined #openstack-release11:08
ttxFor os-collect-config I'd say we should not sweat it too much, since it has switched to independent11:15
*** e0ne has quit IRC11:16
ttxtripleo-ipsec has not, but the tag history shows it could make a good candidate too11:17
ttxSounds like the two "solutions" would be (1) to temporarily disengage Semantic versioning check so that this odd case goes through, or (2) make tripleo-ipsec cycle-independent and forget about stable branch releases in os-collect-config and tripleo-ipsec11:19
ttxIn all cases we should definitely add a check to not be in that situation again11:20
openstackgerritStephen Finucane proposed openstack/releases master: Release cliff 3.7.0  https://review.opendev.org/c/openstack/releases/+/77536711:37
*** dtantsur|afk is now known as dtantsur11:41
*** brtknr has quit IRC11:55
*** brtknr has joined #openstack-release11:56
*** brtknr has quit IRC11:58
*** brtknr has joined #openstack-release11:59
*** brtknr has quit IRC11:59
*** brtknr has joined #openstack-release12:00
*** brtknr has quit IRC12:00
*** brtknr has joined #openstack-release12:00
*** brtknr has quit IRC12:01
*** brtknr has joined #openstack-release12:01
openstackgerritMoisés Guimarães de Medeiros proposed openstack/releases master: Add TLS support to oslo.cache  https://review.opendev.org/c/openstack/releases/+/77537512:35
openstackgerritMoisés Guimarães de Medeiros proposed openstack/releases master: Add TLS support to oslo.cache  https://review.opendev.org/c/openstack/releases/+/77537512:35
openstackgerritIury Gregory Melo Ferreira proposed openstack/releases master: Release IPA bugfix/6.6.0 for wallaby  https://review.opendev.org/c/openstack/releases/+/77537812:52
*** nweinber has joined #openstack-release13:43
hberaudelod: Please can you validate this patch => https://review.opendev.org/c/openstack/releases/+/77516113:44
hberaudttx: I'll ping mario about tripleo-ipsec13:46
elodhberaud: looking13:49
hberaudthx13:49
hberaudand it would be awesome to validate this one too => https://review.opendev.org/c/openstack/releases/+/77537513:50
openstackgerritMerged openstack/releases master: Release metalsmith 1.2.1 for Victoria  https://review.opendev.org/c/openstack/releases/+/77512813:50
*** marios has joined #openstack-release13:52
marioso/ hberaud13:52
hberaudo/13:52
hberaudWe have some issues with os-collect-config and tripleo-ipsec13:53
hberaudlet me grab some links13:53
marioshberaud: hm you mean on some ongoing release (maybe the train one? )13:53
hberaudC.f ttx's mail http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020112.html13:54
hberaudmarios: our issue was with ussuri13:54
marioshberaud: yeah i recall and ttx posted something to tag ussuri13:55
hberaudttx added the missing branches https://review.opendev.org/c/openstack/releases/+/77299513:55
hberaudso yesterday fungi tried to reenqueue the previous failing jobs however it didn't work as expected13:56
mariosah i see13:56
hberaudmarios: it fail because 13.0.0 and 11.0.2 point on the same commit13:58
hberauddue to the branches that missed13:58
marioshberaud: what can we do now13:58
hberaudos-collect-config is now independent so I think we can ignore ussuri13:59
marioshberaud: is there a way to fix it13:59
hberaudWhat do you think about moving tripleo-ipsec to independent?13:59
hberaudand forget about stable branch releases in os-collect-config and tripleo-ipsec14:00
hberaudthe tag history shows that tripleo-ipsec could make a good candidate to independent14:00
marioshberaud: yeah it is a possibility but doing it will take at least a week or so to allow feedback etc14:00
hberaudno rush14:01
marioshberaud: so is it OK to block those jobs until then?14:01
hberaudyes no problem14:01
marioshberaud: ok cool, sorry fungi and hberaud about that even if it was before my time ;)14:01
marios(as the release liaison i mean )14:02
hberaudAs long as we find a solution to unblock the situation, it's not a problem14:02
hberaudmarios: np14:02
marioshberaud: not really much activity there https://opendev.org/openstack/tripleo-ipsec/commits/branch/master so i don't expect much objection14:03
hberaudI'll add this topic to our next meeting to be sure to not forget that14:03
hberaudawesome14:03
hberaudmarios: Thanks for your time14:05
marioshberaud: same to you will post something on the list soon about it and post the review to move it14:06
hberaudThanks14:06
hberaudI added the check to write to avoid similar use case into our "things to change"14:15
hberaudhttps://etherpad.opendev.org/p/wallaby-relmgt-tracking line 53314:15
elodhberaud: sorry, I am a bit unsure about the patch, see my comment >>> https://review.opendev.org/c/openstack/releases/+/77516114:17
*** e0ne has joined #openstack-release14:24
openstackgerritMarios Andreou proposed openstack/releases master: Move tripleo-ipsec repo to independent release model  https://review.opendev.org/c/openstack/releases/+/77539514:25
openstackgerritMarios Andreou proposed openstack/releases master: Move tripleo-ipsec repo to independent release model  https://review.opendev.org/c/openstack/releases/+/77539514:30
marioshberaud: ^^ & http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020451.html fyi thanks14:31
hberaudI seen thanks! marios++14:31
*** e0ne has quit IRC14:49
*** haleyb has quit IRC15:02
*** rpittau is now known as rpittau|afk15:03
*** haleyb has joined #openstack-release15:04
fungittx: for option 1, that would need a feature added to pbr and some additional patch merged to tripleo-ipsec to turn it on indefinitely for the affected branch(es)15:20
fungithough maybe it could just be until the lower tag was applied, depends on whether pbr cares that there's no higher version in the history or only cares about the most recent. it might be the latter. regardless we couldn't find an existing pbr feature switch15:22
fungithere are also less savory options 3 (recreate the branch from a commit prior to the higher tag and backport the final change from master, though this is non-fast-forwardable), and 4 (delete the higher tag(s) and consider them burned, but that leaves orphaned artifacts and dirty checkouts which still have the tag, and would definitely require cleanup on zuul executors since they need to not see the15:24
fungibad tags when running jobs for the new ones)15:24
*** e0ne has joined #openstack-release15:40
*** e0ne has quit IRC15:40
*** e0ne has joined #openstack-release15:41
*** e0ne has quit IRC15:41
*** ykarel has quit IRC15:42
*** ykarel has joined #openstack-release15:42
*** lbragstad_ has joined #openstack-release15:46
*** e0ne has joined #openstack-release15:48
*** e0ne has quit IRC15:49
hberaudhm 4) could be more misleading than 3).15:50
hberaudthey exist since a while now15:50
*** lbragstad has quit IRC15:50
hberaudPersonnaly I'm more for 2) or 3) while 1) isn't possible15:51
hberaud2) is already on the road15:52
*** sboyron_ has quit IRC15:58
*** EmilienM has quit IRC16:07
*** marios is now known as marios|call16:08
*** EmilienM has joined #openstack-release16:16
*** lbragstad_ is now known as lbragstad16:25
*** marios|call is now known as marios16:42
*** ykarel is now known as ykarel|away16:54
*** ykarel|away has quit IRC17:06
*** marios is now known as marios|out17:07
*** marios|out has quit IRC17:18
*** eolivare has quit IRC17:30
*** gmann is now known as gmann_afk17:40
clarkbfungi: I think if you have this git tree A (11.0.0) <- B <- C (13.0.0) pbr will let you tag B as 11.0.1 or 12.0.0 etc17:53
clarkbthe problem here is trying to tag C with a value < 13.0.017:54
fungiright, which is why option 1 would require changes to pbr and probably at least a temporary config change committed to the branch18:08
fungioption 3 would side-step it by creating a branch where that problem doesn't exist by branching prior to that mess, but wouldn't be fast-forwardable for people consuming the branch18:10
fungioption 1 could maybe be done by merging a change to the existing branch, then manually tagging it with a lower version and not releasing that (because pbr would balk) and then tagging a version higher than that but still lower than the earlier tags through normal automation18:11
fungithat creates a transitional tag with no release artifacts though18:11
*** dtantsur is now known as dtantsur|afk18:39
*** gmann_afk is now known as gmann18:52
openstackgerritBrian Rosmaita proposed openstack/releases master: Release os-brick 4.2.0  https://review.opendev.org/c/openstack/releases/+/77544119:48
openstackgerritNicolas Bock proposed openstack/releases master: Release v9.0.2 of Designate  https://review.opendev.org/c/openstack/releases/+/77544219:48
*** slaweq has quit IRC21:00
*** nweinber has quit IRC22:22
openstackgerritIury Gregory Melo Ferreira proposed openstack/releases master: Release Ironic bugfix/16.2.0 for wallaby  https://review.opendev.org/c/openstack/releases/+/77545623:31

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