Tuesday, 2020-12-15

*** tosky has quit IRC00:10
*** icey has quit IRC00:23
masayukighi release team, we're struggling with reno. It seems that reno can't find the 25.0.0 tag in tempest. Any thoughts on this? https://review.opendev.org/c/openstack/tempest/+/75278600:27
openstackgerritSteve Baker proposed openstack/releases master: Release metalsmith 1.4.0 for wallaby  https://review.opendev.org/c/openstack/releases/+/76706000:48
*** armax has quit IRC02:39
*** ykarel has joined #openstack-release04:26
*** vishalmanchanda has joined #openstack-release05:04
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** brinzhang has joined #openstack-release05:55
*** brinzhang has quit IRC07:10
*** brinzhang has joined #openstack-release07:10
*** icey has joined #openstack-release07:42
*** sboyron has joined #openstack-release07:55
*** slaweq has quit IRC07:56
*** slaweq has joined #openstack-release07:58
*** rpittau|afk is now known as rpittau08:06
hberaudmasayukig: I looking for details08:26
masayukighberaud: thank you so much!08:27
hberaudmasayukig: you're welcome08:28
hberaudmasayukig: apparently you haven't even reno for victoria https://docs.openstack.org/releasenotes/tempest/victoria.html08:30
hberaudmasayukig: ah wait... it's maybe because you are branchless08:32
masayukighberaud: yeah, tempest is branchless08:34
hberaudmasayukig: the logs of build-openstack-releasenotes ( https://zuul.opendev.org/t/openstack/build/314be05d54ef429d85aa5d4fdbcbec9d ) are too old, I can't access them08:35
hberaudmasayukig: can we retry to rebase this patch (by example) to trigger a new execution and get fresh logs?08:36
masayukighberaud: sorry about that. yeah, it should be OK08:37
hberaudmasayukig: no problem08:37
masayukighberaud: just rebased08:40
hberaudmasayukig: thanks08:41
*** tosky has joined #openstack-release08:41
hberaudmasayukig: let's wait a bit for fresh logs08:42
masayukighberaud: yeah, btw, FWIW, I dug a bit on the comment. But I'm still 100% not sure. https://review.opendev.org/c/openstack/tempest/+/752786/2#message-150bc4adf0ca3d82c2068eaad87f7c0045306dea08:43
* hberaud read08:45
hberaudmasayukig: apparently you're right only merge commits are retrieved08:49
hberaudmasayukig: all these SHAs seems to matches with the outcome of "git log --oneline --merges "08:51
masayukighberaud: yeah, is that expected behavior?08:51
hberaudmasayukig: I don't know sorry... maybe someone more involved than me within reno (dhellmann by example) can answer your question08:54
masayukighberaud: thanks, no worries. Do you think it's good to bring this to the openstack-discuss ML?08:56
hberaudmasayukig: hm maybe we can wait for reply of someone more experienced on reno before triggering a ML discussion08:58
hberaudmasayukig: also I'll try to dig a bit into reno before08:58
masayukighberaud: thanks! sure. I'm going to call it a day soon, actually. But I'll check the irc log later09:01
hberaudack thanks09:07
hberaudmasayukig: here is the delta of changes added to reno since your latest release note on tempest => http://paste.openstack.org/show/801041/09:15
*** e0ne has joined #openstack-release09:15
*** vishalmanchanda has quit IRC10:22
*** rpittau is now known as rpittau|bbl10:27
*** vishalmanchanda has joined #openstack-release10:30
*** dtantsur|afk is now known as dtantsur11:00
openstackgerritRiccardo Pittau proposed openstack/releases master: Release bifrost 10.0.0 for wallaby  https://review.opendev.org/c/openstack/releases/+/76712112:00
*** ricolin has quit IRC12:09
*** ykarel_ has joined #openstack-release12:14
*** ykarel has quit IRC12:17
openstackgerritHervĂ© Beraud proposed openstack/releases master: Replace series name by template variable  https://review.opendev.org/c/openstack/releases/+/76712812:44
openstackgerritHervĂ© Beraud proposed openstack/releases master: Remove useless canary tests  https://review.opendev.org/c/openstack/releases/+/76712912:52
*** rpittau|bbl is now known as rpittau13:12
*** brinzhang has quit IRC13:21
*** brinzhang has joined #openstack-release13:22
*** brinzhang has quit IRC13:23
*** brinzhang has joined #openstack-release13:23
*** ykarel_ is now known as ykarel13:23
dhellmannmasayukig , hberaud : I think I missed part of the conversation about reno. What is happening?13:48
*** vishalmanchanda has quit IRC13:52
hberauddhellmann: apparently the releasenotes job fail on tempest with the latest version that they try to generate https://review.opendev.org/c/openstack/tempest/+/75278613:54
hberauddhellmann: they got timeout due to something like => 'unable to find release notes file associated with unique id '27000c02edc5a112', skipping' https://zuul.opendev.org/t/openstack/build/3834bae67c3f43b0af82ae525c6eb652/log/job-output.txt13:55
dhellmannis there a tag with that version number?13:56
hberauddhellmann: yes the tag exist13:57
dhellmannthis error means that sphinx didn't find it on the branch it was told to scan https://zuul.opendev.org/t/openstack/build/3834bae67c3f43b0af82ae525c6eb652/log/job-output.txt#64813:57
hberauddhellmann: https://opendev.org/openstack/tempest/src/tag/25.0.013:57
dhellmannoh, no, that's not right. it did find it, there just aren't any release notes13:57
*** jbadiapa has joined #openstack-release13:58
dhellmannlet me see if I can reproduce this13:58
hberauddhellmann: ack. FYI this morning I asked them to rebase that patch to trigger a new execution of that job and get fresh logs and [1] is the outcome of that [1] https://zuul.opendev.org/t/openstack/build/3834bae67c3f43b0af82ae525c6eb652/log/job-output.txt14:00
hberauddhellmann: previous logs expired and weren't available anymore14:00
hberauddhellmann: thanks for your help14:01
openstackgerritGhanshyam proposed openstack/releases master: Release Tempest 26.0.0  https://review.opendev.org/c/openstack/releases/+/76716314:32
openstackgerritGhanshyam proposed openstack/releases master: Release Patrole 0.11.0  https://review.opendev.org/c/openstack/releases/+/76716414:34
*** sboyron has quit IRC14:56
*** ykarel has quit IRC15:01
dhellmannhberaud, masayukig : the 25.0.0 tag is not on the master branch, it is on a commit that was merged into the master branch. reno therefore does not consider it as "inline" between 24.0.0 and HEAD so it does not put any of the release notes into that version15:04
dhellmannI thought the release machinery prevented this sort of error but I guess not15:04
hberauddhellmann: good to know that15:04
dhellmannin any case, I suggest tagging 25.0.1 on 94a76091f15:05
*** armax has joined #openstack-release15:06
hberaudack, thanks for these details, FYI gmann ^15:06
gmanndhellmann: hberaud i see thanks. I will push 25.0.1 on 94a76091f15:12
hberaudgmann: ack, thanks15:12
*** sboyron has joined #openstack-release15:14
gmanndhellmann: hberaud  but i did not get 'the 25.0.0 tag is not on the master branch, it is on a commit that was merged'15:15
gmannit is released on c8d7a01014d4b82dd9960679db5e77dc31f4d87a right15:16
hberaudgmann: yes and master contains c8d7a01014d4b82dd9960679db5e77dc31f4d87a15:16
dhellmannif you look at the 'git log --decorate --graph' output and search for the tag, you'll see that it's on a commit that is then merged into the master branch. reno's toplogical sort isn't smart enough to realize that that means it is on the branch it was merged into15:16
dhellmannthe other commit I mention is the merge commit where the tagged commit is brought into the master branch15:17
hberaudif I correctly understand the release should have been on 94a76091f616a4e4a46534b82d4974534d19764315:18
hberaudto avoid this situation, right?15:19
hberaudwhere 94a76091f616a4e4a46534b82d4974534d197643 is the merge commit related to c8d7a01014d4b82dd9960679db5e77dc31f4d87a15:19
dhellmannyes that's right15:20
dhellmannit is OK to tag the left-hand child of a merge, but not the right-hand child15:20
hberaudok make sense to me15:20
hberaudI'll take a further look to our mechanismes to see why we didn't see that15:21
gmanndhellmann: hberaud  but does it cause issue always? I remember we might have release few old version with 'commit on master' ?15:24
dhellmannif any of the other versions were tagged this way they would have produced the same error15:24
hberaudhowever I don't expect that we can rely on the related jobs logs (https://review.opendev.org/c/openstack/releases/+/752665) as this was released 2 months ago and the logs expired too15:25
dhellmannthis behavior is a fundamental part of some of the oldest code in reno, so it's not a new change. the reason you're seeing it now is that you're explicitly asking for details about 25.0.0 with the changes in https://review.opendev.org/c/openstack/tempest/+/75278615:25
dhellmannif you run `reno report .` from a clean checkout of tempest it does not show the 25.0.0 version even though the tag is there, because reno does not consider any of the release notes to be "in" that release15:26
dhellmannthat KeyError should be wrapped with a more clear message about having been asked for a version that has no data15:27
hberaudon the release side I'll try to reproduce a similar scenario locally or a "DNM" patch to see what's happen and see if we can raise some warnings in this kind of situation15:28
gmannTempest 22.0.0 is released same way on 13c190d62e4c4596339eeee93eb0425cd525d71f but reno did not cause issue15:28
dhellmannI really thought the validation code had logic to prevent this because we had some early releases early on that came from the wrong branch. It may only be looking at the output of `git branch --contains` though, and that's not sufficient for this specific error15:29
hberaudack15:29
dhellmanngmann : in the graph output 22.0.0 is not the right-hand child of a merge15:30
dhellmannsee the difference in the graph structure in http://paste.openstack.org/show/801062/15:31
dhellmannline 10 is the 22.0.0 tag and line 22 is 25.0.015:32
dhellmannyou only ever want to tag releases from commits with the * in the left column of the graph output15:32
gmanndhellmann: and that depends on the timing of the release (if we release with the 'commit on master')? that is why 22.0.0 is on left-hand child ?15:35
dhellmannif you always tag HEAD, it will be fine. if you tag an "old" commit, you have to be careful15:36
gmanni see.15:36
dhellmannthat's why the new-release command in the release repo defaults to whatever it sees as HEAD at the point that you run it15:37
*** markmcclain has joined #openstack-release15:38
*** jbadiapa has quit IRC15:40
*** jbadiapa has joined #openstack-release15:41
gmanndhellmann: thanks for the clarification. I think this is one good thing to learn today :)15:44
dhellmanncongratulations on finding an obscure bug! ;-)15:45
gmann:)15:45
gmannjust wondering if we can autodetect this in in release tooling ?15:45
dhellmannI expect so. Like I said above, I think the check today is using `git branch --contains` to ensure that a commit being tagged is on the right branch, but we would need another check to verify the relative position of that commit and any merge commit that pulls it in, if there is one15:47
*** sboyron has quit IRC15:51
*** sboyron has joined #openstack-release15:52
openstackgerritGhanshyam proposed openstack/releases master: Release Tempest 25.0.1  https://review.opendev.org/c/openstack/releases/+/76718015:53
*** e0ne has quit IRC17:11
*** dtantsur is now known as dtantsur|afk17:29
*** rpittau is now known as rpittau|afk17:46
*** e0ne has joined #openstack-release18:48
*** e0ne has quit IRC20:22
*** sboyron has quit IRC21:02
*** e0ne has joined #openstack-release21:02
*** e0ne has quit IRC21:03
*** jbadiapa has quit IRC21:06
*** trident has quit IRC21:56
*** trident has joined #openstack-release22:00
masayukigdhellmann: hberaud gmann thanks for the clarification!23:00
masayukiggmann: thanks. +1 for the 25.0.1 patch23:05
*** slaweq has quit IRC23:32

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