[Users] Node register bug work around

[Andrew Dunlop]

On 6 February 2012 15:03, Mike Burns <mburns at redhat.com> wrote:
> On Mon, 2012-02-06 at 14:42 +0000, Andrew Dunlop wrote:
>> On 6 February 2012 13:18, Mike Burns <mburns at redhat.com> wrote:
>> > On Mon, 2012-02-06 at 11:12 +0000, Andrew Dunlop wrote:
>> >> I realise there is a bug open for a problem where nodes can't register
>> >> with engine (https://bugzilla.redhat.com/show_bug.cgi?id=782663 ).
>> >
>> > The fix actually was just pushed a few hours ago.
>> Ah ok, will there be a new build of the ISO in the releases folder soon?
>
> This is an engine fix, not a node fix.  You need new engine rpms, not a
> new iso.
Ah yes sorry.

>>
>> >> However is there any way to easily work around this problem for now.
>> >> If I add it from the UI it will try to install the node rather than
>> >> just registering a pre installed from iso node. Is there anyway of
>> >> registering it from the management machine without it trying to
>> >> install?
>> >
>> > This actually should work correctly.  And if not, then it's a new issue.
>> > The engine UI has logic in it to handle when it detects that the host is
>> > ovirt-node.  This has worked in previous versions of engine/node, but I
>> > haven't tested it recently.
>> I have tried to just register the node from the web interface but I
>> get the following in my log file (/var/log/ovirt-engine) and it is put
>> into non-responsive state:
>
> This looks like it is a problem with VDSM starting.  I *think* it's
> probably related to a bug in iscsi-initiator-utils [1].  I'm watching
> this bug and, when fixed, will generate a new iso with the fix.
>
> Mike
>
> [1]https://bugzilla.redhat.com/show_bug.cgi?id=786174
>
Looks like that's what it is.
Thanks