[Users] Hello All I am new to ovirt and have a question

[Doron Fediuck]

On Tuesday 17 January 2012 22:51:39 Mike Burns wrote:
> On Tue, 2012-01-17 at 12:51 -0500, Mike Burns wrote:
> > On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser wrote:
> > > Thanks all,
> > > 
> > > 
> > > I have tried the new ovirt node 2.2.1-3 nightly build today and it
> > > finally recognized my realtek nic card.  So I have moved to try to get
> > > node to install.  Still a fail I might add.  It adds to the ovirt gui
> > > but fails install and says the ovirt hyperviser is not a supported
> > > platform.  That is kind of funny since it is fedora 16.  And yes I had
> > > edited the vdsm.conf by hand was that wrong to do?  Should I have used
> > > vi instead?  I would like to get ovirt node running since it is
> > > working now lighter install.  This is what I get:
> > > 
> > > 
> > > 2012-Jan-17, 12:28:59
> > > Failed to install Host
> > > vm3.bostonvineyard.org.
> > > Step: INSTALLER;
> > > Details: Unsupported
> > > platform:
> > > oVirtNodeHypervisor.
> > > 
> > > 
> > > 
> > > If it registers from ovirt node should it not show up in the ovirt
> > > Management gui?  Or do you still have to add it as usual?  So that is
> > > what I did and that is the error I recieved.  
> > 
> > oVirt Node supports 2 ways of registering.
> > 
> > 1.  Set the hostname and port of the management server
> > 	The Node registers itself to the engine and the admin then only has to
> > approve it.
> 
> This appears to not be working at the moment.  There are 404 errors in
> the log.  I'll file a bug for the vdsm team to look into this.
> 
> > 
> > 2.  Set a password and use add host from the engine
> > 	The node does no registration.  The admin for engine manually adds the
> > node as they would a regular Fedora node.  
> 
> This is not working out of the box.  I get the same error you do about
> it being an unsupported platform.  I filed a bug [1] for this issue with
> a patch as well[2].  This patch can be applied directly on the engine
> system to get around the problem.  oVirtNodeHypervisor is simply missing
> from the list of supported systems.
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=782660
> [2] http://gerrit.ovirt.org/#change,1117
> 
> Mike

Patch was merged.
Mike, thanks and you can close the bz.
Dominic, you should fetch & rebase to latest code to get Mike's fix.

> > 
> > 
> > As for the actual error, I've seen other problems with that build of
> > ovirt-node that I'm working on so I haven't tried to register it yet.
> > I'll try it though.
> > 
> > Mike
> > 
> > > 
> > > 
> > > Let me know what you think,
> > > 
> > > 
> > > Dominic
> > > 
> > > On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck at redhat.com>
> > > wrote:
> > >         On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote:
> > >         > Ok here are the log files. It installs most packages and
> > >         then hangs up on
> > >         > libjpeg?  libjpeg is installed including dev package.  This
> > >         is a bare-metal
> > >         > node running fedora 16 with vdsm packages installed from
> > >         repo.  Your node
> > >         > .iso 2.2.1 does not initialize realtek nic cards so I can
> > >         not use that.
> > >         > The 2.2.1 .iso sees the nic card but that is it.  So I went
> > >         the route of
> > >         > installing the full fedora 16 distro and installing vdsm
> > >         packages from
> > >         > repo.  I am bridged correctly and ssl=false in the
> > >         vdsm.conf.  Now when I
> > >         > go to the ovirt management gui and install the node it fails
> > >         at this step.
> > >         > I can see the node in ovirt management gui just an fyi so
> > >         not a problem
> > >         > with detection.  It seems that the vdsm server will not
> > >         start due to
> > >         > libjpeg install failure but mabey I am wrong.
> > >         >
> > >         > Let me know what you think,
> > >         >
> > >         > Dominic
> > >         >
> > >         
> > >         Hi Dominic,
> > >         This is where your installation fails:
> > >         ParsingError: File contains parsing
> > >         errors: /etc/vdsm/vdsm.conf
> > >                [line 42]: ' default_bridge = engine\n'
> > >                [line 93]: ' ssl = false\n'
> > >                [line 191]: ' management_port = 54321\n'
> > >                [line 193]: ' management_ip = 10.3.0.245\n'
> > >         Sun, 15 Jan 2012 08:01:27 DEBUG    <BSTRAP
> > >         component='CreateConf' status='FAIL' message='Basic
> > >         configuration failed'/>
> > >         
> > >         Now I'm wondering how did you edit /etc/vdsm/vdsm.conf?
> > >         Did you really add a string '\n' or is it just the way the
> > >         error propmts?
> > >         
> > >         --
> > >         
> > >         /d
> > >         
> > >         "Air conditioned environment - Do NOT open Windows!"
> > >         
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
-- 

/d

Why doesn't DOS ever say "EXCELLENT command or filename!"