Bug 2097751

Summary:	Traceback in production.log while trying to remediate issue from c.r.c when inventory status on satellite is not synced.
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	RH Cloud	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	aruzicka, ehelms, sshtein
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Reopened, Triaged
Target Release:	Unused
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:	2024-06-06 12:23:13 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 Jameer Pathan 2022-06-16 12:59:24 UTC

Description of problem:
Traceback in production.log while trying to remediate issue from c.r.c when inventory status on satellite is not synced.

Version-Release number of selected component (if applicable):
- Satellite 6.11.0 snap 25
- rubygem-foreman_rh_cloud-5.0.39-1.el8sat.noarch

How reproducible:
- Tried once

Steps to Reproduce:
1. Configure RHC on Satellite (Go to Configure > Inventory upload > Click on "Configure Cloud Connector" button.)
2. Register Host with satellite and Insights.
3. Try to remediate Insights issue from c.r.c
4. Check /var/log/foreman/production.log on Satellite.

Actual results:
- Traceback with following message.
2022-06-16T08:02:20 [W|app|5b7270f6] Some hosts were not found/ignored. 
Looked for: ["1c9ddase4-2764-439a-bc54-b390dasb73f1", 
"c8dsa2809-bc9a-46be-90f0-91385das6d5bb"], found ids: []

Expected results:
- No traceback in production.log
- Proper error message shown either on c.r.c or Satellite.

Additional info:
- This happens when the inventory status on satellite is not synced.
(Go to Configure > Inventory upload > Click on "Sync Inventory status".)

Comment 2 Shimon Shtein 2022-06-16 13:06:01 UTC

This will need a change in the code to avoid executing a REX job on an empty list of hosts.

Comment 3 Brad Buckingham 2022-06-16 14:02:55 UTC

*** Bug 2097749 has been marked as a duplicate of this bug. ***

Comment 5 Brad Buckingham 2023-11-02 17:44:31 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Brad Buckingham 2023-12-01 18:26:35 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 9 Eric Helms 2024-06-06 12:23:13 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.