releng

#11326 F38 updates stuck in inconsistent state: "testing" but not in "updates-testing" repo
Closed: Fixed by decathorpe. Opened by decathorpe.

Closed: Fixed
Reopen Issue
  • Describe the issue

I have found four F38 updates that are stuck in an inconsistent state, which makes them show up as "testing->stable" or "testing" state in bodhi, but the builds themselves are available in neither the "updates-testing" nor the "fedora "repositories:

  • Lmod-8.7.19-1.fc38:

https://bodhi.fedoraproject.org/updates/FEDORA-2023-fa1d678565
https://koji.fedoraproject.org/koji/buildinfo?buildID=2122777

  • buildah-1.29.1-1.fc38:

https://bodhi.fedoraproject.org/updates/FEDORA-2023-3ee16689eb
https://koji.fedoraproject.org/koji/buildinfo?buildID=2153756

  • dotnet6.0-6.0.114-1.fc38:

https://bodhi.fedoraproject.org/updates/FEDORA-2023-5547e6c354
https://koji.fedoraproject.org/koji/buildinfo?buildID=2152981

  • dotnet7.0-7.0.103-1.fc38:

https://bodhi.fedoraproject.org/updates/FEDORA-2023-30c4106761
https://koji.fedoraproject.org/koji/buildinfo?buildID=2152340

The koji tags for these builds look wrong to me, and don't match the state that's displayed by bodhi (i.e. the "f38-updates-testing" tag is missing, but "f38-updates-testing-pending" is present).

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

Preferably before the end of the beta freeze, so they get some amount of testing. Right now the builds are in a void where they are not available from any repositories. (I'm not even sure if they would get pushed to "stable" state / the "fedora" repo correctly at the end of the beta freeze if they remain in this inconsistent state.)

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

Not sure. Depends on how broken the builds are and if they'd break the "f38-stable" compose after the beta freeze :)

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

Updates for a few packages are not available for testing and stuck in an inconsistent state (which might or might not be resolved when the beta freeze is lifted).

I was looking into similarities between the builds and bodhi updates. Take Lmod as an example. Update in bodhi failed gating 2 times and passed on the 3rd time but the test cases are still failing. But bodhi tagged the build into f38-updates-pending.

$ koji list-history --build=Lmod-8.7.19-1.fc38
Fri Jan 20 01:46:23 2023 Lmod-8.7.19-1.fc38 tagged into f38-updates-candidate by orion [still active]
Fri Jan 20 01:46:30 2023 Lmod-8.7.19-1.fc38 tagged into f38-signing-pending by bodhi
Fri Jan 20 06:10:32 2023 Lmod-8.7.19-1.fc38 untagged from f38-signing-pending by autopen
Fri Jan 20 06:10:32 2023 Lmod-8.7.19-1.fc38 tagged into f38-updates-testing-pending by autopen [still active]
Fri Feb 24 01:37:29 2023 Lmod-8.7.19-1.fc38 tagged into f38-updates-pending by bodhi [still active]

The same thing happened for all of them except for buildah.

Yes. As far as I can tell, the same thing happened to all of them:
The updates were in "testing" state while the beta freeze went into effect.

However, the "testing" state means something completely different before the updates-testing enablement (because before that happens, the "testing" state is just purgatory, while after the updates-testing enablement, builds in that state are actually pushed to the updates-testing repo).

But there is probably more to it, buildah was in testing before the freeze and dint move after the freeze. The dontnet6 update was in testing one day sooner than buildah and it got tagged by bodhi.
Edited by humaton

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

It appears that after the beta freeze was lifted, these updates were ejected from the "stable" compose because they are mis-tagged:

https://bodhi.fedoraproject.org/updates/FEDORA-2023-30c4106761#comment-2940908

Yep. I am just going to tag them into f38-updates-testing so they don't get ejected.

Looks like this worked as expected. All four affected updates are now in "stable". Thanks!

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

medium-gain medium-trouble ops

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.