Describe what you need us to do: Yesterday and today I observed two instances where newrepo did not automatically run on f29-infra and f29-infra-stg repos. Yesterday I built https://koji.fedoraproject.org/koji/buildinfo?buildID=1174013 and eventually had to ask @kevin to run newrepo for me manually. Today I tagged that same build to stable, but it didn't appear in the stable repo and I don't see any newrepo tasks. I reported https://pagure.io/releng/issue/8006 to ask releng to run it for me.
When do you need this? (YYYY/MM/DD) When there's time.
When is this no longer needed or useful? (YYYY/MM/DD) N/A
If we cannot complete your request, what is the impact? People will have to manually request newrepo jobs to be run when tagging things into the infra repos.
I believe the same underlying issue is preventing me from pushing a beta of pagure 5.2 to stg (ie: epel7-infra-stg is also impacted)
This seems to have been caused by some NFS outage/hang on bodhi-backend02 (where tag2repo runs).
I rebooted bodhi-backend02 and manually generated epel7-infra-stg and f29-infra-stg. It should now work again moving forward.
:sunflower:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.