[Users] Not able to add node 2.3 to ovirt-engine 3.1
Good morning, I have installed oVirt 3.1 over Fedora 17. When approving oVirt node it is added install fails. There is no output to engine.log or vdsm.log in the node whatsoever. It just fails. Is there a particular ovirt-node-iso version to be used with version 3.1 of the manager? Only problem I see in the system is that sometimes service libvirtd complains about not finding /etc/libvirt/krb5.tab and virsh is not accesible. Regards, Jose garcia
Hi Jose, On 06/22/2012 05:18 AM, jose garcia wrote:
Good morning,
I have installed oVirt 3.1 over Fedora 17. When approving oVirt node it is added install fails. There is no output to engine.log or vdsm.log in the node whatsoever. It just fails. Is there a particular ovirt-node-iso version to be used with version 3.1 of the manager?
Only problem I see in the system is that sometimes service libvirtd complains about not finding /etc/libvirt/krb5.tab and virsh is not accesible.
A few logs should be generated in /tmp/vds_* in the node side. Can you please check or attach these logs? -- Cheers Douglas
On 06/22/2012 01:21 PM, Douglas Landgraf wrote:
Hi Jose,
On 06/22/2012 05:18 AM, jose garcia wrote:
Good morning,
I have installed oVirt 3.1 over Fedora 17. When approving oVirt node it is added install fails. There is no output to engine.log or vdsm.log in the node whatsoever. It just fails. Is there a particular ovirt-node-iso version to be used with version 3.1 of the manager?
Only problem I see in the system is that sometimes service libvirtd complains about not finding /etc/libvirt/krb5.tab and virsh is not accesible.
A few logs should be generated in /tmp/vds_* in the node side. Can you please check or attach these logs?
Version 2.3 uses the 3.0 protocol not the 3.1 protocol. There 2.4 has issues and wont register currently that is waiting on a fix to go in. In theory you could use the 2.3 iso to talk to a data center setup for 3.0 but I am not sure if anyone has tested that or not. Thanks Robert
On 06/22/2012 06:21 PM, Douglas Landgraf wrote:
Hi Jose,
On 06/22/2012 05:18 AM, jose garcia wrote:
Good morning,
I have installed oVirt 3.1 over Fedora 17. When approving oVirt node it is added install fails. There is no output to engine.log or vdsm.log in the node whatsoever. It just fails. Is there a particular ovirt-node-iso version to be used with version 3.1 of the manager?
Only problem I see in the system is that sometimes service libvirtd complains about not finding /etc/libvirt/krb5.tab and virsh is not accesible.
A few logs should be generated in /tmp/vds_* in the node side. Can you please check or attach these logs?
Hi, I am afraid there are only an ovirt.log and an ovirt-setup.tty2, both empty. I have resolved my problem with libvirt, though.
On 06/22/2012 12:43 PM, jose garcia wrote:
On 06/22/2012 06:21 PM, Douglas Landgraf wrote:
Hi Jose,
On 06/22/2012 05:18 AM, jose garcia wrote:
Good morning,
I have installed oVirt 3.1 over Fedora 17. When approving oVirt node it is added install fails. There is no output to engine.log or vdsm.log in the node whatsoever. It just fails. Is there a particular ovirt-node-iso version to be used with version 3.1 of the manager?
Only problem I see in the system is that sometimes service libvirtd complains about not finding /etc/libvirt/krb5.tab and virsh is not accesible.
A few logs should be generated in /tmp/vds_* in the node side. Can you please check or attach these logs?
Hi,
I am afraid there are only an ovirt.log and an ovirt-setup.tty2, both empty.
I have resolved my problem with libvirt, though.
ah, I misunderstood. I thought you were using Fedora17 as Node, sorry. Glad that you have resolved your problem. Cheers Douglas -- Cheers Douglas
On 06/22/2012 06:51 PM, Douglas Landgraf wrote:
On 06/22/2012 12:43 PM, jose garcia wrote:
On 06/22/2012 06:21 PM, Douglas Landgraf wrote:
Hi Jose,
On 06/22/2012 05:18 AM, jose garcia wrote:
Good morning,
I have installed oVirt 3.1 over Fedora 17. When approving oVirt node it is added install fails. There is no output to engine.log or vdsm.log in the node whatsoever. It just fails. Is there a particular ovirt-node-iso version to be used with version 3.1 of the manager?
Only problem I see in the system is that sometimes service libvirtd complains about not finding /etc/libvirt/krb5.tab and virsh is not accesible.
A few logs should be generated in /tmp/vds_* in the node side. Can you please check or attach these logs?
Hi,
I am afraid there are only an ovirt.log and an ovirt-setup.tty2, both empty.
I have resolved my problem with libvirt, though.
ah, I misunderstood. I thought you were using Fedora17 as Node, sorry. Glad that you have resolved your problem.
Cheers Douglas
I have to use a fedora 17 for the node side too, then. Well, let's try again. At least I won't have to use that curious ovirt-node installer. Thank you.
participants (3)
-
Douglas Landgraf -
jose garcia -
Robert Middleswarth