[ovirt-users] Host installation failed. Command returned failure code 1 during ssh session

[Alon Bar-Lev]

In the event log when you click the host in ui you should see alerts tab, in this you will get status of installation.
Not trivial to look within that tab, but one you know this tab lots of information is visible.
In this tab you will also see a message where the host-deploy log is stored at engine machine it should be at /var/log/ovirt-engine/host-deploy.
Please attach this file or examine the events and understand what is the problem.

----- Original Message -----
> From: "Ryan Nix" <ryan.nix at gmail.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: users at ovirt.org
> Sent: Monday, October 13, 2014 6:14:58 PM
> Subject: Re: [ovirt-users] Host installation failed. Command returned failure code 1 during ssh session
> 
> The log file for the deploy process disappears quickly from /tmp/ovirt,
> however, this is what I was able to capture:
> 
> 2014-10-13 10:07:49 DEBUG otopi.context context._executeMethod:138 Stage
> internal_packages METHOD
> otopi.plugins.otopi.core.transaction.Plugin._pre_prepare
> 
> 2014-10-13 10:07:49 DEBUG otopi.transaction transaction._prepare:77
> preparing 'Yum Transaction'
> 
> Loaded plugins: fastestmirror
> 
> 2014-10-13 10:07:49 DEBUG otopi.context context._executeMethod:138 Stage
> internal_packages METHOD
> otopi.plugins.otopi.network.hostname.Plugin._internal_packages
> 
> 2014-10-13 10:07:49 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum queue package iproute for install
> 
> Loading mirror speeds from cached hostfile
> 
> 2014-10-13 10:07:49 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: epel/metalink (0%)
> 
> 2014-10-13 10:07:49 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: epel/metalink 16 k(100%)
> 
>  * base: mirror.steadfast.net
> 
>  * epel: mirror.steadfast.net
> 
>  * extras: mirror.cisp.com
> 
>  * updates: centosq4.centos.org
> 
> 2014-10-13 10:07:51 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: repomdZB5dnstmp.xml (0%)
> 
> 2014-10-13 10:07:51 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: repomdZB5dnstmp.xml 3.7 k(100%)
> 
> 2014-10-13 10:07:51 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: repomdWiBr5Stmp.xml (0%)
> 
> 2014-10-13 10:07:51 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: repomdWiBr5Stmp.xml 3.3 k(100%)
> 
> 2014-10-13 10:07:52 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: repomdFNAh24tmp.xml (0%)
> 
> 2014-10-13 10:07:52 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: repomdFNAh24tmp.xml 2.9 k(100%)
> 
> 2014-10-13 10:07:52 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: repomda3kAIJtmp.xml (0%)
> 
> 2014-10-13 10:07:52 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:88 Yum Downloading: repomda3kAIJtmp.xml 2.9 k(100%)
> 
> 
> 
> On Mon, Oct 13, 2014 at 9:54 AM, Alon Bar-Lev <alonbl at redhat.com> wrote:
> 
> >
> >
> > ----- Original Message -----
> > > From: "Ryan Nix" <ryan.nix at gmail.com>
> > > To: users at ovirt.org
> > > Sent: Monday, October 13, 2014 5:32:42 PM
> > > Subject: [ovirt-users] Host installation failed. Command returned
> > failure     code 1 during ssh session
> > >
> > > Hi,
> > >
> > > I'm trying to use oVirt 3.4 to manage a simple Gluster 3.5.2 node setup.
> > > However, I can't seem to add either node (there are only two). I keep
> > > getting the following in the log:
> > > Host installation failed. Command returned failure code 1 during ssh
> > session
> > > Redhat lists the answer on their customer portal page, however, I can't
> > see
> > > the answer unless I purchase RHEL. Is anyone familiar with this error?
> > > https://access.redhat.com/solutions/514633
> > >
> >
> > you should scroll up the event log and see what error you get during the
> > host-deploy process.
> >
>