| frickler | release-team: so the failures I mentioned yesterday seems to have been due to acl issues when pushing .gitreview updates for retired repos, like e.g. https://paste.opendev.org/show/bcIOAuVaapda9ELEuFJj/ | 06:28 |
|---|---|---|
| frickler | likely we should have eoled those instead like we did for the similar puppet repos, maybe we can still do this now? | 06:29 |
| frickler | also not clear to me what cleanup action might be needed now | 06:30 |
| ralonsoh | frickler, hi, do you know where is the best place to open a bug for an external library? | 06:33 |
| ralonsoh | twine is breaking a CI job | 06:34 |
| ralonsoh | e.g.: https://04824dc10f811bf71cc7-f60cbd2bdbb8b5648c0b0982a5f4272f.ssl.cf1.rackcdn.com/939769/3/check/test-release-openstack/cd3a31f/job-output.txt | 06:34 |
| ralonsoh | last release was 2 days ago: https://pypi.org/project/twine/#history | 06:34 |
| ralonsoh | https://zuul.opendev.org/t/openstack/builds?job_name=test-release-openstack&skip=0 | 06:34 |
| frickler | ralonsoh: well in this case it would be https://github.com/pypa/twine/issues , but I'm not sure whether it isn't actually our jobs or our packaging that might need adapting. we could also consider pinning the twine version as temporary workaround | 06:39 |
| ralonsoh | frickler, yes, this is what I'm going to propose right now | 06:40 |
| ralonsoh | and also opening a bug for the library | 06:40 |
| ralonsoh | https://github.com/pypa/twine/issues/1218 | 06:48 |
| frickler | hmm, it seems weird that we still run that job on focal with py3.8, while the pkgs require py >= 3.9, I guess we should bump that job to noble, too? | 09:17 |
| elodilles | frickler: about the ACL issue: we should probably EOL that project instead :/ though there is a side case: if a project is retired, but still has stable branches then it cannot push patches on stable branch (and we cannot release it i guess). so it's interesting whether we should think about the ACL settings... :S | 10:24 |
| frickler | elodilles: right, I was using the wrong term, governance calls the state where only master is emptied "deprecated". maybe the ACL was changed prematurely? sadly I don't have the time to dig deeper currently, I was secretly hoping noonedeadpunk would take a look ;) | 10:34 |
| elodilles | about twine: to me that looks like we need a cap (?) for twine as that is - as far as i understand - a bug, not a feature :) | 10:34 |
| frickler | elodilles: ralonsoh already proposed https://review.opendev.org/c/zuul/zuul-jobs/+/939936 , from the discussion in the issue I understand they will fix the description parsing problem | 10:35 |
| elodilles | cool, thanks frickler and ralonsoh o/ | 10:37 |
| noonedeadpunk | what project are you discussing? | 10:38 |
| noonedeadpunk | what to look for ?:D | 10:38 |
| elodilles | noonedeadpunk: openstack-ansible-os_murano | 10:38 |
| elodilles | frickler linked this snippet: https://paste.opendev.org/show/bcIOAuVaapda9ELEuFJj/ | 10:39 |
| noonedeadpunk | So IF I understand retirement correctly - nobody should push anything to stable branches | 10:39 |
| noonedeadpunk | as then it's not retired, but deprecated | 10:39 |
| noonedeadpunk | about ACLs - that's interesting point | 10:39 |
| elodilles | i had the understanding that a retired projects master branch is cleaned completely, thus that cannot be used, but usually other branches are not deleted/EOLd | 10:40 |
| noonedeadpunk | but I see 2023.1-eom being done there yesterday, so I guess ACL is not an issue? | 10:40 |
| noonedeadpunk | I think that's were destinction between retirement and deprecation is | 10:41 |
| noonedeadpunk | if you can have stable branches | 10:41 |
| noonedeadpunk | "If you need to retire a project and no longer accept patches - for both master and stable branches -, it is important to communicate that to both users and contributors. " | 10:41 |
| noonedeadpunk | https://docs.openstack.org/project-team-guide/repository.html#retiring-a-repository | 10:41 |
| noonedeadpunk | so effectively - it's EOLed | 10:41 |
| noonedeadpunk | to be frank - sanity-wise, I see how things are mis-aligned and confusing | 10:42 |
| noonedeadpunk | but I somehow never tried to challanged that part as it _always_ was like that | 10:43 |
| noonedeadpunk | I am even not sure if retirement is a good thing overall. As removing project from zuul config results in errors on all branches | 10:44 |
| noonedeadpunk | SO maybe indeed a question should be raised if our retirement process is adequate overall | 10:44 |
| noonedeadpunk | fwiw, about 2023.1 osa EOM - waiting for this patch: https://review.opendev.org/c/openstack/openstack-ansible/+/939944 | 10:47 |
| noonedeadpunk | it's sha is gonna be used for 2023.1-eom | 10:47 |
| frickler | looks like that is failing https://zuul.opendev.org/t/openstack/status?change=939944 | 10:49 |
| noonedeadpunk | ah, zun_kuryr doesn't have EOM... | 10:49 |
| noonedeadpunk | I assume they were retired and went right to eol | 10:49 |
| noonedeadpunk | thanks for pointing as I frankly didn't check zuul | 10:50 |
| noonedeadpunk | oh, well | 10:50 |
| noonedeadpunk | kuryr-libnetwork still has stable/2023.1 | 10:51 |
| noonedeadpunk | same for kuryr itself | 10:52 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: [kuryr] Transition 2023.1 Antelope to Unmaintained https://review.opendev.org/c/openstack/releases/+/939950 | 10:59 |
| frickler | ah, right, that's likely because those repos were transitioned to zun governance, but only after https://review.opendev.org/c/openstack/releases/+/934467 was merged | 11:00 |
| noonedeadpunk | I assume that'd require zun approval then. Also - not sure, there were 2 commits with gitreview and tox edit, but I thought that tagging them is a bit useless | 11:21 |
| frickler | release-team: ^^ that's another interesting question, IMO governance changes should affect all stable branches. deliverables/dalmatian/kuryr.yaml has "team: zun" while older branches still say "team: kuryr"? | 11:35 |
| frickler | noonedeadpunk: also regarding the hashes, deleting the stable/2023.1 branch won't work if 2023.1-eom doesn't point to its HEAD | 11:36 |
| noonedeadpunk | doh | 11:39 |
| noonedeadpunk | so then we'd need to create new bugfix releases which would include .gitreview only to replace it with unmaintained one... | 11:40 |
| ttx | frickler: agree governance changes should affect all stable branches | 12:33 |
| opendevreview | Merged openstack/releases master: Create final stable/2023.1 release of puppet-keystone https://review.opendev.org/c/openstack/releases/+/939805 | 14:22 |
| frickler | humm, elod was once again faster than me with triggering the recheck ;) | 14:38 |
| frickler | also the 2023.1-last patches don't gate in our current fixup state :( | 14:39 |
| Clark[m] | frickler: elodilles: while the twine issue is being treated as a bug it seems to at least partially originate in the use of old setuptools on old python. Updating where the job runs may help mitigate | 14:40 |
| frickler | Clark[m]: yes, that was just done with https://review.opendev.org/c/openstack/project-config/+/939947 , though I expect the job will need some more fixes | 14:41 |
| frickler | yup, as expected, ensure-twine needs to switch to using a venv I'd assume https://zuul.opendev.org/t/openstack/build/c92944a4a28345c6b38fcfb285e250ef | 15:06 |
| elodilles | release-team: about the 2023.1-last patches failures: we should recheck them after we set back 2023.1 antelope as unmaintained o:) (the error is: "deliverables/antelope/zun-tempest-plugin.yaml: validate_version_numbers: LAST tag 2023.1-last aren't allowed on a series (antelope) that are not EM or Unmaintained") | 15:16 |
| elodilles | i've +2+W'd the puppet 2023.1-eom patch | 15:23 |
| frickler | elodilles: thx. do you also have some idea how to best proceed with the kuryr eom stuff? iiuc this is blocking noonedeadpunk from finishing the final osa 2023.1 things | 15:31 |
| opendevreview | Merged openstack/releases master: [Puppet OpenStack] Transition 2023.1 Antelope to Unmaintained https://review.opendev.org/c/openstack/releases/+/934488 | 15:44 |
| opendevreview | Elod Illes proposed openstack/releases master: [zun] Transition missed deliverables https://review.opendev.org/c/openstack/releases/+/939980 | 15:54 |
| elodilles | frickler: ^^^ | 15:54 |
| opendevreview | Elod Illes proposed openstack/releases master: [zun] Transition missed deliverables https://review.opendev.org/c/openstack/releases/+/939980 | 15:56 |
| opendevreview | Michal Nasiadka proposed openstack/releases master: pycadf: Release 4.0.1 https://review.opendev.org/c/openstack/releases/+/939548 | 17:11 |
| mnasiadka | Hello release team - any chance in getting pycadf 4.0.1 released? https://review.opendev.org/c/openstack/releases/+/939548 | 17:11 |
| ttx | looking | 17:48 |
| ttx | mnasiadka: we seem to be missing the PTL+1 checkmark on this one | 17:49 |
| *** tosky_ is now known as tosky | 21:41 | |
| -opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline momentarily while we reboot for a patch version upgrade of the software, but should return again within a few minutes | 22:46 | |
| *** promethe- is now known as prometheanfire | 23:25 | |
| opendevreview | Ian Y. Choi proposed openstack/releases master: Add dates for 2025.2/"F" elections https://review.opendev.org/c/openstack/releases/+/939927 | 23:52 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!