@pingou @cverna do you know what is used to trigger these automatic pushes?

@pingou @cverna do you know what is used to trigger these automatic pushes?

I think it's a celery beat

Can I push the update manually or would that interfere with debugging this issue?

I'Ve pushed the update because I need to make a new one and this would have been obsoleted anyway.

This looks like https://github.com/fedora-infra/bodhi/issues/4042 ? That 'This update can be pushed to stable now if the maintainer wishes' message was posted after 2 karma even though that's not the limit, and it was certainly not 14 days since it was pushed to testing.

2 karma is the required limit for a critpath upgrade thou.

Maybe related? The settings on your update are +5 though.

Yes but the comment 'This update can be pushed to stable now if the maintainer wishes' shows up after the required limit is met, not the set one.

Should we perhaps move this one upstream? Or close and see if it happens again? (Do we see any more cases of it?)

Whatever you deem appropriate. This is the only case I've seen but @qulogic seems to be hit be this too.

I rarely get +2 karma, so I have no other cases, except the one I posted in the bodhi issue, and the original reporter's.

I believe there has been a new bodhi release pushed recently. Could you see if that makes a difference for you?

Has this hit you all since the bodhi update?

No. Will reopen if it ever does. Thanks.

Another one; https://bodhi.fedoraproject.org/updates/FEDORA-2021-0691392fdd +2 karma only, says it can be pushed, but hasn't after 3 days.

Bodhi logs say:

[2021-04-02 00:58:35,677: INFO/ForkPoolWorker-15] FEDORA-2021-0691392fdd has already the comment that it can be pushed to stable - bailing