Description of problem: spacewalk-setup and spacewalk-hostname-rename presently only detect the shortname as would be returned by "uname -n", not the FQDN as would be detected by checking /etc/hosts, or a reverse DNS lookup in a correctly configured DNS environment. This causes SSL verification failure when clients make a request against against the FQDN. The SSL certificate has components populated with the shortname rather than FQDN, and as such verification fails when clients provide the FQDN because it doesn't match the shortname found in the SSL cert. It also causes the Spacewalk server name to be populated with the shortname which can cause problems for client registration and Inter Server Synchronisation AuthN. spacewalk-setup and spacewalk-hostname-rename should attempt to obtain the FQDN and only fallback to providing the shortname if all attempts to identify the FQDN fails. Version-Release number of selected component (if applicable): All How reproducible: On a system with the shortname in /etc/hostname or /etc/sysconfig/network, run spacewalk-setup or spacewalk-hostname-rename. The shortname will be detected and used to populate components of the SSL certificate.
Additionally, having a shortname detected by spacewalk-setup-jabberd causes SSL validation failure for jabberd clients and osa-dispatcher. spacewalk-setup-jabberd also updated to correctly detect the FQDN.
GitHub PR 625 created with proposed fix. ttps://github.com/spacewalkproject/spacewalk/pull/625
Additionally, add FQDN detection to spacecmd.
spacewalk f8a7cc0181e2fc3b0e49bb4cc79453289458a21d d5caec0bae9421ea792dda515732f02de6ac8283
Above commits have been reverted for 2.8, removing from space28
spacewalk 1bcde51c72fd569ba8e36a7f6bdf78e1967c6499 6a8bcfde37692bade3cf3882e7934cda47aa38a3
Move Spacewalk 2.9 bugs ON_QA.
Spacewalk 2.9 has been released. https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes29