Subscription Watch - How to fix inventory mismatch with cloud providers

Environment

Subscription Watch (This content is not included.This content is not included.https://cloud.redhat.com/subscriptions) with data coming from cloud providers.

Issue

On the Subscription Watch interface the message: "There may be inconsistencies between data in the graph and your inventory display" is displayed.

Resolution

• Solution 1
  Use the Insights client to register all systems to Insights. This action will cause the previously unknown systems to display in the current systems table, in addition to displaying in the graph.

• Solution 2
  Set accurate subscription attributes (RHEL system purpose data) in the RHEL image. Allow those settings to propagate to the instances to ensure that public cloud metering data matches the data from other data collection tools.

• Solution 3
  Set up public cloud metering for all AWS accounts by adding those accounts as sources in the Sources application. Because of the ability of public cloud metering to recognize an individual instance as running multiple times per day, instead of counting each occurrence of an instance separately, public cloud metering generally provides a more accurate instance count.

• Solution 4
  Wait 24 hours. If AWS instances have recently been provisioned or deprovisioned (for example, within the past 24 hours), the data mismatch might occur temporarily, but resolve over time.

Root Cause

When subscription watch detects a discrepancy between data from the sources defined for public cloud metering and data from other data collection tools, this message is shown.

The message might or might not indicate an issue with the configuration of the various data collection tools. The discrepancy results in a possible mismatch between data in the usage and utilization graph and the current systems table in the subscription watch interface.

The data mismatch usually appears in one of the three following ways in the subscription watch interface:

• More public cloud metering data appears in the graph than in the table.
  Public cloud metering is enabled through the Sources application. Because of this, it can report on systems that are not otherwise known to cloud.redhat.com, for example, systems that are not registered with Insights. If so, the data gathered by public cloud metering will show in the graph, but not in the table. The current systems table is a subset of data for the Inventory application, and the public cloud metering function does not supply data to the Inventory application, unlike the other data collection tools for subscription watch. (See solution 1.)

• Public cloud data is not appearing in the correct place in the table, for example, when I try to filter data.
  Public cloud metering data on systems is based on subscription attributes that are set during the image creation. For RHEL, these subscription attributes are also known as the system purpose values. If those values are modified after image creation or within the instance, then the values will be reflected incorrectly in public cloud metering data. This is because these values are gathered at the time that the image is inspected, at the time of source creation in the Sources application. (See solution 2.)

• Some of my public cloud data is missing or is not being counted correctly.
  Public cloud metering might not have permissions to gather system information for all relevant AWS systems in cloud.redhat.com, because they are not added as sources for public cloud meter data collection. (See solution 3.)

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.