Monday, 2021-01-04

*** brinzhang0 has joined #openstack-release00:09
*** tosky has quit IRC00:12
*** brinzhang_ has quit IRC00:13
*** armax has quit IRC00:24
*** armax has joined #openstack-release00:32
*** armax has quit IRC00:33
*** armax has joined #openstack-release00:44
*** armax has quit IRC01:27
*** brinzhang_ has joined #openstack-release01:42
*** brinzhang0 has quit IRC01:45
*** armax has joined #openstack-release01:47
*** armax has quit IRC01:51
*** ricolin_ has joined #openstack-release02:27
*** ricolin_ has quit IRC02:34
*** ricolin_ has joined #openstack-release02:34
*** ricolin_ has quit IRC03:04
*** ricolin_ has joined #openstack-release04:01
*** ricolin_ has quit IRC04:07
*** ricolin_ has joined #openstack-release04:08
*** ykarel has joined #openstack-release05:13
*** ykarel_ has joined #openstack-release05:32
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** ykarel has quit IRC05:34
*** ykarel_ is now known as ykarel05:35
*** fnordahl has joined #openstack-release06:01
*** vishalmanchanda has joined #openstack-release06:14
*** whoami-rajat__ has joined #openstack-release06:39
*** cgoncalves has joined #openstack-release07:27
*** ricolin_ has quit IRC07:27
*** ricolin has joined #openstack-release07:27
*** gibi_pto is now known as gibi07:58
*** e0ne has joined #openstack-release07:58
*** slaweq has joined #openstack-release08:09
*** e0ne has quit IRC08:15
*** sboyron has joined #openstack-release08:27
*** vishalmanchanda has quit IRC08:34
*** tosky has joined #openstack-release08:35
*** rpittau|afk is now known as rpittau08:51
*** brinzhang0 has joined #openstack-release08:56
*** brinzhang_ has quit IRC08:59
*** icey has quit IRC09:19
*** icey has joined #openstack-release09:25
*** slaweq has quit IRC09:31
*** slaweq has joined #openstack-release09:33
*** e0ne has joined #openstack-release10:04
*** e0ne has quit IRC10:05
openstackgerritMerged openstack/releases master: Release os-win 5.4.0 (Wallaby)  https://review.opendev.org/c/openstack/releases/+/76767410:10
*** dirk1 is now known as dirk10:18
openstackgerritMerged openstack/releases master: TripleO repos feature release for stable/victoria  https://review.opendev.org/c/openstack/releases/+/76823710:24
ttxI've been holding on the tempest EM patches so that we discuss it first10:30
hberaudHNY to everyone!10:30
hberaudttx: yes I seen thanks10:30
ttxHappy new year to you too!10:30
hberaudttx: I already added this one to our next meeting agenda10:31
ttxOn Dec 18 there was a release job failure around https://review.opendev.org/c/openstack/releases/+/76768610:31
ttxLogs at https://zuul.opendev.org/t/openstack/build/cc76b45601184d6484c5783b550a0951/console10:31
ttxWas it investigated already?10:31
hberaudyes we already discussed about this with fungi the OSA team10:32
ttxwhat was the issue? /home/zuul/scripts/release-tools/add_release_note_page.sh: line 51: python: command not found ?10:32
hberaudWe think that a project-config script doesn't behave as expected10:32
hberaudlemme find the link10:33
ttxIt seems to have mostly branched as requested, so probably not critical10:33
ttxMaybe we can track progress in the meeting, just don;t want it to fall in post-holidays cracks10:33
ttxhttps://zuul.opendev.org/t/openstack/build/9927456740bf4287ad980af9482b2111/console looks like a similar issue10:35
hberaudyes we investigated and everything seems to have been created as expected, unfortunately the script doesn't behave as expected especially this part https://opendev.org/openstack/project-config/src/branch/master/roles/copy-release-tools-scripts/files/release-tools/process_release_requests.py#L110-L116 and so we didn't caught the error properly10:41
hberaudConcerning the last release job failure I suppose this one is due to the fact that we branched in the same time that we created a new tag, please can you double check? => http://lists.openstack.org/pipermail/release-job-failures/2020-December/001499.html10:41
hberaudit was related to these changes => https://review.opendev.org/c/openstack/releases/+/76800810:41
hberaudthe following command "git checkout stable/victoria" returned "error: pathspec 'stable/victoria' did not match any file(s) known to git"10:42
hberaudbut everything was created as expected (tag, branch) too, only the release note is wrong and I think it's due to the fact that we skipped the doc job due to the rc code10:42
hberaudso the 22.0.0rc1 appear under the unreleased section instead of the victoria section of reno (c.f https://docs.openstack.org/releasenotes/openstack-ansible/unreleased.html)10:42
hberaudI already added this topic to our next meeting10:43
ttxyeah, that seems like a fair analysis10:43
hberaudhowever I suppose we need to reenque the doc part10:44
hberaudto move 22.0.0rc under victoria10:44
ttxbranching and tagging at the same time should work10:44
ttxthat pathspec error is, I think, expected10:45
hberaudbut we got a rc>010:46
ttx/home/zuul/scripts/release-tools/add_release_note_page.sh: line 51: python: command not found10:47
ttxis more likely to blame10:47
hberaudah I missed this one10:49
hberaudexact10:49
ttxwe should get rid of that other message, it's been misleading me regularly too10:50
hberaudyes10:53
ttxlooking at where it originates since I have the tabs open now :)10:53
hberaudI can't find this script10:53
hberaudWhere I can find it?10:54
ttxstill digging10:54
hberaudI suppose we just need "python3" rather than "python" somewhere10:54
ttxit starts from release.sh https://opendev.org/openstack/project-config/src/branch/master/roles/copy-release-tools-scripts/files/release-tools10:54
hberaudhttps://opendev.org/openstack/project-config/src/branch/master/roles/copy-release-tools-scripts/files/release-tools/add_release_note_page.sh#L5110:55
ttxoh sure, I'm trying to find where the spurious error comes from10:55
ttx(pathspec 'stable/victoria' did not match any file(s) known to git)10:55
hberaudah10:56
hberaudsorry :)10:56
* hberaud school run10:56
ttxok got it10:58
ttxhttps://opendev.org/openstack/project-config/src/branch/master/roles/copy-release-tools-scripts/files/release-tools/clone_repo.sh#L19710:58
ttx(git checkout $BRANCH || git checkout master) && retry git pull --ff-only)10:58
ttxgit checkout $BRANCH is expected to fail in some cases, thus activating the "|| git checkout master"10:59
ttxBut in that case it logs a spurious error11:00
ttxWe probably should (git checkout $BRANCH 2>/dev/null || ... or even better expand that code and properly log in that case11:03
hberaud+1 to expand11:03
ttxI'll try to find time to do it... but not today :)11:04
hberaudack np11:04
hberaudon my side I'll propose "python3" rather "python"11:04
hberaud*than11:04
hberaudit seems that this one was forgotten, I can see that other scripts of "roles" already use python3 => https://opendev.org/openstack/project-config/src/branch/master/roles/copy-release-tools-scripts/files/release-tools/release.sh#L9711:10
hberauddone by https://review.opendev.org/c/openstack/project-config/+/76912811:17
*** slaweq has quit IRC12:18
*** slaweq has joined #openstack-release12:20
*** ykarel has quit IRC12:33
hberaudwell... a freshly release job failure related to https://review.opendev.org/c/openstack/releases/+/768237 just poped up, it seems related to the new pip's resolver12:33
*** ykarel has joined #openstack-release12:33
hberaudhttp://paste.openstack.org/show/801385/12:34
hberaudthe first of 2021... http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html12:35
*** ykarel_ has joined #openstack-release12:37
*** ykarel has quit IRC12:37
hberaudI suppose we didn't see this error previously as the previous jobs all failed for various reasons and the publish reno/doc's job wasn't triggered due to these fails12:38
fungiif it ran in a python3-based virtualenv/venv it would have been unnoticed13:04
*** ricolin has quit IRC13:06
*** haleyb has quit IRC13:24
*** haleyb has joined #openstack-release13:27
*** tosky has quit IRC13:30
*** tosky has joined #openstack-release13:30
*** dave-mccowan has quit IRC13:52
*** CrayZee has quit IRC13:53
*** snapiri has joined #openstack-release13:53
*** dave-mccowan has joined #openstack-release13:54
fungithe script call i mean13:58
fungihberaud: that resolver conflict looks pretty typical, we've been hitting it in places where we install things not covered by the global upper-constraints.txt in openstack/requirements, so lower-constraints jobs as well as linters and static analysis tools which we don't cover globally13:59
hberaudfungi: you speak about http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html , right?14:00
fungihberaud:14:01
fungier, hberaud yes14:01
hberaudack14:01
fungiprobably just need to tweak the test-requirements.txt entries a bit14:02
hberaudfrom openstack/release?14:02
hberaudI guess yes14:03
fungihberaud: i think it's trying to install https://opendev.org/openstack/tripleo-image-elements/src/branch/master/test-requirements.txt14:04
fungiprobably the version of flake8 hacking wants is incompatible with the pyflakes pin in there14:04
hberaudIIUC, that mean that potentially we could face similar issue with all the repos14:06
fungii'm not entirely sure why the job installs the project's test-requirements.txt instead of, say, doc/requirements.txt14:06
fungi(clearly things like hacking and pyflakes aren't needed to generate release notes)14:07
hberaudit would be terrible if it is the case14:07
hberaudmaybe it's because this project haven't doc/requirements.txt14:08
hberaudmaybe it's a default rule... I don't know14:09
fungiyeah, this is where it decides to use test-requirements.txt: https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L3614:10
fungii'll bring it up in #zuul, seems like a questionable choice, or at least something we'd like to be able to override14:10
hberaudthanks14:10
fungioh!14:10
fungii misread that. so it _will_ use doc/requirements.txt if it exists, and only fall back to test-requirements.txt if not14:11
hberaudyes a break will be triggered if the file exist14:12
fungiif tripleo-image-elements adds a more focused doc/requirements.txt file with just their docs (and release notes) deps then this would work much more reliably and faster14:12
hberaudbut in all the case that mean that all repos should be fixed/standardized first to avoid similar issue14:13
fungisure. that's basically what we're finding with the new dep solver in pip, it's pointing out actual errors in our projects and highlighting places where we've been inconsistent/sloppy up to now14:13
hberaudack14:14
fungiso in the case of tripleo-image-elements, 1. they have an incompatibility between entries in their test-requirements.txt, and 2. they're missing a doc/requirements.txt file14:15
fungiboth things worth fixing14:15
fungianyway, i need to go run some errands, but will be back in an hour14:15
hberaudI'll try to get a list of identified repos that need to be fixed by using beagle14:16
hberaudbeagle search --ignore-comments -f link --file '(^test-requirements.txt)' --repo-pattern "openstack/*" 'sphinx'14:17
hberaudsomething like this should works ^14:17
hberaudif we consider that sphinx should be present in doc/requirements.txt14:18
hberaudby example with PyCADF it seems to works as expected https://opendev.org/openstack/pycadf14:19
hberaudhttps://opendev.org/openstack/pycadf/src/branch/master/test-requirements.txt#L1614:19
hberaudand the doc/requirements.txt doesn't exist14:19
hberaudall these repos seems fit our search => http://paste.openstack.org/show/801396/14:24
hberaudnow I need to check if a doc/requirements.txt file exist or not in thel14:24
hberaudthem14:25
hberaudttx, smcginnis: Please hold all the validations for now14:47
ttxack14:47
*** ykarel_ has quit IRC15:26
*** ykarel_ has joined #openstack-release15:55
iurygregoryhberaud, I will push some patches to ironic projects (sushy, sushy-tools, virtualbmc, ironic-python-agent-builder)15:56
hberaudiurygregory: related to the doc issue?15:56
iurygregoryyeah15:57
hberaudiurygregory: awesome thanks15:57
iurygregorynp =)15:57
*** ykarel_ has quit IRC16:03
*** slaweq has quit IRC16:19
*** slaweq has joined #openstack-release16:20
iurygregoryhberaud, https://review.opendev.org/c/openstack/virtualbmc/+/769160 would be something like this right?16:23
*** armax has joined #openstack-release16:36
hberaudiurygregory: I replied directly on https://review.opendev.org/c/openstack/virtualbmc/+/76916016:52
hberaudiurygregory: but yes it would be something like this16:53
iurygregoryhberaud, I did the clean-up locally (just trying to get pdf-build working because I'm using a new notebook hehe)16:53
hberaud:)16:55
*** slaweq has quit IRC17:13
*** rpittau is now known as rpittau|afk17:14
*** slaweq has joined #openstack-release17:15
openstackgerritHervĂ© Beraud proposed openstack/releases master: Add doc related to validation status (red, orange, green)  https://review.opendev.org/c/openstack/releases/+/76917117:28
*** diablo_rojo has joined #openstack-release17:47
*** e0ne has joined #openstack-release18:40
*** e0ne has quit IRC18:55
*** e0ne has joined #openstack-release18:57
*** e0ne has quit IRC18:57
nicolasbockhberaud: I am trying to get `designate-tempest-plugin` up to speed in terms of pip resolver issue and submitted https://review.opendev.org/c/openstack/designate-tempest-plugin/+/76917018:59
*** e0ne has joined #openstack-release18:59
nicolasbockIs that sufficient? Or do we also need to add the `release-notes-jobs-python3` template job?19:00
*** e0ne has quit IRC19:06
iurygregoryhberaud, hey molteniron is a bit of problems (we neve did release on ironic side,  it is just some tools 3rd party CI use to checkin/out baremetal resources for CI19:12
iurygregoryis there a way to "remove" from the publish job?19:12
hberaudiurygregory: these projects are published? Please, can you give me an example19:45
iurygregoryhberaud, https://opendev.org/openstack/releases/src/branch/master/deliverables/_independent/molteniron.yaml19:47
iurygregorymolteniron doesn't have any release19:47
iurygregoryalso by anychance do you have an idea about the need to test docs build with usedevelop=False? dtantsur raised two comments in the changes for ironic projects but zuul seems happy with the changes https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/769196/1/tox.ini https://review.opendev.org/c/openstack/sushy/+/769174/1/tox.ini19:49
hberaudnicolasbock: I see that you already use `publish-openstack-docs-pti` so I think you're potentially impacted by this bug, but I don't think you need to add this job template except if you want to release your release notes, but I didn't see lot of them in your repo19:51
nicolasbockThanks hberaud . So you think the current change is sufficient then?19:58
hberaudiurygregory: even if motleniron doesn't yet have been released it should be fixed, concerning `usedevelop` I think it can't hurt but I'm not an expert on this point19:58
nicolasbockAh just noticed that you left me a comment on the change :)19:59
hberaudnicolasbock: at first glance yes, but some clean up could be done19:59
hberaudyes :)19:59
hberaudnp19:59
nicolasbockI updated the change hberaud20:02
hberaudthanks20:04
*** sboyron has quit IRC20:35
*** dave-mccowan has quit IRC20:40
*** dave-mccowan has joined #openstack-release20:41
*** whoami-rajat__ has quit IRC21:01
*** e0ne has joined #openstack-release21:05
*** slaweq has quit IRC21:24
*** e0ne has quit IRC21:31
*** tkajinam has joined #openstack-release23:00

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