Push fails for update that reached testing when release did not have updates-testing but is submitted stable when it does

[AdamWill]

https://bodhi.fedoraproject.org/updates/FEDORA-2024-4e960d96d5 is the case here. It looks like when that update was created and subsequently reached "testing" status in Bodhi, F40 (the release it's for) was Rawhide. That means it was using the different workflow for Rawhide releases. But the update failed gating for a long time. When it finally passed gating, it was submitted for stable - but by then, F40 was no longer Rawhide. So now F40 is on the workflow for branched releases (well, releases after u-t activation, technically, I guess).

It looks like this results in the stable push failing because the package does not have the tags Bodhi is expecting for an update going from 'testing' to 'stable' for a branched release.

Maybe Bodhi can recognize this case and send the update through the branched release tag workflow from the start, or something? Not sure. But it seemed worth reporting.

[AdamWill]

alternatively, at u-t activation time, we could look for updates in this state (stuck in 'testing' due to gating failure) and do...something...to "convert" them to the expected state post u-t activation, so they have the correct tags and go into the new u-t repo? @nirik