Description of problem: When I specify hostname in /etc/hostname which is different than hostname registration code detects it should be used (same as /etc/sysconfig/network in RHEL). Version-Release number of selected component (if applicable): rhn-client-tools-1.6.46-2.fc17.noarch rhnlib-2.5.49-2.fc17.noarch How reproducible: always Steps to Reproduce: 1. Set hostname to something != your fqdn in /etc/hostname and use `hostname` command to set that hostname in your shell 2. Run rhn-profile-sync and make sure your hostname in RHN Satellite changes Actual results: I still see mine fqdn instead of string set in /etc/hostname returned by client.system.getNetwork()['hostname'] Expected results: Hostname should be set to what is in /etc/hostname Additional info: This behavior is in due to bug 457953.
Okay, so: it's not `hostname`, it just running hostname. And, it's not just running hostname, it's running hostname with a parameter. So, kinda like hostname `cat /etc/hostname`
*** This bug has been marked as a duplicate of bug 882174 ***
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.