[Users] VDSM failing to start because iscsid fails to start

[Dave Allan]

On Wed, Feb 01, 2012 at 09:59:05AM +0200, Moran Goldboim wrote:
> On 02/01/2012 07:23 AM, Dave Allan wrote:
> >I just installed the engine and a few nodes from RPMs all on F16 per
> >the instructions at:
> >
> >http://www.ovirt.org/wiki/Installing_ovirt-engine_from_rpm
> >
> >After installing the engine, I installed a few nodes by installing the
> >minimal F16 package set + wget, configuring the ovirt repo on the
> >nodes and using the 'New' button in the hosts tab of the engine GUI.
> >The installation went fine, but after the nodes rebooted they were
> >listed as non-reponsive.  It turned out that VDSM was failing to start
> >because iscsid was failing to start.  I turned up the debug level on
> >iscsid but didn't find any culprit.  Manually force-starting iscsid
> >and then manually starting the vdsm service caused the nodes to change
> >status to Up.  Anybody seen this or have any thoughts about what might
> >be wrong?
> >
> >Dave
> >_______________________________________________
> >Users mailing list
> >Users at ovirt.org
> >http://lists.ovirt.org/mailman/listinfo/users
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=786174

Ah, that explains it.  Thanks.  I've volunteered to test and give
karma when a fix hits updates-testing.

Dave

> Moran.