On Monday, 6 February 2012, Mike Burns <<a href="mailto:mburns@redhat.com">mburns@redhat.com</a>> wrote:<br>> On Mon, 2012-02-06 at 14:42 +0000, Andrew Dunlop wrote:<br>>> On 6 February 2012 13:18, Mike Burns <<a href="mailto:mburns@redhat.com">mburns@redhat.com</a>> wrote:<br>
>> > On Mon, 2012-02-06 at 11:12 +0000, Andrew Dunlop wrote:<br>>> >> I realise there is a bug open for a problem where nodes can't register<br>>> >> with engine (<a href="https://bugzilla.redhat.com/show_bug.cgi?id=782663">https://bugzilla.redhat.com/show_bug.cgi?id=782663</a> ).<br>
>> ><br>>> > The fix actually was just pushed a few hours ago.<br>>> Ah ok, will there be a new build of the ISO in the releases folder soon?<br>><br>> This is an engine fix, not a node fix. You need new engine rpms, not a<br>
> new iso.<br>><br>>><br>>> >> However is there any way to easily work around this problem for now.<br>>> >> If I add it from the UI it will try to install the node rather than<br>>> >> just registering a pre installed from iso node. Is there anyway of<br>
>> >> registering it from the management machine without it trying to<br>>> >> install?<br>>> ><br>>> > This actually should work correctly. And if not, then it's a new issue.<br>
>> > The engine UI has logic in it to handle when it detects that the host is<br>>> > ovirt-node. This has worked in previous versions of engine/node, but I<br>>> > haven't tested it recently.<br>
>> I have tried to just register the node from the web interface but I<br>>> get the following in my log file (/var/log/ovirt-engine) and it is put<br>>> into non-responsive state:<br>><br>> This looks like it is a problem with VDSM starting. I *think* it's<br>
> probably related to a bug in iscsi-initiator-utils [1]. I'm watching<br>> this bug and, when fixed, will generate a new iso with the fix.<br>><br>> Mike<br>><br>> [1]<a href="https://bugzilla.redhat.com/show_bug.cgi?id=786174">https://bugzilla.redhat.com/show_bug.cgi?id=786174</a><br>
Looks like that is indeed the problem. Thanks.