Trouble activating new hosts - SSL certificate

Latest response

This issue is similar to the discussion at the following URL.  However, since that discussion is so long, I have started a new discussion.

 

https://access.redhat.com/discussion/trouble-activating-host-rhev30

 

After reconfiguring the networking for RHEV, I have had trouble activating new hosts.  I believe that this happens because the ssh public key doesn't get downloaded to RHEV-H so it can't be activated by RHEV-M.

 

From the earlier discussion, it seems that you are required to enter the FQDN of RHEV-M when registering a new RHEV-H.  In order words, it seems that using an IP address in place of the FQDN doesn't work.  Would using an IP address instead of an FQDN cause problems with activating a new RHEV-H?

Responses

It seems that this issue was not due to the use of IP address (instead of FDQN) when registering a host.

 

I found that the error message in the vdsm-reg.log file was similar to that in the following KB article:

 

https://access.redhat.com/knowledge/solutions/126233

 

It seems that the problem was that the commercial SSL certificate that I had installed in JBOSS had to be made available to the hosts.  I concatenated the ca-bundle.crt file from /etc/pki/tls/certs with the intermediate certificate provided by the CA.  As per the above KB article, I stored the file in /var/lib/jbossas/server/thevm-slimmed/deploy/ROOT.war.  After that, I was able to activate hosts in RHEVM.

I'm glad you were able to resolve this issue, Aram. Thanks for following up with the solution.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.