Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

Verified 

Verified with:
- Satellite 6.14.0 snap 18
- rubygem-foreman_rh_cloud-8.0.50-1.el8sat.noarch

Test steps:
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

Observations:
- The status of the remediation job on c.r.c is "Succeeded".

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.14 security and bug fix update), 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-2023:6818