Red Hat Bugzilla – Bug 1428499
add setting to change host name setting between fqdn and shortname
Last modified: 2017-03-06 03:38:05 EST
Some users want their hosts to be created without a domain name. This would involve using the 'network.hostname' property instead of hte 'network.fqdn' or 'network.hostname-override' fact
Created from redmine issue http://projects.theforeman.org/issues/17102
Upstream bug assigned to jsherril@redhat.com
This adds a new setting 'register_hostname_fact' under Administer > Settings > Content that allows the user to specify which subscription manager fact to use for generating the name of the host (in the form of 'network.hostname')
Verified in Satellite 6.2.8 Snap 4 You can now set the "Subscription manager name registration fact" in Administer -> Settings -> Katello. To register a host with the fqdn, use the fact "network.fqdn". To register a host with a short name, use the fact "network.hostname". (see attached) Steps: 1. Set the registration fact to network.fqdn 2. Changed the hostname on the first system to a short name [root@cloud-qe-21 ~]# hostname cloud-qe-21.idmqe.lab.eng.bos.redhat.com [root@cloud-qe-21 ~]# hostname cloud-qe-21 [root@cloud-qe-21 ~]# hostname cloud-qe-21 [root@cloud-qe-21 ~]# hostname -f cloud-qe-21.idmqe.lab.eng.bos.redhat.com 3. Registered the system to Satellite. 4. Set the registration fact to network.hostname 5. Changed the hostname on the second system to a short name [root@yttrium ~]# hostname yttrium.idmqe.lab.eng.bos.redhat.com [root@yttrium ~]# hostnamectl set-hostname yttrium [root@yttrium ~]# hostname yttrium [root@yttrium ~]# hostname -f yttrium.idmqe.lab.eng.bos.redhat.com 6. Registered the system Results: The first system was correctly registered with its fqdn, and the second system was correctly registered with its short hostname. I put them in a host collection to be more easily seen. (see attached)
Created attachment 1259539 [details] new setting
Created attachment 1259540 [details] verification screenshot
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0447