#11675 No new Fedora Silverblue/Kinoite/Sericea build since 38.20230915.0 in Fedora 37 & 38
Closed: Fixed by siosm. Opened by siosm.

  • Describe the issue

No new builds of Fedora Silverblue/Kinoite/Sericea have been pushed since 38.20230915.0 in Fedora 37 & 38.

Also tracked in https://github.com/fedora-silverblue/issue-tracker/issues/492

My pipeline in https://gitlab.com/fedora/ostree/ci-test/-/pipelines appear to be working for those releases so I don't know where the issue is.

I used to look at https://pagure.io/releng/failed-composes/issues to find broken builds but I can't find any F38/F37 ones now.

  • When do you need this? (YYYY/MM/DD)

As soon as possible.

  • When is this no longer needed or useful? (YYYY/MM/DD)

N/A

  • If we cannot complete your request, what is the impact?

Users will not get updates for those variants.


I have a suspicion that it's due to a security update of python on bodhi-backend01. The service was still trying to use the older one that no longer existed.

I see in logs https://kojipkgs.fedoraproject.org/compose/updates/Fedora-38-updates-20230918.0/logs/global/pungi.global.log

"2023-09-18 00:15:41 [WARNING ] Failed to invoke notification script."

I've restarted it and am going to try a f38 push.

ok, it's still saying that, so that theory seems wrong.

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

Some questions... can you clarify what you mean by 'builds'? The ostree repo commits? Or the installer image builds?

This is affecting both stable updates and testing updates? or only one or the other?

And I assume 39/rawhide are fine?

I re-ran the playbook to make sure everything was set right and... now it might be working? But nothing should have changed, so I am pretty confused as to what caused it...

Some questions... can you clarify what you mean by 'builds'? The ostree repo commits? Or the installer image builds?

There were no new ostree commit in all F37/F38 refs. F39 & Rawhide were fine.

We now have new commits in F37 & F38 so looks like it's fixed. Thanks!

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

Metadata