#8789 Errant Modules That Need To Be Retired
Closed: Fixed by mprahl. Opened by mprahl.

Due to a bug in MBS [1], the following modules were built and reused components from modules built against the wrong platform
6398 (perl:5.28:3020190912134325:eb1b2d95)
6397 (perl:5.28:2920190912134325:c8f01160)
6396 (perl:5.28:3120190912134325:a5d38390)
6390 (sway:rolling:3020190912072731:a5b0195c)
6389 (sway:rolling:3220190912072731:43bbeeef)
6388 (sway:rolling:3120190912072731:f636be4b)
6387 (sway:rolling:2920190912072731:6c81f848)
6386 (silver:rolling:2920190912064049:c5ebb199)
6385 (silver:rolling:3020190912064049:a23e773d)
6383 (silver:rolling:3120190912064049:22d7e2a5)

Could I have approval from releng to retire these module builds using mbs-manager retire <nsvc> on the MBS backend?

The following users are affected by this: @ignatenkobrain, @thofmann, and @ppisar.

1 - https://pagure.io/fm-orchestrator/issue/1409


What does it mean "retire these modules"? I guess you mean retire the builds. If that's so, please do that.

What will happen with the builds that were already shipped to mirrors? What's the remedy? A rebuild with only-changed strategy? Or do I have to use rebuild-all strategy to prevent from reusing the affected artifacts?

@ppisar yes, I meant retire those builds. Once the affected builds are retired, you can rebuild your module like normal and the components should be reused from the correct module. The retired build will be ignored during checks for component reuse.

Done.

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

Metadata Update from @mprahl:
- Issue status updated to: Open (was: Closed)

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

That's great. I only have a more work for you. I've just finished building perl:5.28:xx 20190912134325 that seems also affected:

https://mbs.fedoraproject.org/module-build-service/2/module-builds/6396
https://mbs.fedoraproject.org/module-build-service/2/module-builds/6397
https://mbs.fedoraproject.org/module-build-service/2/module-builds/6398

Please retire them too.

Please notify me when MBS is fixed. A post here is enough.

@ppisar MBS is hotfixed in production. Please let me know if you experience any more issues.

That's great. I only have a more work for you. I've just finished building perl:5.28:xx 20190912134325 that seems also affected:
https://mbs.fedoraproject.org/module-build-service/2/module-builds/6396
https://mbs.fedoraproject.org/module-build-service/2/module-builds/6397
https://mbs.fedoraproject.org/module-build-service/2/module-builds/6398
Please retire them too.

These are included in the initial ticket description and are retired as well.

@mprahl , please rebuild those modules and edit bodhi updates.

@ignatenkobrain I'm sorry, but I don't have permission to that repo or Bodhi update. If for some reason you can't do it yourself, maybe @mohanboddu could help out.

You need to do the following:

fedpkg clone modules/silver
cd silver
git commit -m "Bump" --allow-empty
fedpkg push
fedpkg module-build -w

Then you need to edit the Bodhi update(s).

Let me know if I need to build them.

Metadata