ted.
> >
> > To update the host to 4.0, you should add 4.0 repos to the host.
> >
> > > On 01/02/17 17:33, users-requ...@ovirt.org wrote:
> > > > Re: ovirt-engine failed to check for updates
> > >
> > > --
>
Thanks. I guess we'll just have to ignore these errors until the host
nodes get upgraded.
On Thu, 2017-02-02 at 17:38 +0100, Martin Perina wrote:
> Hi,
>
> unfortunately you have found a bug [1]. The workaround is to upgrade
> 3.6 host to 4.0, for 4.0+ package lists for "Check for upgrades"
to a later 3.6.z
> version? that's not supported.
>
> To update the host to 4.0, you should add 4.0 repos to the host.
>
> > On 01/02/17 17:33, users-requ...@ovirt.org wrote:
> > > Re: ovirt-engine failed to check for updates
> >
> > --
> >
> &
Hi,
unfortunately you have found a bug [1]. The workaround is to upgrade 3.6
host to 4.0, for 4.0+ package lists for "Check for upgrades" flow are
correct.
Martin Perina
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1418757
On Wed, Feb 1, 2017 at 8:52 PM, Michael Watters
stead of engine version.
>
Do you intend a 4.0 engine to update a 3.6 host to a later 3.6.z version?
that's not supported.
To update the host to 4.0, you should add 4.0 repos to the host.
>
> On 01/02/17 17:33, users-requ...@ovirt.org wrote:
>
> Re: ovirt-engi
Hi,
could you please share what repositories you have configured on the host
nodes?
As already mentioned in the thread ovirt-imageio is included in 4.0, but
not in 3.6
Thanks
Martin Perina
On Wed, Feb 1, 2017 at 8:52 PM, Michael Watters wrote:
> The engine is 4.0, the
Le 01/02/2017 à 18:18, Nicolas Ecarnot a écrit :
Le 01/02/2017 à 17:37, Michael Watters a écrit :
I have ovirt-engine 3.6 set up on a dedicated host which is managing
two ovirt hosts. I am seeing errors when the engine attempts to
check for updates as follows.
Failed to check for available
So, that's the problem, engine is looking for updates for version 4, it
does not matter if your node is version 3.6, i think this is a bug.
Engine should be looking for node version updates instead of engine version.
On 01/02/17 17:33, users-requ...@ovirt.org wrote:
Re: ovirt-engine failed
The engine is 4.0, the host nodes are running 3.6 with VDSM 4.17.35.
On 02/01/2017 02:41 PM, Victor Jose Acosta wrote:
> Hello
>
> ovirt-imageio-daemon is part of ovirt 4 repository, is your engine
> version 4 or 3.6?
___
Users mailing list
om>
To: users@ovirt.org
Subject: Re: [ovirt-users] ovirt-engine failed to check for updates
(NicolasEcarnot)
Message-ID: <205a0dae-7d8a-1239-36b6-490a0e520...@gmail.com>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Hello
ovirt-im
.org
Subject: Re: [ovirt-users] ovirt-engine failed to check for updates
Message-ID: <a2fcc701-96ed-2bdc-dd98-630e814b7...@ecarnot.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Le 01/02/2017 ? 17:37, Michael Watters a ?crit :
I have ovirt-engine 3.6 set up on a dedicated
I don't think IPv6 is the cause. When the engine checks for updates
there is a yum error shown in the debug logs as follows.
2017-02-01 10:38:39 INFO otopi.plugins.ovirt_host_mgmt.packages.update
update.info:98 Yum: Performing yum transaction rollback
2017-02-01 10:38:39 DEBUG otopi.context
Le 01/02/2017 à 17:37, Michael Watters a écrit :
I have ovirt-engine 3.6 set up on a dedicated host which is managing
two ovirt hosts. I am seeing errors when the engine attempts to
check for updates as follows.
Failed to check for available updates on host ovirt-node-production2
with message
I have ovirt-engine 3.6 set up on a dedicated host which is managing two
ovirt hosts. I am seeing errors when the engine attempts to check for
updates as follows.
Failed to check for available updates on host ovirt-node-production2 with
message 'Command returned failure code 1 during SSH
14 matches
Mail list logo