It looks like the-new-hotness hasn't filed new "new version is available!" bugs (or updated existing bugs) since ~June 16. release-monitoring.org seems to find new releases just fine, but no bugs are getting updated and / or filed on bugzilla.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, high-gain
Metadata Update from @zlopez: - Issue untagged with: Needs investigation - Issue assigned to zlopez - Issue tagged with: low-trouble
There is an expired bugzilla certificate. I will regenerate it.
This is now fixed on production. I couldn't regenerate it on staging as I wasn't able to login to bugzilla.stage.redhat.com with the credentials in ansible-private.
I'm closing this as on staging it's not an issue for now.
Metadata Update from @zlopez: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
I suspect there's no way to have it file / update the bugs for the releases it missed during this time?
No, it already dropped all the messages because of the bugzilla error :/
Log in to comment on this ticket.