When using both `network` and `rhsm` to install and register a system during installation, the system's hostname (as specified in `network`) is not properly recorded in rhsm / insights.

The following kickstart can be used to reproduce:

network  --hostname=<HOSTNAME> --bootproto=static --device=link --ip=<IP> --netmask=<NETMASK> --gateway=<GATEWAY> --nameserver=<DNS> --noipv6 --activate

rhsm --organization=<ORG_ID> --activation-key=<ACT_KEY> --connect-to-insights

After installation, the information in Insights (Hybrid Cloud Console) is not correct. While the "Host Name" and "Ansible hostname" fields likely will get populated on the next run of `insights-clients`, the "Display name" never does, and shows 'localhost.localdomain'.

SImilarly, `subscription-manager identity` also shows 'localhost.localdomain' on the booted system:

# subscription-manager identity
system identity: <UUID>
name: localhost.localdomain
org name: <ORG_NAME>
org ID: <ORG_ID>