Bug 2015938

Summary: RHC stuck at "checking" if a Satellite connected system is also in the remediation plan
Product: Red Hat Hybrid Cloud Console (console.redhat.com) Reporter: John Spinks <jspinks>
Component: RemediationsAssignee: Rex White <rexwhite>
Status: CLOSED CURRENTRELEASE QA Contact: jaudet
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: cmarinea, fjansen, jaudet
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-16 15:25:50 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 John Spinks 2021-10-20 12:10:56 UTC 
Description of problem:

If you have a remediation plan that contains both one or more RHC systems AND one or more Satellite connected systems, when you click the Execute Playbook button the RHC system will be stuck at "checking".
You will not be able to execute the remediation plan on the RHC system.

Variations I have tested using the Vulnerability service:
RHC only = Ready
RHC + Direct Connected = Ready
RHC + Satellite = CHECKING
RHC + Satellite + Direct Connect = CHECKING

Version-Release number of selected component (if applicable):


How reproducible:

Always.
(Note - I used Vulnerability service.  I have not verified this with every service)

Steps to Reproduce:
1.Create a remediation plan with a RHC system.  
2.Click Execute playbook and note that the RHC host is "Ready"
3.Add a Satellite connected host to the same playbook (or a new playbook with both RHC and Satellite)
4. Click Execute playbook button.  Satellite system will be Ready and RHC system will be checking.



Actual results:
RHC status is "checking" and cannot be remediated.

Expected results:
RHC status is "ready" and can be remediated.

Additional info:
Comment 6 Rex White 2023-02-16 15:25:50 UTC 
Fixed in https://issues.redhat.com/browse/REMEDY-111