Project

General

Profile

Actions

Bug #29562

closed

Repo override in activation key does not reflect in RHEL hosts after change in repository sets

Added by Besmir Zanaj about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Repositories
Target version:
-
Difficulty:
medium
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Basically assume I have a RHEL system where my <Product Key> is providing 7Server and extras repository.
All systems are using the same key and have functioning repos and updates are smooth.
On a second time, I try to sync from upstream the optional repo.
1. add the repo in "Redhat Repositories
2. sync it
3. confirm it is in the "Red Hat Enterprise Linux Server" product as synced successfully
4. Update the Content View that the <Product Key> is using for the rhel repos to include this new "optional" repo
5. Finally override to enabled the repo "optional" in <Product Key>

Expected output:
all RHEL systems to be able to use the newly presented repo immediately or after a subscription-manager refresh action

Actual output:

"subscrption-manager repos" lists the new repo as disabled at all times. I have to manually enable the repo:

subscription-manager repos --enable=rhel7-server-optional-rpms

Actions #1

Updated by Besmir Zanaj about 5 years ago

  • Subject changed from Repo override in activation key does not reflect in RHEL hosts to Repo override in activation key does not reflect in RHEL hosts after change in repository sets
Actions #2

Updated by Jonathon Turel about 5 years ago

The overridden repos on an Activation Key only take effect at registration time. I think the easiest thing to do after registration is update the repository sets for your hosts in bulk. See Hosts -> Content Hosts -> Manage Repository Sets (dropdown at top right).

Let us know if that works for you.

Actions #3

Updated by Besmir Zanaj about 5 years ago

not sure how to add a new comment here so adding this thing/comment.

Jonathon Turel your recommendation worked. I was assuming there was no need for re-registration.

Have a good one

Actions #4

Updated by Besmir Zanaj about 5 years ago

  • Category set to Repositories
  • Status changed from New to Resolved
  • Assignee set to Besmir Zanaj
  • Difficulty set to medium
  • Triaged changed from No to Yes
Actions

Also available in: Atom PDF