#6411 qtpass: request for stable open for 13 days
Closed: Fixed None Opened 7 years ago by daveo.

I made a new package [https://apps.fedoraproject.org/packages/qtpass/overview/ qtpass] which seems to be having some problems.

The stable request in bodhi has been open for 13 days for both [https://bodhi.fedoraproject.org/updates/FEDORA-2016-52d9d7d25f f22] and [https://bodhi.fedoraproject.org/updates/FEDORA-2016-52d9d7d25f f23]. And according to the [https://apps.fedoraproject.org/packages/qtpass/overview/ overview] the package seems to be in both the testing and stable repositories for f24.


The issue is much more severe than this one package. All push requests submitted (except for F24 packages) between approximately 2016-05-02 14:30 UTC and 2016-05-03 09:00 UTC have ended up in this state where the updates were locked in preparation for a push, but the push never happened. And since the push attempt never failed they are not picked up for retry on the next push. These update requests are in a state that is impossible for the requesters to manipulate and bodhi sees them to be in a state it does not expect to find any update requests in and refuses to do anything with them. Intervention from an administrator is urgently needed.

This issue was reported for the requests for pushes to the testing repositories in the bodhi ticket https://github.com/fedora-infra/bodhi/issues/838 five days ago, but not much happened since except that there was a request for a link to a sample update suffering from the problem. Such a link was provided.

As indicated in this ticket, also push requests to stable are suffering from this issue, not just the requests to testing as reported in the bodhi ticket. In the bodhi web interface updates are sorted according to the their creation time, i.e. the time for the request to push to testing, so it is easy to find all the affected requests for pushes to testing since they are listed together. The affected pushes to stable are scattered in the lists so not so easy to see, but they are there too.

This was fixed a while back. Sorry for not closing it.

Metadata Update from @daveo:
- Issue set to the milestone: Fedora 24 Alpha

7 years ago

Login to comment on this ticket.

Metadata