Trouble activating host on RHEV3.0

hellmet · 03-29-2012, 03:45 AM

Here's the setup:

60day RHEV 3.0 evaluation.
RHEV Virtualization Manager running on a VM
RHEV Hypervisor running on a Dell laptop with virtualization enabled

Trouble:
Adding the host to the Default cluster is not an issue. However, trying to "Activate" the host results in a "Host xxxx is non-responsive" error in the Events tab.

Trouble is that I do not even know where to begin to check for issues.

Can someone here point me to where I can possibly start looking - logs etc - so I can get past this issue?

A bit of search took me to "vdsm" so I started looking...

One thing I noticed in the vdsm log on the RHEV Hypervisor (if of any use) - /var/log/vdsm/vdsm.log - is :

Code:

MainThread::ERROR::2012-03-29 08:16:12,103::vdsm::74::vds::(run) Traceback (most recent call last):
  File "/usr/share/vdsm//vdsm", line 72, in run
    serve_clients(log)
  File "/usr/share/vdsm//vdsm", line 40, in serve_clients
    cif = clientIF.clientIF(log)
  File "/usr/share/vdsm/clientIF.py", line 92, in __init__
  File "/usr/share/vdsm/libvirtconnection.py", line 94, in get
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 102, in openAuth
libvirtError: authentication failed: authentication failed

and trying to start vdsmd results in:

Code:

/etc/init.d/vdsmd start
vdsm: Missing certificates, vdsm not registered            [FAILED]
Starting iscsid: 
Starting up vdsm daemon: 
vdsm start                                                 [  OK  ]

dyasny · 03-29-2012, 05:22 AM

First of all, if you want help with RHEV, the best place is the Red Hat User Groups, at https://access.redhat.com/groups/red...virtualization - you get both Red Hat associates helping out with issues, and other users who already have experience working with RHEV in there

Now, about your problem - it's quite obvious, but you need to understand how RHEV Hypervisor is registered to RHEV-Manager first. RHEV-Hypervisor contacts RHEV-Manager, reports its parameters, and receives a signed certificate, which is later on used to encrypt the communication between the two systems. Obviously that didn't happen, hence the missing certificate in the vdsm startup output, and if there's no communication, because encryptions hadn't been set up, the host will be non responsive, as far as RHEV-Manager is concerned.

You need to check why the certificate exchange didn't happen, but before you do that, make sure all the prerequisites are in place - DNS name resolution works in all directions (RHEV-M can lookup RHEV-H and vice versa, and both have PTR records as well), then remove the host, and try to add it again.

hellmet · 03-29-2012, 06:16 AM

Quote:

Originally Posted by dyasny

First of all, if you want help with RHEV, the best place is the Red Hat User Groups, at https://access.redhat.com/groups/red...virtualization - you get both Red Hat associates helping out with issues, and other users who already have experience working with RHEV in there

Now, about your problem - it's quite obvious, but you need to understand how RHEV Hypervisor is registered to RHEV-Manager first. RHEV-Hypervisor contacts RHEV-Manager, reports its parameters, and receives a signed certificate, which is later on used to encrypt the communication between the two systems. Obviously that didn't happen, hence the missing certificate in the vdsm startup output, and if there's no communication, because encryptions hadn't been set up, the host will be non responsive, as far as RHEV-Manager is concerned.

You need to check why the certificate exchange didn't happen, but before you do that, make sure all the prerequisites are in place - DNS name resolution works in all directions (RHEV-M can lookup RHEV-H and vice versa, and both have PTR records as well), then remove the host, and try to add it again.

Thank you for the link to User Groups.
Coming to DNS resolution, I'm using IP both ways to connect instead of using hostnames. Do you think that would be an issue?

dyasny · 03-29-2012, 06:26 AM

Quote:

Originally Posted by hellmet

Thank you for the link to User Groups.
Coming to DNS resolution, I'm using IP both ways to connect instead of using hostnames. Do you think that would be an issue?

yes, RHEV uses FQDNs almost everywhere, DNS resolution with PTR records in place is a prerequisite

hellmet · 04-02-2012, 04:46 AM

IT added the necessary DNS records for both the hypervisor and the RHEV Manager machines. Both machines now talk to each other with FQDNs. However, my issue continues to exist...