[Engine-devel] Unknown operation 'force-start' when starting VDSM
Douglas Schilling Landgraf
dougsland at redhat.com
Fri Jul 19 02:25:08 UTC 2013
Hello Greg,
On 07/18/2013 04:38 PM, Greg Sheremeta wrote:
> Engine is installed and working on a fresh laptop install of Fedora 19. Rebased ovirt-engine from gerrit/master this morning. Trying to install host on a fresh Fedora 19 VM -- I'm trying to get a nested host setup.
>
> Host installation fails with:
>
> Jul 18 16:24:52 ovirt-host-fedora-2 systemd[1]: Starting Virtual Desktop Server Manager...
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Note: Forwarding request to 'systemctl disable libvirt-guests.service'.
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: vdsm: libvirt already configured for vdsm [ OK ]
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Starting multipathd...
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Redirecting to /bin/systemctl start multipathd.service
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Redirecting to /bin/systemctl force-start iscsid.service
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Unknown operation 'force-start'.
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: vdsmd.service: control process exited, code=exited status=1
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: Failed to start Virtual Desktop Server Manager.
> Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: Unit vdsmd.service entered failed state.
>
> I've never heard of force-start before, and googling for "fedora force-start" brings up this as the second result:
> https://ask.fedoraproject.org/question/27737/vdsmdservice-fails-bc-iscsid-is-started-using-force-start/
>
> So someone else out there is having this problem too :)
>
vdsm-4.10.3-18 should fix it.
Please check:
http://permalink.gmane.org/gmane.comp.emulators.ovirt.user/9488
--
Cheers
Douglas
More information about the Engine-devel
mailing list