It appears that some packages don't get blocked in koji when a retirement commit gets pushed to dist-git.
I've seen this happen multiple times in the past few months, and the only thing I see that those packages have in common is that they were also created in the last ~3 months - is some component that processes retirements not getting an updated list of "valid package names" or something?
In the current case, the retirements that weren't processed correctly are:
rust-rstest0.23: retired in epel9 branch but not blocked in epel9 tag in koji
When do you need this? (YYYY/MM/DD)
Not urgent. But would be great to find out what's going wrong in the retirement processing that causes some packages to zombify.
N/A
zombified packages hanging around.
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
Thank you for opening request - I have manually blocked them for now, and will look into why they weren't blocked automatically in koji.
koji list-pkgs --show-blocked --package rust-rstest_macros0.23 Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- rust-rstest_macros0.23 epel9 decathorpe rust-rstest_macros0.23 f41 decathorpe rust-rstest_macros0.23 f42 decathorpe rust-rstest_macros0.23 f43 decathorpe rust-rstest_macros0.23 epel10.1 decathorpe rust-rstest_macros0.23 f44 decathorpe [BLOCKED] rust-rstest_macros0.23 epel10.2 decathorpe rust-rstest_macros0.23 f43-Beta decathorpe ➜ ~ koji list-pkgs --show-blocked --package rust-rstest0.23 Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- rust-rstest0.23 epel9 decathorpe [BLOCKED] rust-rstest0.23 f41 decathorpe rust-rstest0.23 f42 decathorpe rust-rstest0.23 f43 decathorpe [BLOCKED] rust-rstest0.23 epel10.1 decathorpe rust-rstest0.23 f44 decathorpe [BLOCKED] rust-rstest0.23 epel10.2 decathorpe rust-rstest0.23 f43-Beta decathorpe
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Found and reported another case of the same general problem: https://pagure.io/releng/issue/13037
Log in to comment on this ticket.