Bug 2131729 - Repository sets does not work on new host details page
Summary: Repository sets does not work on new host details page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.12.0
Assignee: Partha Aji
QA Contact: Shweta Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-03 13:59 UTC by Peter Dragun
Modified: 2023-01-17 18:56 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-katello-4.5.0.20-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:35:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
old_ui (85.99 KB, image/png)
2022-10-03 13:59 UTC, Peter Dragun
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35596 0 Normal Closed Repository Sets does not list reposets 2022-10-06 16:40:19 UTC
Red Hat Issue Tracker SAT-13237 0 None None None 2022-10-03 15:39:08 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:35:57 UTC

Description Peter Dragun 2022-10-03 13:59:50 UTC
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:

Comment 2 Peter Dragun 2022-10-04 12:15:29 UTC
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.

Comment 3 Partha Aji 2022-10-05 02:38:04 UTC
Connecting redmine issue https://projects.theforeman.org/issues/35596 from this bug

Comment 4 Bryan Kearney 2022-10-05 04:04:31 UTC
Upstream bug assigned to paji

Comment 5 Bryan Kearney 2022-10-05 04:04:33 UTC
Upstream bug assigned to paji

Comment 6 Bryan Kearney 2022-10-06 16:04:42 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35596 has been resolved.

Comment 8 Silas Pusateri 2022-10-12 11:45:30 UTC
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

Comment 13 errata-xmlrpc 2022-11-16 13:35:51 UTC
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


Note You need to log in before you can comment on or make changes to this bug.