#8813 buildroot confusion with hwloc and openmpi
Closed: Fixed 2 years ago by mohanboddu. Opened 2 years ago by zbyszek.

I built hwloc on 2019-08-28 [1] and submitted a buildroot override [2] for the maximum duration, until 2019-09-28. A bunch of packages was built against the new hwloc [3].
openmpi-4.0.2-0.4.rc2.fc31 [4] was built on 2019-09-15 and got the old version of hwloc in the buildroot. bodhi says the override expired today "7 h ago".

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1366144
[2] https://bodhi.fedoraproject.org/overrides/hwloc-2.0.4-1.fc31
[3] https://bodhi.fedoraproject.org/updates/FEDORA-2019-af50f19b83
[4] https://koji.fedoraproject.org/koji/buildinfo?buildID=1377543

It seems like koji is pulling some random packages into the buildroot.

Also, various buildroot overrides that I made are shown as expired, without any justification. They didn't reach their time limit yet, eg. [2, 5].

[5] https://bodhi.fedoraproject.org/overrides/mpich-3.3.1-1.fc31

edit:
There are two issues:
1. overrides are expired early for some unknown reason
2. overrides seem to be ignored, even before the early expiration


  1. overrides are expired early for some unknown reason

@bowlofeggs Does the override gets untagged when the update associated with that build get changed?

The update associated to hwloc-2.0.4-1.fc31 was first updated (changed a build in that update, but its not the hwloc package build) on Sept 5th 2019, on that day itself the override is also expired, same with mpich-3.3.1-1.fc31 override as well.

Thu Sep  5 14:00:34 2019 hwloc-2.0.4-1.fc31 untagged from f31-updates-testing by bodhi
Thu Sep  5 14:00:35 2019 hwloc-2.0.4-1.fc31 untagged from f31-override by bodhi
  1. overrides seem to be ignored, even before the early expiration

@zbyszek I guess the problem here is wrong info being display, the override hasn't expired 7/8 hours ago, instead they were expired (untagged from overrides tag) on Sept 5th 2019.
@bowlofeggs So, those updates got pushed to stable 7/8 hours ago which is when I think bodhi sees them as expired. Probably another bug to fix, please let me know if my debugging is right and I will create a bodhi ticket for you.

On Wed, 2019-09-18 at 13:57 +0000, Mohan Boddu wrote:

@bowlofeggs So, those updates got pushed to stable 7/8 hours ago
which is when I think bodhi sees them as expired. Probably another
bug to fix, please let me know if my debugging is right and I will
create a bodhi ticket for you.

I don't work on Bodhi anymore, so you may want to file a bug against
the Bodhi issue tracker.

Closing this as its fixed upstream and deployed.

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

2 years ago

Login to comment on this ticket.

Metadata