#9169 Bodhi update not pushed to stable after "Auto-request stable based on time?"
Opened 10 days ago by churchyard. Modified 7 days ago

Describe what you would like us to do:

https://bodhi.fedoraproject.org/updates/FEDORA-2020-56e5d11739

This update was not pushed to stable automatically after time. It is in testing for 3 weeks now, but the auto push is set for 14 days.

Is something broken? I can certainly push the update manually, but I thought you should know.

When do you need this to be done by? no date


Metadata Update from @mobrien:
- Issue tagged with: medium-gain, medium-trouble

9 days ago

@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

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

9 days ago

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.

Login to comment on this ticket.

Metadata