Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
We are already aware of the Random Inventory Sync failure as reported in this BZ https://bugzilla.redhat.com/show_bug.cgi?id=2127180 and the customer had also hit the same issue initially.
That was solved by changing the scheduled time for Automated Inventory sync. But since then, despite the fact that insights-client is running fine on the host and Inventory sync is happening fine on satellite
* Some existing hosts in Satellite show Global Status "Warning" and "Inventory" status shows "Host was not uploaded to your RH Cloud Inventory"
* When we check the inventory sync\upload task details in satellite, certain hosts are marked as disconnected and concerned systems are part of that list.
* Surprisingly, The same system\set of systems shows up with OK status in console.redhat.com inventory.
Version-Release number of selected component (if applicable):
Satellite 6.11 ( and Satellite 6.12 )
How reproducible:
NA ( Only reproducible by the customer in his all four satellites which were at 6.11 and recently been upgraded to 6.12 )
Steps to Reproduce:
NA ( Only reproducible by the customer in his all four satellites which were at 6.11 and recently been upgraded to 6.12 )
Actual results:
As explained above
Expected results:
There should be no inconsistency in the Inventory status for a host in Satellite and console.redhat.com
Additional info:
* At some point, the customer mentioned that the issue went away for those existing hosts automatically.
* But for any newly build system, the same issue is reproducible i.e mismatch in status.
* Also to be noted, manual re-execution insights-client on client host or Inventory upload in satellite, does not help to immediately remediate the issue but it gets resolved for the host after some days on their own ( which does not seems like a correct behavior ).
We don't know if this is an after-effect of the BZ 2127180 or if it's something else but I thought I should mention the same here.
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.
Comment 21Red Hat Bugzilla
2024-10-05 04:25:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days