Tuesday, 2021-06-22

*** ykarel|away is now known as ykarel04:45
*** ricolin_ is now known as ricolin05:05
*** marios is now known as marios|ruck05:15
*** ysandeep|out is now known as ysandeep06:11
*** gthiemon1e is now known as gthiemonge06:46
*** rpittau|afk is now known as rpittau07:06
*** amoralej|off is now known as amoralej07:14
*** ykarel is now known as ykarel|lunch07:50
opendevreviewchandan kumar proposed openstack/releases master: Release tripleo-operator-ansible-0.5.1  https://review.opendev.org/c/openstack/releases/+/79701008:23
elodillesduring yesterday's ocata-eol 'cleaning' it turned out that python-neutronclient is not tagged. I forgot about this tag-releases job failure: https://zuul.opendev.org/t/openstack/build/69fc52bff367468f9de9ad4713baf33908:35
elodillesthis was an SSH connection timeout again08:35
elodillesfungi hberaud : is it possible to re-schedule this job?08:36
elodilles(if not then I'll prepare a 'delete' + a 're-add' patch)08:37
opendevreviewMark Goddard proposed openstack/releases master: Release rc2 for Kolla projects  https://review.opendev.org/c/openstack/releases/+/79741308:43
hberaudelodilles: good question09:05
hberaudelodilles: I think that yes09:06
hberaud(that it's possible to reenqueue the job)09:07
*** ykarel|lunch is now known as ykarel09:08
elodilleshberaud: ok, let's wait for fungi I guess he can tell/re-enqueue the job :)09:15
hberaudack09:24
opendevreviewHervé Beraud proposed openstack/releases master: Release Openstack-Ansible  https://review.opendev.org/c/openstack/releases/+/79742110:22
opendevreviewHervé Beraud proposed openstack/releases master: Release cinderlib for wallaby  https://review.opendev.org/c/openstack/releases/+/79742210:31
*** ykarel_ is now known as ykarel12:02
*** prometheanfire is now known as Guest18412:25
*** osmanlicilegi is now known as Guest18712:25
*** amoralej is now known as amoralej|lunch12:28
*** ChanServ 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/"12:29
hberaudelodilles: o/ Are you ok to continue with this one? => https://review.opendev.org/c/openstack/releases/+/795652 see my inline comment12:54
elodilleshberaud: sure, let me double-check that everything is in the right place12:57
hberaudsure12:57
hberaudfeel free to +w12:58
opendevreviewMerged openstack/releases master: [fuel] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79565213:09
*** marios|ruck is now known as marios|ruck|call13:10
*** amoralej|lunch is now known as amoralej13:23
*** marios|ruck|call is now known as marios|ruck13:25
*** marios|ruck is now known as marios|ruck|call13:34
fungielodilles: hberaud: i'm looking into it now13:41
hberaudfungi: thanks13:41
elodillesfungi: thanks!13:41
fungissh://release@review.opendev.org:29418/openstack/python-neutronclient.git did not work. Description: ssh: connect to host review.opendev.org port 29418: Network is unreachable13:44
fungiwhen it tried to `git review -s` before pushing the tag, looks like13:44
fungioh, and before that, "fatal: unable to access 'https://opendev.org/openstack/python-neutronclient/': Failed to connect to opendev.org port 443: Connection timed out"13:45
fungilooks like there must have been some sort of networking problem at the time13:46
hberaudso I suppose in this case it make sense to reenqueue the job, isn't?13:46
fungi5 days ago, back on 2021-06-17, so probably not much point in digging further13:46
fungiyeah i think we can reenqueue it13:46
hberaudcool13:46
fungizuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release-post --project=openstack/releases --ref=refs/heads/master --newrev=d527ef063c2d609c6f7e12b9172348aa8916570213:47
fungiis what i ran just now13:48
hberaudthank you13:48
fungii guess keep an eye on the result and make sure it works as expected this time13:48
hberaud+113:48
hberaudsuccessfully tagged13:59
hberaudpublish-tox-docs-releases queued13:59
*** marios|ruck|call is now known as marios|ruck14:00
elodilles\o/14:18
hberaudAnd this last job also successed. Thanks fungi ^ 14:19
hberaudhttps://opendev.org/openstack/python-neutronclient/src/tag/ocata-eol14:19
*** ykarel is now known as ykarel|away14:35
opendevreviewMerged openstack/releases master: Release rc2 for Kolla projects  https://review.opendev.org/c/openstack/releases/+/79741314:41
*** marios|ruck is now known as marios|ruck|call14:44
*** marios|ruck|call is now known as marios|ruck14:44
opendevreviewMark Goddard proposed openstack/releases master: Release Kolla projects for Wallaby  https://review.opendev.org/c/openstack/releases/+/79746714:52
*** ysandeep is now known as ysandeep|out14:57
*** Guest184 is now known as prometheanfire15:10
opendevreviewRiccardo Pittau proposed openstack/releases master: Release ironic 17.0.3 for wallaby  https://review.opendev.org/c/openstack/releases/+/79749915:21
rpittauhi all! Quick question, can release from bugfix branches be handled automatically or we need to request one manual ?15:37
*** gthiemon1e is now known as gthiemonge15:38
*** marios|ruck is now known as marios|out16:00
smcginnisrpittau: I'm not sure I understand the question, but you can do a bugfix release from stable branches like normal releases.16:16
ttxDo we do release from bugfix branches?16:16
rpittausmcginnis: not a bugfix release, a release from a bugfix branch :)16:17
ttxsmcginnis: he means releasing from a bugfix/16.2 branch like defined in 16:17
ttxhttps://review.opendev.org/c/openstack/releases/+/797499/1/deliverables/wallaby/ironic.yaml16:17
rpittauttx: exactly16:17
rpittaufrom bugfix/18.0 to be precise16:17
ttxI think we don't support releasing from those branches... as they conflict with the master/stable releases16:18
ttxtrying to see if there was a precedent16:18
rpittauttx: thanks!16:19
smcginnisI thought we did set those up to do releases, but maybe we settled on manual releases. Completely swapped that out by now. :]16:19
ttxrpittau: a good way would be to try and see if it passes tests16:19
ttxand/or find a precedent :)16:20
ttxbut I can't find any16:21
smcginnisI think I am vaguely remembering that the thought at the time was that we would not be doing new releases from those branches.16:22
smcginnisIt will fail with our validation jobs.16:22
rpittauttx: me neither16:22
smcginnisIIRC, I tried a PoC to see if we could get that to work, but it ended up being way too complex.16:22
rpittauso not even a manual release ?16:22
smcginnisI think the statement from the team at the time was that it shouldn't be needed often, if at all.16:23
smcginnisSo maybe a manual tagging, but nothing official.16:23
rpittauok, I see, thanks smcginnis and ttx 16:24
ttxrpittau: I don;t remember well, tbh16:24
ttxhttps://review.opendev.org/c/openstack/releases/+/739993 is when that was first introduced16:24
ttxhttps://releases.openstack.org/reference/using.html#deliverables-file-schema has the definition for std-with-versions16:26
ttxwhich does not say it's impossible16:26
rpittauyes, that's the very first, I actually did that :)16:26
ttxrpittau: I think, like smcginnis said, that back then we said releases would be rare, but possible. looks like this one would be the first one16:26
ttxSo if you really want it you can push a change and see what tests say :)16:27
smcginnisAbility added here: https://opendev.org/openstack/releases/commit/804e5608327d24b791e3eedaf1e8d961c3fe8f4716:27
ttxso... maybe it just works™16:28
ttxI change my answer from "no way" to "you're brave, my young padawan, entering the cave"16:29
smcginnisIronic change: https://review.opendev.org/c/openstack/ironic-specs/+/72554716:29
rpittaualthough we don't have a "bugfix" dir under deliverables, I guess we need to create that?16:29
rpittauand lol16:29
rpittauyep16:29
rpittauI know the history, I was there :D16:29
dtantsurpreviously we would ask one of you to do a release manually16:30
dtantsurif that has changed, I'm glad16:30
ttxdtantsur: to the rescue16:30
dtantsur:)16:31
ttxyeah, the bugfix directory question makes me think there is no way that's supported by the automation16:31
ttxsince we did not add that to it yet16:31
ttxso manual release it is16:31
rpittauok :)16:31
dtantsurI think we've done it at least twice before :)16:31
dtantsurso yeah, these are not frequent16:31
TheJulia++16:32
ttxthat's what you get by asking the old people on the bench rather than our fearless leader16:32
ttxwe just try to remember but then our lack of fresh neurons shows16:32
dtantsur:D16:32
dtantsuror rather: we all need a break. a lot of it.16:33
ttxso... maybe just send an email to openstack-discuss with [release] on subject and it will get hberaud's attention16:34
rpittauttx: sounds good, thanks :)16:34
TheJuliaa nice, long break... on a beach... sipping delicious beverages16:35
rpittauin 49 days and 5 hours16:36
TheJulia:)16:36
*** rpittau is now known as rpittau|afk17:11
hberaudrpittau|afk, ttx, smcginnis: ack17:27
*** amoralej is now known as amoralej|off17:31
hberaudttx, smcginnis: So, if I summarize, it is possible to release "manually" those bugfix branches by proposing a patch. Here is a patch example => https://review.opendev.org/c/openstack/releases/+/739993 , I'm right?17:34
*** iurygregory_ is now known as iurygregory18:39

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