Description of Problem

When multiple Satellites collect data from the same vSphere infrastructure (via virt-who), the same hosts are reported multiple times to HCC/Lightspeed. These duplicates appear in inventory and result in subscriptions being counted more than once.

Today, the Satellite/HCC inventory payload does not populate provider_id and populate subscription_manager_id and satellite_id with different values. As a result, HBI host deduplication cannot consolidate records coming from different Satellites, even when they represent the same underlying host.

virt-who already collects a VM UUID for each host (vm_uuid) and use this value to populate bios_uuid fact. This UUID is consistent across reports from different Satellites for the same vSphere object and appears to correspond to the vSphere instance UUID.

Proposed Enhancement:

Populate provider_id in the Satellite inventory payload using the same value that populates bios_uuid. Populate provider_type }}with {{discovery }}as the underlying collector is {{{}qpc.

HBI treats provider_id as immutable and uses it to consolidate inventory records. This approach is already used by cloud providers (e.g. AWS) and would allow HBI to deduplicate hosts reported by multiple Satellites via virt-who.

Note: this should only be done in the case of virt-who. If Satellite manages hosts deployed in a public cloud, provider_id should be populated by the instance uuid. It is assumed virt-who is not used for hosts deployed on public clouds.

How reproducible

Always

Steps to Reproduce

1. [Step 1]
2. [Step 2]
3. [Step 3]

Actual Behavior

Customers running multiple Satellites against shared vSphere infrastructure experience inflated inventory counts and incorrect subscription usage.

Expected Behavior

Hosts should not be duplicated.

Business Impact / Additional info