| gouthamr | i've a list here: https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L52 ; yaml formatted it in the hope that there was an API we could script against.. | 00:00 |
|---|---|---|
| gouthamr | there're about ~270 repositories which need some more sifting that aren't in this list.. not all of these are on PyPi.. | 00:04 |
| gouthamr | i've added those to the etherpad as well... will attempt to find their state | 00:05 |
| opendevreview | Merged openstack/openstack-manuals master: Retire Solum: remove doc ref https://review.opendev.org/c/openstack/openstack-manuals/+/919227 | 06:12 |
| opendevreview | Merged openstack/openstack-manuals master: Retire Senlin: remove doc ref https://review.opendev.org/c/openstack/openstack-manuals/+/919356 | 06:57 |
| opendevreview | Merged openstack/openstack-manuals master: Retire Murano: remove doc ref https://review.opendev.org/c/openstack/openstack-manuals/+/919372 | 07:06 |
| opendevreview | Merged openstack/openstack-manuals master: Retire Sahara: remove doc ref https://review.opendev.org/c/openstack/openstack-manuals/+/919392 | 07:06 |
| opendevreview | Merged openstack/openstack-manuals master: Retire ec2-api: remove doc ref https://review.opendev.org/c/openstack/openstack-manuals/+/919395 | 07:06 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Make the project removal from infra as step#6 https://review.opendev.org/c/openstack/project-team-guide/+/919976 | 17:28 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Make the project removal from infra as step#6 https://review.opendev.org/c/openstack/project-team-guide/+/919976 | 17:28 |
| gmann | noonedeadpunk: ^^. I am going to start the ref cleanup | 17:29 |
| fungi | revisiting the mistral situation, didn't we "yank" year-based releases for other projects from pypi so that those would stop showing as the highest version numbers? | 17:30 |
| gmann | noonedeadpunk: for openstack-ansible, did you already proposed the fixes ? if not then I can do. | 17:33 |
| fungi | gmann: i think jrosser_ already did yesterday | 17:34 |
| gmann | fungi: ohk, thanks | 17:34 |
| gmann | will check for other projects | 17:34 |
| jrosser_ | then other projects got retired also and my patch failed | 17:34 |
| jrosser_ | so takes forever to get it merged | 17:35 |
| gmann | JayF: link please | 17:35 |
| gmann | jrosser_: ^^ | 17:35 |
| gmann | JayF: please ignore this ping | 17:35 |
| gmann | jrosser_: there are total 5 projects are being retired together those were inactive since last cycle and leaderless in this cycle too | 17:35 |
| jrosser_ | gmann: https://review.opendev.org/c/openstack/openstack-ansible/+/919902 | 17:37 |
| gmann | jrosser_: thanks. as you have removed all of those retired one, it seems jobs are running now https://zuul.openstack.org/status | 17:39 |
| jrosser_ | fungi: what was interesting was when we got a subsequent failure due to Sahara, we did not see the same “CI bypass” trouble as I did initially yesterday | 17:39 |
| fungi | jrosser_: was it on a change that was modifying the project's zuul configuration? | 17:40 |
| fungi | if so, that does get validated and must actually result in sensible configuration | 17:40 |
| jrosser_ | right yes I saw a proper error on the patch that initially just removed murano | 17:41 |
| fungi | it's just when zuul has been asked to run with nonsensical configuration (because something has changed outside its control) that you end up with the incomplete jobs not being run | 17:41 |
| fungi | like i mentioned on the ml, it might be possible to add something like a tenant-wide option to keep jobs with nonsensical configuration in the pipeline instead as empty jobs that instantly fail, that's just not the current behavior under those conditions | 17:42 |
| jrosser_ | I guess I came close to disaster yesterday with merging lots of unchecked/gated patches | 17:43 |
| jrosser_ | and the same situation still exists on our stable branches until I merge / backport that removal patch I think | 17:44 |
| fungi | well, the sort of "disaster" that most other open source projects call a thursday ;) | 17:44 |
| fungi | but yes, definitely not up to our promised quality standard | 17:44 |
| gmann | I think this seems bug to me. it should fail is job are not running which are expected to be run | 17:45 |
| fungi | yeah, i can bring it up in the zuul matrix channel and see if there are any suggestions | 17:45 |
| gmann | if not then zuul should ignore the required-proejcts non existing project and try to run the job | 17:45 |
| gmann | thanks | 17:46 |
| fungi | revisiting the year-based version yanking from pypi, we did a bunch in the first half of 2019, for example https://lists.openstack.org/pipermail/openstack-discuss/2019-March/004224.html | 18:16 |
| fungi | noonedeadpunk: do you think that ^ is something the mistral maintainers would like done too? | 18:22 |
| fungi | then https://pypi.org/project/mistral/ wouldn't look like its last release was 9 years ago | 18:24 |
| opendevreview | Merged openstack/governance master: Neutron: Retire networking-ovn https://review.opendev.org/c/openstack/governance/+/919700 | 19:43 |
| opendevreview | Ghanshyam proposed openstack/governance master: Clarify the project retirement vs project's repository retirement https://review.opendev.org/c/openstack/governance/+/919984 | 19:48 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Make the project removal from infra as step#6 https://review.opendev.org/c/openstack/project-team-guide/+/919976 | 19:50 |
| gmann | tc-memebrs: gouthamr: clarifying the house rule for retirement of project vs repo of existing project https://review.opendev.org/c/openstack/governance/+/919984 | 19:51 |
| gouthamr | ack ty gmann | 19:51 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!