[Ovirt-devel] ovirt see only 1 node. how to add other servers ?

[Perry Myers]

�� wrote:
> В Птн, 12/12/2008 в 10:31 -0500, Perry Myers пишет:
>> �� wrote:
>>> Hello
>>> i send identify information from second node starting
>>> "ovirt-identify-node -s 192.168.50.2 -p 12120 -d -v"
>>> but in listing "Hosts" hypervisor field  empty
>>> i think ovirt-appliance can't connect to libvirtd
>> Why are you running ovirt-identify-node manually?  That should run only as 
>> part of the Node bootup sequence automatically.
> 
> Automaticaly this query "dig +short -t srv _$1._$2.$(dnsdomainname)"
> from /etc/init.d/ovirt-functions haven't answer (i didn't configure dns
> for local zones).

DNS on the oVirt Appliance is provided by dnsmasq which provides the DNS 
SRV records that oVirt needs automatically.  The Appliance won't work with 
external DNS without major changes to it.

 From the .254 Node and the Appliance what is the output of:

dig +short -t srv _ovirt._tcp.priv.ovirt.org

>> Are you running that on the 192.168.50.254 host or is this a different 
>> physical machine?
> physical machine is 192.168.50.254 and 192.168.50.1

Ok

> ovirt-appliance virtual machine is 192.168.50.2 on 192.168.50.1

Ok

>> In the logs you sent, the only hosts that I can see that have tried to 
>> register with the Server are 192.168.50.254 and 192.168.50.1.  If there 
>> are other nodes that have tried to register, the host-browser daemon on 
>> the Appliance did not see them.  Can you give me the logs from these other 
>> nodes?
>>
>> I also saw errors like this in your host-status log:
>>
>>> Connecting to host 192.168.50.254
>>> libvir: Remote error : Failed to start SASL negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs found)
>> This could be a time synchronization issue.  Please run
>> date --utc
>> on both the host running the Appliance, the appliance and all nodes and 
>> let me know what the results are
> on all nodes time is Fri Dec 12 15:43:58 UTC 2008
> 			Fri Dec 12 15:43:49 UTC 2008
> 			Fri Dec 12 15:43:40 UTC 2008

Ok, so not a time sync issue then

>> Also, from your appliance in an ssh session try:
>>
>> klist
>> ping -c 1 192.168.50.254
>> virsh -c qemu+tcp://192.168.50.254/system list
>>
>> And give me the output for those commands.
> 
> [root at management ~]# klist 
> Ticket cache: FILE:/tmp/krb5cc_0
> Default principal: admin at PRIV.OVIRT.ORG
> 
> Valid starting     Expires            Service principal
> 12/12/08 14:13:19  12/13/08 14:13:19
> krbtgt/PRIV.OVIRT.ORG at PRIV.OVIRT.ORG
> 12/12/08 14:13:20  12/13/08 14:13:19
> ldap/management.priv.ovirt.org at PRIV.OVIRT.ORG
> 12/12/08 14:13:20  12/13/08 14:13:19
> HTTP/management.priv.ovirt.org at PRIV.OVIRT.ORG
> 
> 
> Kerberos 4 ticket cache: /tmp/tkt0
> klist: You have no tickets cached
> [root at management ~]# virsh -c qemu+tcp://192.168.50.254/system list
> libvir: Remote error : Failed to start SASL negotiation: -4 (SASL(-4):
> no mechanism available: No worthy mechs found)
> error: failed to connect to the hypervisor
> [root at management ~]# ping -c 1 192.168.50.254
> PING 192.168.50.254 (192.168.50.254) 56(84) bytes of data.
> 64 bytes from 192.168.50.254: icmp_seq=1 ttl=64 time=0.554 ms
> 
> --- 192.168.50.254 ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 0.554/0.554/0.554/0.000 ms

Ok, so we've ruled out a time sync issue.  And you have valid kerberos 
tickets on the appliance.  And we know the Node at .254 is running since 
you can ping it.

The next question is, does the Node have a valid kerberos ticket?  Can you 
give me the /var/log/ovirt.log file from the .254 Node?  And do you have 
an /etc/libvirt/krb5.tab file on the Node?

Perry