Learn more about these different git repos.
Other Git URLs
As discussed in https://github.com/fedora-infra/bodhi/issues/4480 , Bodhi currently never marks Rawhide updates as critical path, because the 'branch' value for the "Fedora 37" release in Bodhi (which is currently Rawhide) is set to 'f37', and Bodhi queries PDC for critpath components using that name, but PDC expects to be queried with the name 'rawhide' for Rawhide.
@mattia says that the correct fix for this would be for the Bodhi release that is currently the same as Rawhide - so, right now, "Fedora 37" - to have "rawhide" set as its branch name, not "f37". He points out that the sample command in the SOP does say --branch rawhide.
--branch rawhide
So if I'm understanding things correctly, this is what should happen at branch points. A new Bodhi release should be created, called "Fedora NN", but with its branch name as "rawhide", not "fNN". The release which is being branched should have its branch name changed from "rawhide" to "fNN".
So for instance when Fedora 38 is branching, there should already be a "Fedora 38" release in Bodhi which has the branch name "rawhide". That release's branch name should be changed to "f38", and a new release called "Fedora 39" should be created, with the branch name "rawhide". Does that makes sense? If so, the SOP should be updated to explain this more clearly, it should be followed in future, and the existing "Fedora 37" release's branch name should be changed from "f37" to "rawhide" until Fedora 38 branches.
It can simply be fixed with bodhi-manage-releases edit --name F37 --branch rawhide
bodhi-manage-releases edit --name F37 --branch rawhide
About the switch to branched, this is covered in https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/bodhi/#_pre_beta_bodhi_config (which uses more or less the same command above)
Metadata Update from @zlopez: - Issue tagged with: low-gain, low-trouble, ops
The SOP you are linking is now one releng is using. Our SOP is here, but it has the wrong branch there so I am going to update it.
I am also not sure where is the executable mentioned there coming from we use $bodhi releases edit to make changes to existing releases.
$bodhi releases edit
The branch on the F37 release is now set to rawhide.
$ bodhi releases info F37 Release: Name: F37 Long Name: Fedora 37 Version: 37 Branch: rawhide ID Prefix: FEDORA Dist Tag: f37 Stable Tag: f37 Testing Tag: f37-updates-testing Candidate Tag: f37-updates-candidate Pending Signing Tag: f37-signing-pending Pending Testing Tag: f37-updates-testing-pending Pending Stable Tag: f37-updates-pending Override Tag: f37-override State: pending Email Template: fedora_errata_template Composed by Bodhi: True Create Automatic Updates: False Package Manager: unspecified Testing Repository: None End of Life: None
So, this has caused a nice mess. ;)
Bodhi is no longer tagging builds into f37-signing-pending... they just sit in f37-updates-candidate.
So, I think it's somewhere trying to use 'tagname-signing-pending' and if thats 'rawhide' it fails.
CC: @mattia in case he has ideas.
Ah, the problem was that when the branch was changed, the
Composed by Bodhi: True Create Automatic Updates: False
values were changed back to default. ;(
I switched them back and it's working now...
yeah, as discussed on IRC, I believe that's a Bodhi CLI bug. I'll try and do something about it this afternoon.
https://github.com/fedora-infra/bodhi/pull/4484 should fix the CLI bug, I reckon.
THe release was updated and the github PR merged. Closing.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.