** Note that this is a public ticket, please refrain from adding any sensitive data. **

Description of Problem

 Inconsistency in system display names when customers use both subscription-manager and insights-client. The issue occurs when a customer registers their system with both tools but provides a --display-name to insights-client and not subscription-manager. In this case, the system's display name in the console.redhat.com inventory is not consistent. The root cause is that Errata Notifications syncs data from RHSM to HBI and sets the display name of the host to the consumer name in Candlepin. If no --name is provided during registration, the default name is the host name, which causes inconsistency when the insights-client has a different name.

Systems that aren't registered with an explicit -name end up using the FQDN (Fully Qualified Domain Name) as the system name, which can override any name set by the insights-client register  --display-name . This means that if a customer only sets their system name using the insights-client, it will be replaced by the FQDN when RHSM (Red Hat Subscription Manager) performs the check-in.

How reproducible

Always

Steps to Reproduce

1. Register the system without specifying any consumer name

subscription-manager register

1. Register the system with insights-client by specifying a display name:

insights-client register --display-name my_display_name

Expected Behavior

There should be a permanent solution to address this issue and prevent the inconsistency moving forward. We would like to know the best recommended process that customers should follow when registering their systems to avoid this issue in the future. This should be documented as there could be one or more reporters for the same system in HBI.

Business Impact / Additional info

https://issues.redhat.com/browse/CHAINSAW-333