Bug 2096399

Summary: When setting satellite server as source to apply remediation, the same is still as unkown on console.redhat.com
Product: Red Hat Hybrid Cloud Console (console.redhat.com) Reporter: Waldirio M Pinheiro <wpinheir>
Component: RemediationsAssignee: Rex White <rexwhite>
Status: CLOSED CURRENTRELEASE QA Contact: jaudet
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: cmarinea, egolov, fjansen, ktordeur, nowens
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-22 14:49:42 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 Waldirio M Pinheiro 2022-06-13 18:08:20 UTC
Description of problem:
After following the steps to configure satellite as a server to apply the remediation, the same is still on console.redhat.com as Unknow

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


How reproducible:
100%

Steps to Reproduce:
1. Install Satellite
2. Proceed with the steps mentioned here [1]
3. Register a content host to satellite
4. on console.redhat.com, track and create a remediation
5. Try to apply the remediation via console.redhat.com, applying it via satellite that should be the source for this scenario


[1]. https://access.redhat.com/documentation/en-us/red_hat_insights/2022/html-single/using_cloud_connector_to_remediate_issues_across_your_red_hat_satellite_infrastructure/index#proc-configuring-cloud-connector-on-satellite-server_remediating-satellite


Actual results:
Satellite it's not visible as source/gateway when trying to apply the remediation

Expected results:
Satellite should be with a status different from Unkown and it should be also visible when trying to apply the remediation.

Additional info: