On 04/12/2013 12:40 AM, martin.krali...@accenture.com wrote:
Now I see where can be problem. In vdsm-reg.log are issues with https. The 
server has changed httpd certificate but certificate in node passed.

how did this look in the vdsm-reg log?


-----Original Message-----
From: Kralicek, Martin
Sent: Thursday, April 11, 2013 11:23 PM
To: 'Fabian Deutsch'
Cc: users@ovirt.org
Subject: RE: [Users] oVirt 3.2.1 and node 2.6.1


AIO is AllInOne I presume :)

Node: 2.6.1
Engine: 3.2.1 on Fedora 18
Components: from engine "yum list installed | grep ovirt"
otopi.noarch                         1.0.0-1.fc18                  @ovirt-stable
otopi-java.noarch                    1.0.0-1.fc18                  @ovirt-stable
ovirt-engine.noarch                  3.2.1-1.fc18                  @ovirt-stable
ovirt-engine-backend.noarch          3.2.1-1.fc18                  @ovirt-stable
ovirt-engine-cli.noarch                   @ovirt-stable
ovirt-engine-dbscripts.noarch        3.2.1-1.fc18                  @ovirt-stable
ovirt-engine-genericapi.noarch       3.2.1-1.fc18                  @ovirt-stable
ovirt-engine-restapi.noarch          3.2.1-1.fc18                  @ovirt-stable
ovirt-engine-sdk.noarch                   @ovirt-stable
ovirt-engine-setup.noarch            3.2.1-1.fc18                  @ovirt-stable
ovirt-engine-tools.noarch            3.2.1-1.fc18                  @ovirt-stable
ovirt-engine-userportal.noarch       3.2.1-1.fc18                  @ovirt-stable
ovirt-engine-webadmin-portal.noarch  3.2.1-1.fc18                  @ovirt-stable
ovirt-host-deploy.noarch             1.0.1-1.fc18                  @ovirt-stable
ovirt-host-deploy-java.noarch        1.0.1-1.fc18                  @ovirt-stable
ovirt-image-uploader.noarch          3.2.0-1.fc18                  @ovirt-stable
ovirt-iso-uploader.noarch            3.2.0-1.fc18                  @ovirt-stable
ovirt-log-collector.noarch           3.2.0-1.fc18                  @ovirt-stable

So, this is what I doing:
I have already installed and configured ovirt-engine with some hosts installed 
from clear minimal fedora 18 and everything works fine.
Now I would like to add host (node) based on ovirt-node 2.6.1, installation is 
ok, setting network, hostname, ssh, etc seems to be ok (no error shown).
The problem starts with registration to engine. I dont know if the issue is on 
engine or node I hope that log files will be helpful.



-----Original Message-----
From: Fabian Deutsch [mailto:fabi...@redhat.com]
Sent: Thursday, April 11, 2013 5:59 PM
To: Kralicek, Martin
Cc: users@ovirt.org
Subject: Re: [Users] oVirt 3.2.1 and node 2.6.1

Hey Martin,

Am Donnerstag, den 11.04.2013, 15:53 +0000 schrieb

So I try to do again but with same result. I am not able to register node to 

First - Thanks for retrying this :)
Could you explain this a bit more?

Would you like to send server or node log?

yes - It would be nice if you could send the following:
- versions of all components engine + ovirt-node
- on the node side: /var/log/ovirt.log /var/log/vdsm-reg.log (or so)
- on the engine side, engine logs ...




-----Original Message-----
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On
Behalf Of Fabian Deutsch
Sent: 9. dubna 2013 20:18
To: users@ovirt.org
Subject: Re: [Users] oVirt 3.2.1 and node 2.6.1

Am Donnerstag, den 04.04.2013, 17:54 +0200 schrieb Fabian Deutsch:
Am Donnerstag, den 04.04.2013, 12:57 +0000 schrieb
If I remember correctly I have problem only with registered node to ovirt, 
everything seems OK (CA was verified etc.) but in ovirt management does not 
show this node.

Hey Martin,

I've now checked it with AIO 1.0 and could reproduce it - I opened
[1] to track it. I couldn't reproduce it with AIO 0.97 thoguh ..

Hey Martin,

just an update. After a couple of testruns with clean installs of
ovirt-live-1.0 and node-2.6.1 it seems that this isn't a bug.
I could only reproduce this once - and I suppose this was due to me being 


Thanks for bringing this up.

- fabian

[1] https://bugzilla.redhat.com/show_bug.cgi?id=948269

Users mailing list

Users mailing list

This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its 
affiliates, including e-mail and instant messaging (including content), may be 
scanned by our systems for the purposes of information security and assessment 
of internal compliance with Accenture policy.



Users mailing list

Users mailing list

Reply via email to