Bug #21898
closedsatellite-change-hostname does not uninstall old ssl certificate rpms
Description
After running satellite-change-hostname to change the hostname of the satellite server, it does not uninstall old ssl certificate rpms.
Version-Release number of selected component (if applicable):
Sat 6.3 SNAP 26
After successful execution of satellite-change-hostname command, below rpms which provide ssl certifiate are still present:
Old Hostname: baga.gsslab.pnq.redhat.com
New Hostname: dhcp210-90.gsslab.pnq.redhat.com
baga.gsslab.pnq.redhat.com-qpid-router-server-1.0-1.noarch
baga.gsslab.pnq.redhat.com-tomcat-1.0-1.noarch
baga.gsslab.pnq.redhat.com-puppet-client-1.0-1.noarch
baga.gsslab.pnq.redhat.com-foreman-client-1.0-1.noarch
baga.gsslab.pnq.redhat.com-foreman-proxy-1.0-2.noarch
baga.gsslab.pnq.redhat.com-qpid-client-cert-1.0-1.noarch
baga.gsslab.pnq.redhat.com-foreman-proxy-client-1.0-1.noarch
baga.gsslab.pnq.redhat.com-apache-1.0-1.noarch
baga.gsslab.pnq.redhat.com-qpid-router-client-1.0-1.noarch
baga.gsslab.pnq.redhat.com-qpid-broker-1.0-1.noarch
dhcp210-90.gsslab.pnq.redhat.com-qpid-router-server-1.0-5.noarch
dhcp210-90.gsslab.pnq.redhat.com-qpid-client-cert-1.0-5.noarch
dhcp210-90.gsslab.pnq.redhat.com-foreman-proxy-client-1.0-5.noarch
dhcp210-90.gsslab.pnq.redhat.com-qpid-router-client-1.0-5.noarch
dhcp210-90.gsslab.pnq.redhat.com-tomcat-1.0-5.noarch
dhcp210-90.gsslab.pnq.redhat.com-puppet-client-1.0-5.noarch
dhcp210-90.gsslab.pnq.redhat.com-apache-1.0-5.noarch
dhcp210-90.gsslab.pnq.redhat.com-qpid-broker-1.0-5.noarch
dhcp210-90.gsslab.pnq.redhat.com-foreman-proxy-1.0-6.noarch
dhcp210-90.gsslab.pnq.redhat.com-foreman-client-1.0-5.noarch
SSL based connection for browser and clients work without any problem, so I think just we need to make sure we remove old ssl certificate rpms also.