Description of problem:

When provisioning rhel9+ via fdi using static network information, localhost.localdomain will be created on Satellite webUI

We got a similar issue long ago, and it was already fixed, the main difference here is that, before, we were using the DHCP, and now, it's static.

How reproducible:

100%

Is this issue a regression from an earlier version:

no

Steps to Reproduce:

1. Setup satellite for provisioning (rhel9)

2. FDI, using static network information

3. Start the provisioning of rhel9

Actual behavior:
Initially, the content host will be created on Satellite, and once the VM reaches the rhsm call, a new entry will be created on satellite, called localhost.localdomain

Expected behavior:
The same content host entry should be used. During the rhsm call, the Content Host should already know the hostname, which is not the case.

Business Impact / Additional info: