#9224 f33-signing-pending packages stuck as nonsigned
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by mtasaka.

It seems that after branches packages built for f33 are stuck on f33-signing-pending but not signed or moved to f33 buildroot.

https://koji.fedoraproject.org/koji/builds?order=-completion_time&tagID=18678&inherited=0&latest=1

Currently (as of 2020/08/12 21:54 JST) 50 packages are left on f33-signing-pending. Except for calibre, signiing is not executed for 16 hours.

Would you investigate the status for f33 signing?


This is actually expected. Until we have a f33 branched compose, we 'freeze' the f33 builds to make it easier to do that.

See: https://fedoraproject.org/wiki/Changes/Freeze_after_branching_until_compose_is_ready

Hopefully we will get one soon/today and unblock things.

Sorry for the trouble.

Metadata Update from @kevin:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

3 years ago

I wonder if, at this stage, automatic-updates shouldn't be disabled for F33...
Users cannot create new updates until a Release is marked composed_by_bodhi, but with create_automatic_updates set to ON every build on F33 will create a new Update that will stay stuck in pending till the activation point. So the 'freeze' is not really cold.

no. We want it the way it is.

Everything will stay in pending until we get a compose. :)

If we need something to get a compose, we can manually sign it and bodhi will move it in place for the compose.

Once we have a compose, we enable autosign for f33, automatic updates will flow.

Does that make sense?

Metadata Update from @kevin:
- Issue status updated to: Open (was: Closed)

3 years ago

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Sure, I was just surprised today to see that high number of pending updates. There's a 'Frozen' state in Bodhi that should display a descriptive message to users, but I've never seen in action and I'm not sure if it implies anything else.

Also, in the past I'm pretty sure that updates in 'pending' status were not set as 'obsoleted' when a newer build was pushed. I'll check that, but consider we could have some leftovers in pending when the freeze is over.

Log in to comment on this ticket.

Metadata