On Fri, 2012-06-15 at 00:45 +0200, Dennis Jacobfeuerborn wrote: > On 06/14/2012 11:48 PM, Mike Burns wrote: > > On Thu, 2012-06-14 at 23:32 +0200, Dennis Jacobfeuerborn wrote: > >> Thanks! With the new iso I can successfully configure the network. > >> When I try to register the node with the engine I get the same problem > >> though. I select "oVirt Engine", enter the IP of the engine system and hit > >> apply and get the same menu problem as with the Network option before. > >> > >> Regards, > >> Dennis > > > > Hi Dennis, > > > > I've had another report of the same issue [1]. It's being investigated > > now. > > > > Mike > > > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=832196 > > I added some information to that bug. Apparently setting the password for > registration from the engine side works because after setting that I was > able to make the node appear in the engine (by adding the node in the > administration portal) but then the initialization fails. > > Regards, > Dennis
Thanks Dennis. It turns out that a bug in sanlock (832230) causes a problem in the build process of the iso where sanlock and vdsm packages don't get installed . I've patched the sanlock bug and sent the patch to the maintainer. In the meantime, I've built a temporary sanlock rpm and built the ISO using that RPM instead. I've confirmed that the ISO has vdsm and sanlock included and boots. It appears that there are additional bugs with registration though. Registering itself to engine fails completely while adding from engine side runs into different problems. The build is being pushed out because it's *better* than it was before and should be useful for debugging what's going on with registration. Mike > _______________________________________________ > node-devel mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/node-devel _______________________________________________ node-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/node-devel
