#7836 mesa-18.2.0-2.fc29 disappeared from compose, might not be the only one
Closed: Fixed 5 years ago Opened 5 years ago by kparal.

mesa-18.2.0-2.fc29 has been tagged into f29 on Sep 20. But it's not available in any future compose, including today's 0925 one (it's not complete yet, but I checked the available logs). The only mesa present is the -1 one. Either I'm misunderstanding something or there's some bug in the compose process. I guess there might be multiple packages affected. The inconvenient thing is that we're trying to make sure the blocker fixes are present in F29 composes and we can't be sure now, unless we check everything manually.

Can somebody please have a look what went wrong, if it affects more packages, and what can we do to prevent it? Thanks.

Bodhi update:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-b94fe152c1

Koji tags:

$ koji list-tag-history --build mesa-18.2.0-2.fc29
Wed Sep 19 20:23:02 2018: mesa-18.2.0-2.fc29 tagged into f29-updates-candidate by adamwill
Wed Sep 19 20:26:33 2018: mesa-18.2.0-2.fc29 tagged into f29-signing-pending by bodhi
Wed Sep 19 20:28:47 2018: mesa-18.2.0-2.fc29 tagged into f29-updates-testing-pending by autopen
Wed Sep 19 20:28:47 2018: mesa-18.2.0-2.fc29 untagged from f29-signing-pending by autopen
Wed Sep 19 21:04:51 2018: mesa-18.2.0-2.fc29 tagged into f29-compose by mohanboddu [still active]
Thu Sep 20 14:11:58 2018: mesa-18.2.0-2.fc29 untagged from f29-updates-candidate by bodhi
Thu Sep 20 14:11:58 2018: mesa-18.2.0-2.fc29 tagged into f29-updates-testing by bodhi [still active]
Thu Sep 20 14:12:17 2018: mesa-18.2.0-2.fc29 untagged from f29-updates-testing-pending by bodhi
Thu Sep 20 21:32:27 2018: mesa-18.2.0-2.fc29 tagged into f29-updates-pending by bodhi
Thu Sep 20 22:34:57 2018: mesa-18.2.0-2.fc29 tagged into f29 by bodhi [still active]
Thu Sep 20 22:35:10 2018: mesa-18.2.0-2.fc29 untagged from f29-updates-pending by bodhi
Thu Sep 20 22:51:55 2018: mesa-18.2.0-2.fc29 tagged into f29-Beta by mohanboddu [still active]

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

5 years ago

This is a bug with bodhi, esp after freeze. Bodhi doesn't know about how to tag the builds and if there are multiple builds of same package, it might tag them randomly and highest nvr might tagged first and then the lower nvr which becomes the latest tagged and pungi will pick the latest tagged builds and by which it will pick the older nvr build.

I fixed this and I will check if there are anymore issues like this.

Thanks for reporting.

Login to comment on this ticket.

Metadata