Description of problem:
when virt-who is installed in a KVM server and the same is already registered to satellite, the machine will get renamed from fqdn to virt-who-fqdn. This seems to be interesting. However, there are some customers executing jobs to those servers as well, once the virt-who is updated, the information get updated and the fqdn now is something like virt-who-fqdn-<org_id>. After that, the customer is not able anymore to execute/push jobs to the kvm servers as well.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
"Error initializing command: SocketError - getaddrinfo: Name or service not known"

Expected results:
the name still the same and/or the customer be able to enable/disable this fqdn rename. At the end of the day, the job command should be executed properly.

Additional info: