Bug 1859601

Summary: activation key mapped to a CV requires to force 'Enable (overridden)' repositories, when in Organization Environment Access ( Simple Content Access)
Product: Red Hat Satellite Reporter: Daniel Leroux <dleroux>
Component: Subscription ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Cole Higgins <chiggins>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: ahumbe, akarimi, aludwar, dhjoshi, dsynk, saydas
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-02 09:40:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Leroux 2020-07-22 14:54:01 UTC
Description of problem:
----------------------
When running a Satellite in Simple Content Access mode.
After having synchronized repositories and created a CV and activation key
if the Repository Sets (under activation key) are left to their defaults, registering a host with the satellite won't enable ANY repo, even some are listed as 'Enabled' in the GUI.

On the other end, if the repos are forced to 'Enabled (overridden)' in the activation key, then registering a system with the satellite will get these repositories enabled

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
Satellite 6.7.1 ( on my specific environment )
candlepin-selinux-2.9.25-1.el7sat.noarch
candlepin-2.9.25-1.el7sat.noarch


How reproducible:
-----------------
Every time and this is documented in length under case #02707433

Steps to Reproduce:
1. Sync repositories
2. Create CV with above repositories
3. Create an activation key which matches the CV created in step 2,
   the activation key should match the proper Release Version
   and Environment as well.
4. Do not attach any subscription to the activation key
5. Leave the Repository Sets to it's defaults.
6. Register a system with the satellite using the activation key

Actual results:
  # subscription-manager register --org="Vandelay" --activationkey="ak7"
      The system has been registered with ID: eb8f4457-3e91-4785-bc08-369f4169f361
      The registered system name is: serva.nleroux.ca
      Installed Product Current Status:
      Product Name: Red Hat Enterprise Linux Server
      Status:       Not Subscribed

  # yum repolist
       Loaded plugins: product-id, search-disabled-repos, subscription-manager

       This system is registered with an entitlement server, but is not receiving updates. You can use subscription-manager to assign subscriptions.

       repolist: 0






Expected results:
######  Whereas if the list of Repository Sets are forced to "Enabled (overridden)", the repositories WILL be enabled when registering the system with the activation key.

All same steps as above, but this time:
  [root@serva ~]# yum repolist
Loaded plugins: product-id, search-disabled-repos, subscription-manager

This system is registered with an entitlement server, but is not receiving updates. You can use subscription-manager to assign subscriptions.

rhel-7-server-extras-rpms                                | 2.0 kB     00:00     
rhel-7-server-optional-rpms                              | 1.8 kB     00:00     
rhel-7-server-rh-common-rpms                             | 2.1 kB     00:00     
rhel-7-server-rpms                                       | 2.0 kB     00:00     
rhel-7-server-satellite-tools-6.7-rpms                   | 2.1 kB     00:00     
(1/15): rhel-7-server-extras-rpms/x86_64/group             |  124 B   00:00     
(2/15): rhel-7-server-extras-rpms/x86_64/updateinfo        | 236 kB   00:00     
(3/15): rhel-7-server-extras-rpms/x86_64/primary           | 396 kB   00:00     
(4/15): rhel-7-server-optional-rpms/x86_64/group           |  22 kB   00:00     
(5/15): rhel-7-server-rh-common-rpms/x86_64/group          |  124 B   00:00     
(6/15): rhel-7-server-rh-common-rpms/x86_64/updateinfo     |  34 kB   00:00     
(7/15): rhel-7-server-rh-common-rpms/x86_64/primary        |  68 kB   00:00     
(8/15): rhel-7-server-optional-rpms/x86_64/updateinfo      | 2.7 MB   00:00     
(9/15): rhel-7-server-optional-rpms/x86_64/primary         | 5.9 MB   00:00     
(10/15): rhel-7-server-rpms/x86_64/group                   | 631 kB   00:00     
(11/15): rhel-7-server-satellite-tools-6.7-rpms/x86_64/gro |  124 B   00:00     
(12/15): rhel-7-server-rpms/x86_64/updateinfo              | 3.7 MB   00:00     
(13/15): rhel-7-server-satellite-tools-6.7-rpms/x86_64/upd | 7.4 kB   00:00     
(14/15): rhel-7-server-satellite-tools-6.7-rpms/x86_64/pri |  22 kB   00:00     
(15/15): rhel-7-server-rpms/x86_64/primary                 |  45 MB   00:01     
rhel-7-server-extras-rpms                                             1303/1303
rhel-7-server-optional-rpms                                         21328/21328
rhel-7-server-rh-common-rpms                                            243/243
rhel-7-server-rpms                                                  29225/29225

Additional info:
case 02707433 documents this bug

Comment 2 Craig Donnelly 2020-08-31 14:27:38 UTC
*** Bug 1873966 has been marked as a duplicate of this bug. ***

Comment 3 Ashish Humbe 2020-10-02 09:40:48 UTC

*** This bug has been marked as a duplicate of bug 1862772 ***