Description of problem:

Issues on sat6.16 when provisioning rhel9

How reproducible:

100% (you can check in the attached video)

Is this issue a regression from an earlier version:

Not sure.

Steps to Reproduce:

1. Enable and sync all the repos

2. Create the ak + hostgroup + subnet

3. Try the provisioning, using fdi for instance

Actual behavior:
one entry localhost.localdomain will get created, and the server will get registered on this entry (localhost.localdomain). You can also confirm that when executing "subscription-manager identity" on the new rhel9 content host

Also, whenever moving on to deploy a second one, it will fail, once there is already a localhost.localdomain registed on Satellite, and the installation will stop

Expected behavior:
Move on with the deploy/installation/registration with no problem, and use the correct FQDN during the registration, and not localhost.localdomain

Business Impact / Additional info: