Description of problem: If we generate a certificate to change the FQDN part of the hostname value, the new certificate generated is still using the old FQDN Version-Release number of selected component (if applicable): spacewalk-certs-tools-1.1.1.1 How reproducible: all the time Steps to Reproduce: 1.rhn-ssl-tool --gen-server -v --set-hostname="test.broken.fqdn" --set-country="GB" --set-state="Hampshire" --set-city="Raleigh" --set-org="Red Hat" --set-org-unit="GSS EMEA" --set-email="emea-gss-lab" 2.rhn-ssl-tool --gen-server -v --set-hostname="test.fixed.fqdn" --set-country="GB" --set-state="Hampshire" --set-city="Raleigh" --set-org="Red Hat" --set-org-unit="GSS EMEA" --set-email="emea-gss-lab" Actual results: the new certificate generated still uses the old fqdn ; the hostname field is not altered in the .cnf file that's used in the generation either Expected results: a new certificate with the new fqdn is generated Additional info: it is possible to manually fix this by changing the hostname value in the .cnf file to what's supposed to be used. this also happens when the first hostname was given without any fqdn on the first time.
Making bugzilla public.
Fixed in Spacewalk master, eb03cacd442bc4819a9f62c16fb23a0adb169148.