Bug 2229897 - Remediation from CRC via Satellite shows "Failed" status even after successful remediation of Insights recommendations.
Summary: Remediation from CRC via Satellite shows "Failed" status even after successfu...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Cloud Connector
Version: 6.13.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.14.0
Assignee: satellite6-bugs
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-08 06:54 UTC by Jameer Pathan
Modified: 2023-08-18 00:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot of failed job (185.36 KB, image/png)
2023-08-08 06:54 UTC, Jameer Pathan 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19423 0 None None None 2023-08-08 06:57:46 UTC

Description Jameer Pathan 2023-08-08 06:54:53 UTC 
Created attachment 1982236 [details]
Screenshot of failed job

Description of problem:
Remediation from CRC via Satellite shows "Failed" status even after successful remediation of Insights recommendations.

Version-Release number of selected component (if applicable):
- Satellite 6.13.3 
- rubygem-foreman_rh_cloud-7.0.45-1.el8sat.noarch

How reproducible:
- Always

Steps to Reproduce:
1. Enable cloud connector plugin for satellite
2. Check Satellite shows available status on the sources page on console.redhat.com
3. Register host/s with Satellite and Insights.
4. Perform Inventory upload
5. Try to remediate insights issues from console.redhat.com

Actual results:
- The job status on c.r.c is "Running" even after the issues are remediated for the host. This status eventually turns into "Failed".

Expected results:
- The status of the remediation job on c.r.c should be "Succeeded".

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