Description of problem: vdsmd doesn't come up cleanly after registering Node with Engine and rebooting the Node. Version-Release number of selected component (if applicable): vdsm-4.12.1-1 How reproducible: Always Steps to Reproduce: 1. Install Node with vdsm: http://fedorapeople.org/~fabiand/node/ovirt-node-iso-3.0.1-1.0.20130903draft.vdsm.fc19.iso 2. Configure network and register with Engine 3. Set host into maintenance mode 4. Reboot the Node Actual results: vdsmd is in a failed state Expected results: vdsmd starts successfully Additional info: This issue is only present on F19 and not on EL6. Restarting the service manually after rebooting works (so vdsmd will come up normally). Also running <alonbl> vdsm-tool libvirt-configure <alonbl> vdsm-tool sanlock-check-service brings up the service fine, alon's notes: <alonbl> so I guess this is a race between services at startup. ybronhei's notes: <ybronhei> check if ksmtuned is there and run <ybronhei> check if another instance of vdsm runs <ybronhei> check also that sanlock is installe
Created attachment 794142 [details] supervdsm.log
Created attachment 794143 [details] vdsm.log
Created attachment 794144 [details] /var/log/messages
Let me point out that this bug prevents Engine from using Node. A workaround is to manually restart vdsmd. This should be fixed before the release, otherwise we've got an non-working Engine-Node combination.
While there is a workaround available, it's an ugly workaround (login to ovirt-node, drop to a shell, run service vdsmd restart or systemctl restart vdsmd.service). If we can get this fixed in short order, then I'd rather hold the release a couple days. Thanks, Mike
After additional testing, applying a manual workaround for bug 999664 results in vdsmd coming up correctly after reboot. Manual workaround on node: mount -o remount,rw / edit /usr/lib/systemd/systemd-vdsmd to remove ksmtuned from CONFLICTING_SERVICES persist /usr/lib/systemd/systemd-vdsmd *** This bug has been marked as a duplicate of bug 999664 ***