Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Running crb enable fails with 'subscription-manager: error: no such option' Version-Release number of selected component (if applicable): epel-release-9-7.el9.noarch How reproducible: Always Steps to Reproduce: 1. Use a subscription where codeready-builder-for-rhel-9-x86_64-rhui-rpms is available 2. run 'crb enable' Actual results: crb enable fails with: Enabling CRB repo subscription-manager: error: no such option: codeready-builder-for-rhel-9-x86_64-rpms CRB repo is enabled and named: codeready-builder-for-rhel-9-x86_64-rpms Expected results: CRB repository is enabled Additional info: It looks like 'crb' fails as it does not filter 'codeready-builder-for-rhel-9-x86_64-rhui-rpms' repo correctly
You are correct, but I have no rhui machines to test on. What do you get when you do dnf repolist --all | grep -i -e crb -e powertools -e codeready
codeready-builder-for-rhel-9-x86_64-debug-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-eus-debug-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-eus-rhui-debug-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-eus-rhui-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-eus-rhui-source-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-eus-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-eus-source-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-rhui-debug-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-rhui-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-rhui-source-rpms Red Hat C disabled codeready-builder-for-rhel-9-x86_64-rpms Red Hat C enabled codeready-builder-for-rhel-9-x86_64-source-rpms Red Hat C disabled
I think you just need to add -e rhui to all the ocurrences of 'grep -v -i -e debug -e source -e eus -e virt'
(In reply to Miguel Martin from comment #3) > I think you just need to add -e rhui to all the ocurrences of 'grep -v -i -e > debug -e source -e eus -e virt' Yep Simple enough fix.
I'm not sure why this wasn't automatically updated, but here are the builds. epel9: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-5e6d90ccde epel8: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-6e5a4ffb91
On a RHUI connected system, shouldn't the preference be for codeready-builder-for-rhel-9-x86_64-rhui-rpms, not codeready-builder-for-rhel-9-x86_64-rpms? I think you would only have the later on a RHUI system if there was a regular subscription on that system as well, which seems like a mistake. The script is going to need a bit better logic than just always excluding repos with "rhui" in the repo ID.
You have a good point. Although excluding rhui still get's you crb enabled, it doesn't give you an efficient repo (one that is close to you.) The error was happening because we have more than one item coming from our logic. What if we fix that, and make it so the rhui line would be the prefered line. We currently have crb_repo=$(dnf repolist | grep -i -e crb -e powertools -e codeready | grep -v -i -e debug -e source -e eus -e virt -e rhui | awk '{print $1}') But if we switch it to this, it should give us what we want. crb_repo=$(dnf repolist | grep -i -e crb -e powertools -e codeready | grep -v -i -e debug -e source -e eus -e virt | awk '{print $1}' | head -n1) "dnf repolist" gives the repo's sorted in an alphabetical order. Thus 'codeready-builder-for-rhel-9-x86_64-rhui-rpms' will always be before 'codeready-builder-for-rhel-9-x86_64-rpms' and "head -n1" will give us the repo that we want. If that sounds good, I'll get a pull request written up.
I am slightly worried long term about relying on an alphabetical sort because that seems fragile (for instance, if the id of the RHUI repos changes), but it would work for now until we get around to implementing more advanced logic. Let's do it. Drop a link to the PR here once you have it worked up and I'll try to review.
Not sure where the output of comment #2 comes from, but on AWS it simply looks like this: $ dnf repolist --all | grep -i -e crb -e powertools -e codeready codeready-builder-for-rhel-9-rhui-debug-rpms Red Hat CodeReady Linux B disabled codeready-builder-for-rhel-9-rhui-rpms Red Hat CodeReady Linux B disabled codeready-builder-for-rhel-9-rhui-source-rpms Red Hat CodeReady Linux B disabled $ That's why I am now proposing this merge request: https://src.fedoraproject.org/rpms/epel-release/pull-request/39
Could you please review https://src.fedoraproject.org/rpms/epel-release/pull-request/39? Thank you.
The pull request is basically just taking the "-e rhui" out of the "grep -v" If what you show above, is what is happening, then yes, we need to do that. Even if someone has the output in the earlier comment, they will still get the rhui repo, or at worst, the non-rhui repo. Even the non-rhui repo is better than no repo.
I have merged the merge requests. I will check to see if there are any more expected changes to epel-release. If there are expected changes, I'll wait until they come to get this built. If there aren't any, I'm bump the release and build these.
FEDORA-EPEL-2026-8f402ccbf4 (epel-release-10-8.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-8f402ccbf4
FEDORA-EPEL-2026-007628f1c3 (epel-release-10-8.el10_3) has been submitted as an update to Fedora EPEL 10.3. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-007628f1c3
FEDORA-EPEL-2026-6247e08a96 (epel-release-9-11.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-6247e08a96
FEDORA-EPEL-2026-8f402ccbf4 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-8f402ccbf4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-007628f1c3 has been pushed to the Fedora EPEL 10.3 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-007628f1c3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-6247e08a96 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-6247e08a96 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-007628f1c3 (epel-release-10-8.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-8f402ccbf4 (epel-release-10-8.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-6247e08a96 (epel-release-9-11.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.