Issue

DISCLAIMER: THIS IS NOT A VALID RESOLUTION. IF YOUR CUSTOMER HITS THIS ISSUE, PLEASE ASK HIM NOT TO UPGRADE OTHER HOSTS TO RHEL6 AND REMAIN IN 2.2 COMPATIBILITY MODE TILL THIS ISSUE IS RESOLVED (CONTACT MKU|HANNAH FOR QUESTIONS).

Detailed Issue: migration tool was used to move from 2.2 to 3.0 setup. Can't approve 6.2 host / live migration fails.
Resolution: stay with RHEL5 hosts.
Root Cause: this KB fixes only the libvirtd start issue, but does not fix the live migration issue. Work in progress.

----------------------------------

If you are unable to add a node to the RHEV manager, it could be that libvirtd is failing to start on the hypervisor. The following log message in the node's libvirtd.log is an indication that you are being affected by the problem.

virNetTLSContextCheckCertPair:483 : Our own certificate /etc/pki/vdsm/certs/vdsmcert.pem failed validation against /etc/pki/vdsm/certs/cacert.pem: The certificate is not trusted.