Monday, 2021-04-12

*** tosky has quit IRC00:00
*** brinzhang has joined #openstack-release01:02
*** iurygregory has quit IRC01:05
*** evrardjp has quit IRC02:33
*** evrardjp has joined #openstack-release02:33
*** brinzhang_ has joined #openstack-release04:00
*** brinzhang has quit IRC04:03
*** jrosser has quit IRC04:20
*** jrosser has joined #openstack-release04:34
*** vishalmanchanda has joined #openstack-release04:41
*** ricolin has joined #openstack-release04:41
*** ykarel has joined #openstack-release04:56
*** whoami-rajat_ has joined #openstack-release05:36
*** sboyron has joined #openstack-release05:52
*** slaweq has joined #openstack-release06:09
*** eolivare has joined #openstack-release06:23
*** eolivare has quit IRC07:07
*** e0ne has joined #openstack-release07:09
*** eolivare has joined #openstack-release07:09
*** xinranwang has joined #openstack-release07:29
*** tosky has joined #openstack-release07:35
*** jbadiapa has joined #openstack-release07:37
*** rpittau|afk is now known as rpittau08:04
openstackgerritMerged openstack/releases master: Improve R-3 and R-2 documentation  https://review.opendev.org/c/openstack/releases/+/78410308:47
openstackgerritMerged openstack/releases master: Release horizon 19.2.0 (wallaby)  https://review.opendev.org/c/openstack/releases/+/78565908:47
*** brinzhang_ is now known as brinzhang08:55
*** dtantsur|afk is now known as dtantsur08:56
openstackgerritMartin Chacon Piza proposed openstack/releases master: Release monasca-ui 1.17.2 (stable/train)  https://review.opendev.org/c/openstack/releases/+/78584210:02
*** e0ne has quit IRC10:32
*** whoami-rajat_ is now known as whoami-rajat10:33
hberaudI think that we have an issue here => https://opendev.org/openstack/releases/blame/branch/master/deliverables/wallaby/puppet-freezer.yaml#L2810:43
hberaudversion moved from 7.3.0 to 18.4.010:44
hberaudI wonder if we should remove that version10:45
hberaudI also noticed that the tarball wasn't generated => https://tarballs.opendev.org/openstack/puppet-freezer/puppet-freezer-18.4.0.tar.gz10:46
elod:S10:51
elodwhat was usually done in this case in the past?10:51
hberaudI don't know10:53
hberaudPersonally, I have not yet had the opportunity to witness a similar case10:55
hberaudI would argue that we could remove that version (from pypi) and then recreate a 7.4.0 as surely expected10:56
hberaudpuppet-* are trailing projects10:56
hberaudSo, I guess this will minimize the side effects of removing a version10:57
hberaudttx, fungi: FYI ^ . summary: A bad version number have been released for puppet-freezer (18.4 instead of 7.4) and the associated tarball (18.4) doesn't exist (haven't been created)10:59
hberaudCan we remove that version and realign things properly?11:00
hberaudI also informed the author of these changes about the situation, but I didn't get feedback for now11:01
hberaudthe tarball signature is also missing => https://tarballs.openstack.org/puppet-freezer/puppet-freezer-18.4.0.tar.gz.asc11:02
*** brinzhang_ has joined #openstack-release11:05
*** brinzhang has quit IRC11:08
*** iurygregory has joined #openstack-release11:11
*** dhellmann_ has joined #openstack-release11:44
*** dhellmann has quit IRC11:45
*** dhellmann_ is now known as dhellmann11:45
fungiare you asking about trying to delete a git tag?11:48
ttxWe can remove the deliverable file entry from openstack/releases, we can't really remove the tag11:57
ttxAlternate solution is to own it and jump to 18.4, and re-release11:58
ttxbut with the tarball not created I would lean toward the former solution11:59
hberaudfungi: yes, I ask about trying to remove deleted artifacts that refer to 18.4.0 (git tag, pypi (I think it's not the case here), etc...)12:18
hberaudttx: which is the former solution? remove the file entry and re-release?12:20
*** nweinber has joined #openstack-release12:31
smcginnisThe puppet team would occasionally want to "re-align" their release numbers to match up with other artifacts. We've pushed back in the past, but technically there is no reason they can't do that. Other than it being kind of odd to the end consumer to go from 7.x to 18.x.12:34
smcginnisIf that was intended, of course.12:34
hberaudI think it's a mistake here12:35
hberaudAll other puppet deliverables follow the same pattern and so were updated to 7.4.012:35
priteauHello. I have just noticed that python-cloudkittyclient release notes are missing. I don't know if this is a new problem or not. https://docs.openstack.org/releasenotes/python-cloudkittyclient12:38
priteauI don't remember where this is configured?12:38
priteauNo release-notes-jobs-python3 job, that could be it12:42
openstackgerritHervĂ© Beraud proposed openstack/releases master: Fix puppet-freezer missing tarball  https://review.opendev.org/c/openstack/releases/+/78586612:44
hberaudpriteau: yes that could be that12:45
hberaudpriteau: if I take example on oslo.messaging this job is present and relnote are well produced => https://opendev.org/openstack/oslo.messaging/src/branch/master/.zuul.yaml#L11412:46
ttxhberaud: the former = just remove the deliverable file entry from openstack/releases12:46
priteauSubmitted https://review.opendev.org/c/openstack/python-cloudkittyclient/+/78586712:46
priteauI guess they've been unpublished forever12:46
hberaudpriteau: I think too else we will get something similar => https://docs.openstack.org/releasenotes/oslo.messaging/12:47
hberaud(all series relnotes index)12:47
priteauWhat's going on with the strange formatting of the list?12:47
hberaudttx: the problem is that stable/wallaby refer to 18.4.0 I don't think that our tooling will love that12:48
hberaudI just proposed a patch to discuss about that ^12:48
priteauhberaud: I submitted a patch to fix the formatting in olso.messaging release notes index12:52
hberaudpriteau: thanks12:52
priteauThere are other oslo libs with the same issue. Anyway, sorry for hijacking the conversation.12:53
hberaudpriteau: np12:53
ttxhberaud: if stable/wallaby mentions it I would just consider they jumped13:39
ttxso +1ed the patch13:40
*** e0ne has joined #openstack-release13:45
*** sboyron has quit IRC14:06
*** sboyron has joined #openstack-release14:07
hberaudthanks14:07
hberaudfungi: let us know if that proposed solution is something feasible from your point of view => https://review.opendev.org/c/openstack/releases/+/785866/1#message-578cf6cd91a94e32478be3986767dbf59206cd8514:16
ttxhberaud: yeah I guess we could delete the branch in git, then recreate it on 7.4.0... There would still be a 18.4.0 tag in git though, which we'll have to remember to skip14:18
fungithat should work fine14:19
ttxSo solution 1 would be to bump the metadata.json file to 18.5.0 and release 18.5.0.14:19
ttxSolution 2 would be to remove the stable/wallaby branch created on 18.4.0, ckean up the deliverable file, then push a 7.4.0 instead14:20
hberaudtkajinam: ^14:20
ttx(with stable/wallaby created on it)14:20
ttxSlight preference for (2), but I could go either way14:20
hberaudif recreate stable/wallaby is something feasible then +1 for (2) too14:21
*** ykarel has quit IRC14:21
ttxhmm, 7.4.0 was released on puppetforge apparently14:21
hberaudyeah their metadata produced that version14:22
ttxso solution 2 would be to bump the metadata.json file to 7.4.1, remove the stable/wallaby branch created on 18.4.0, ckean up the deliverable file, then push a 7.4.0 instead (with stable/wallaby created on it)14:22
ttxpush a 7.4.1*14:22
hberaudyes14:22
ttxthat way we'll have a 7.4.1 consistent everywhere14:23
hberaudyes14:23
ttxand just a trash tag on the git repo (but would not be our first)14:23
*** ykarel has joined #openstack-release14:24
tkajinamif we can't remove 18.4.0 tag created in git repo then I feel bumping the version to 18.5.0 sounds like the better solution14:24
tkajinamto avoid any confusion caused by 18.4.0 in our repo14:24
hberaudas you want14:25
hberaudboth are feasible14:25
fungialso keep in mind that if the 18.4.0 tag is on a commit which appears in the history of another branch, it will still show up in that branch's history14:26
fungiyeah, the commit tagged as 18.4.0 is in the master branch history14:28
fungiso that tag will be in the history of any new branches created from master at or after that commit14:28
elodjust out of curiosity: is the branch cut connected to a tag or a commit hash?14:30
fungieverything in git is attached to a commit id14:31
hberaudboth are possible14:31
fungieven if you reference the branch point by a tag, that's just dereferenced to a commit14:31
hberaudyes14:31
elodI see, thanks. (I was thinking whether it's really possible to keep the hash 2249c4fbae362ec4862ab039903b943c5a13781b and only change the tag from 18.4.0 to 7.4.0, so in my understanding we don't even have to delete and recreate the branch)14:33
tkajinamhberaud, I have submitted a commit to bump version in metadata https://review.opendev.org/c/openstack/puppet-freezer/+/785613 https://review.opendev.org/c/openstack/puppet-freezer/+/78588614:35
tkajinamhberaud, once these are merged then we can create 18.4.1 release from that hash14:35
hberaudthanks tkajinam14:35
hberaudok14:35
tkajinamthen the current inconsistency is supposed to be fix... I'll ask some feedback from other cores in puppet14:35
hberaudok14:36
fungielod: it wouldn't be "changing" the tag, but rather adding a second tag referencing that same commit14:38
fungigit would just report both tags for that commit in the history of the stable/wallaby branch (and also in the master branch history since the commit is present there as well)14:39
elodfungi: indeed. by "changing" I meant that in the release release repo in puppet-freezer.yaml, and in reality there would be two tags. anyway, as I see it's settled, so it was only a theory from me :)14:45
openstackgerritTakashi Kajinami proposed openstack/releases master: Recreate puppet-freezer release with the consistent version  https://review.opendev.org/c/openstack/releases/+/78590015:10
*** ykarel is now known as ykarel|away15:19
*** ykarel|away has quit IRC15:33
*** e0ne has quit IRC15:36
*** xinranwang has quit IRC15:46
*** nweinber_ has joined #openstack-release15:57
*** nweinber has quit IRC15:58
*** vishalmanchanda has quit IRC16:10
*** armstrong has joined #openstack-release16:42
*** rpittau is now known as rpittau|afk16:59
openstackgerritMarios Andreou proposed openstack/releases master: TripleO client and common repos release and branch stable/wallaby  https://review.opendev.org/c/openstack/releases/+/78567017:04
*** dtantsur is now known as dtantsur|afk17:06
*** sboyron has quit IRC17:21
*** sboyron has joined #openstack-release17:21
*** eolivare has quit IRC18:00
*** sboyron has quit IRC18:41
openstackgerritJohn Fulton proposed openstack/releases master: Wallaby cycle highlight update for TripleO Ceph version  https://review.opendev.org/c/openstack/releases/+/78595518:55
*** toabctl has quit IRC19:36
*** toabctl has joined #openstack-release19:37
*** whoami-rajat has quit IRC19:55
*** slaweq has quit IRC20:38
*** nweinber_ has quit IRC20:39
*** slaweq has joined #openstack-release20:41
*** slaweq has quit IRC21:53
*** tosky has quit IRC23:24

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