Red Hat Bugzilla – Bug 832196
vdsm missing from ovirt node iso
Last modified: 2016-04-26 19:42:32 EDT
Created attachment 591919 [details]
Missing Directory Error
Description of problem:
[Error 2] No such file or directory" '/etc/pki/vdsm/certs/cacert.pem'
Version-Release number of selected component (if applicable):
Second try gave me a white screen and had to hit power the power button to anything.
Repeatable after reboot.
Steps to Reproduce:
1. Select oVirt Enginue
2. Enter Enginue info.
3. Apply changes.
Getting errors and the system stops repling. Never regesters with the engine.
Regesters to the engine
Douglas, Looks like an issue with vdsm rather than ovirt-node, but feel free to assign back if you disagree.
I'm seeing this too. When I just enter the IP of the node I don't get an error and only the mentioned GUI issues. Hitting f12 "resets" the infterface though and it becomes usable again.
I got the certificate issues initially but not after I tried registering the node from the engine side. Apparently setting the optional password for this on the node works and the node appears under Hosts in the engine gui but the initialization fails with "Host installation failed. Fix installation issues and try to Re-Install".
I have reproduced the report (Thanks Robert). VDSM package is not automatically installed in the node as we talked over IRC. In that case, /etc/pki/vdsm/ won't be created and will affect TUI.
#rpm -qa | grep -i vdsm
Generated a rpm in the vdsm git tree:
# rpm -ivh vdsm-reg-4.10.0-0.32.git61ecfc0.el6.noarch.rpm
error: Failed dependencies:
vdsm = 4.10.0-0.32.git61ecfc0.el6 is needed by vdsm-reg-4.10.0-0.32.git61ecfc0.el6.noarch
Moving back to ovirt-node.
Blocked by bug 832230.
In the meantime, I've built a temporary sanlock package that I will upload to ovirt.org repos and regenerate the ISO image with those packages to ensure that vdsm is included
I just tested this again with this image:
The initial registration from the node side now works though in the engine it then show "install failed".
Is there a way to get shell access to the node or a way to get access to the log files directly? There are tracebacks in the vdsm-reg.log but I don't want to re-type them all by hand out of the gui.
logs should be viewable on the log viewer screen by pressing the F8 key (iirc)
You can drop to a shell by pressing the F2 key.
As for the actual issue of registration, i'll be filing a separate bug for that shortly.
Moving back to modified. This will be fixed when a new build is available (should be in next couple days).