Created attachment 1915717 [details] old_ui Description of problem: Repository sets are not working on the new host details page, but they can be viewed on the old Content host page. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Register host 2. Add manifest with SCA and enable some repo, e.g. SAT client 3. Navigate to Hosts->Content host-> $hostname -> Repository sets 4. Verify that you can see the repo that you enabled in old UI 5. Navigate to Hosts->All hosts-> $hostname -> Content-> Repository sets Actual results: No repository sets in the new UI, but I can see them in the old one. Expected results: The new UI should show the same repository sets as the old one. Additional info:
After some testing, I have found out that you also need to clear all statuses on the new host details page before adding repos. Updated Steps to Reproduce: Steps to Reproduce: 1. Register host 2. Clear all host statuses on the host in new host UI 3. Add manifest with SCA and enable some repo, e.g. SAT client 4. Navigate to Hosts->Content host-> $hostname -> Repository sets 5. Verify that you can see the repo that you enabled in old UI 6. Navigate to Hosts->All hosts-> $hostname -> Content-> Repository sets Additional info: A workaround is just to run the `subscription-manager` command that will report subscription status (e.g. subscription-manager refresh). Updating the severity of this BZ, as this scenario is less likely to occur.
Connecting redmine issue https://projects.theforeman.org/issues/35596 from this bug
Upstream bug assigned to paji
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35596 has been resolved.
Verified. Version Tested: 6.12.0 snap 14 Steps 1. Ensure Org has simple content access 2. Create a Custom repository 3. Register a host 4. Go to host => manage statuses 5. Remove the subscription status 6. Now go to the repository sets page Results: Custom repository and other repo sets are displayed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:8506