[ovirt-users] Cannot add host to cluster - install fails
Yedidyah Bar David
didi at redhat.com
Mon Jul 6 09:24:07 UTC 2015
----- Original Message -----
> From: "Mitja Mihelič" <ftp-admin at arnes.si>
> To: "Yedidyah Bar David" <didi at redhat.com>
> Cc: users at ovirt.org
> Sent: Monday, July 6, 2015 11:49:28 AM
> Subject: Re: [ovirt-users] Cannot add host to cluster - install fails
>
> On 05/07/15 13:40, Yedidyah Bar David wrote:
> > ----- Original Message -----
> >> From: "Mitja Mihelič"<mitja.mihelic at arnes.si>
> >> To:users at ovirt.org
> >> Sent: Friday, July 3, 2015 2:12:28 PM
> >> Subject: [ovirt-users] Cannot add host to cluster - install fails
> >>
> >> Dear all,
> >>
> >> We are running the following setup:
> >> ovirt-engine host:
> >> - CentOS release 6.6
> >> - ovirt-engine-3.5.3.1-1.el6.noarch
> >>
> >> node:
> >> - CentOS Linux release 7.1.1503
> >> - vdsm-4.16.20-0.el7.centos.x86_64
> >>
> >> While adding a new host to our cluster the package installations fail.
> >>
> >> I have attached a piece of engine.log and a full ovirt-host-deploy* log
> >> from the node.
> >>
> >> Why is is happening? Help would be very much appreciated.
> > Perhaps an older ovirt-host-deploy package?
> >
> > You seem to have 1.2.3, while engine 3.5.3 requires at least 1.3.0 -
> > not sure how this happened. Can you try to upgrade?
> >
> > Thanks and best regards,
> This is interesting. The ovirt-host-deploy package version on the engine
> host is ovirt-host-deploy-1.3.1-1.el6.noarch.
> I tried to install ovirt-host-deploy manually using yum on the cluster
> node. It wanted to install ovirt-host-deploy-1.3.1-1.el7, which should
> be OK.
> When adding a node, the install process tries to push an older version
> of the ovirt-host-deploy package and also for the wrong CentOS version
> (el6 instead od el7).
>
> Could this be a problem of the ovirt engine?
The engine caches the bundle (tarfile) used for host-deploy in
/var/cache/ovirt-engine/ovirt-host-deploy.tar .
You can try to remove/rename it so that the engine will re-create it.
It might have a too-new timestamp with older content for some reason.
--
Didi
More information about the Users
mailing list