Title: Replacing the Red Hat Enterprise Virtualization Manager SSL Certificate Describe the issue: It is unclear what constraints the resulting CA needs to work for rhevm Suggestions for improvement: A walk through of generating and signing the CA for rhev with the required CA options and constraints would be handy (using openssl). A description of how rhev uses this CA and the resulting certificates would also assist in troubleshooting Additional information: having a broken cert in place prevents engine-log-collector from collecting the information to get appropriate support from GSS
Is the /etc/pki/ovirt-engine/keys/apache.p12 actually accessed ? Should /etc/pki/ovirt-engine/apache-ca.pem contain a CA certificate based on the hostname? Should it also have appended all intermediate CA certificates?
*** This bug has been marked as a duplicate of bug 1122895 ***