Bug 2066892 - Duplicated hypervisors showing as virtual and physical respectively with identical UUIDs at cloud.redhat.com [NEEDINFO]
Summary: Duplicated hypervisors showing as virtual and physical respectively with iden...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Insights
Version: 6.10.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Shimon Shtein
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-22 17:08 UTC by Anthony Hogbin
Modified: 2023-07-11 13:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
bcourt: needinfo? (ahogbin)
sshtein: needinfo? (ahogbin)


Attachments (Terms of Use)

Comment 1 Steve Arnold 2022-03-23 09:03:12 UTC
We believe this is a result of the satellite server containing virt-who mappings for RHV servers.  The customer's account no longer has VDC subscriptions.  So we would expect subscription watch to count each RHV host and RHV guest as a separate subscription, and for there to be no nested servers in the server list in subscription watch.

We have tried deleting the inventory from console.redhat.com - however when satellite reports again, we still see the nested entries.

Satellite only has one entry for each RHV host - and there does not appear to be anyway of removing the virt-who mappings from the satelite inventory.

The customer has stopped all virt-who services on the RHV hosts.

Comment 2 Rich Jerrido 2022-03-23 10:53:24 UTC
Some useful data that would be helpful in troubleshooting:

• does the customer have the rh_cloud plugin enabled? (It is enabled by default on new installations of Satellite >= 6.9)
• can we get the output of the rh_cloud plugin available (either attached to this BZ or provided via a support case). That'll help identify if the 'data being sent is incorrect' or if 'the data is being interpreted incorrectly'.


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