On 2013/8/18 16:52, Alon Bar-Lev wrote:
----- Original Message -----
> From: "lof yer" <lofyer(a)gmail.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: "Yedidyah Bar David" <didi(a)redhat.com>, "users"
<users(a)ovirt.org>
> Sent: Sunday, August 18, 2013 11:17:03 AM
> Subject: Re: [Users] engine-setup's forcing update
>
> thanks, I think it would be better if it was not aborted at this point then.
There is a conflict... which is not easy to resolve as the upgrade sequence is not
closed.
1. ovirt-engine* are versionlocked.
2. exception is ovirt-engine-setup
3. newer ovirt-engine-setup cannot install older ovirt-engine.
So if a user performs:
# yum update
Then you get newer ovirt-engine-setup with a versionlocked blocked update of the rest of
ovirt-engine.
And user may face issues.
So for now, the default behavior is to stop the setup if an update is available, it is
the safest option.
Regards,
Alon
>
> 2013/8/18 Alon Bar-Lev <alonbl(a)redhat.com>
>
>>
>> ----- Original Message -----
>>> From: "Yedidyah Bar David" <didi(a)redhat.com>
>>> To: "lof yer" <lofyer(a)gmail.com>
>>> Cc: "users" <users(a)ovirt.org>
>>> Sent: Sunday, August 18, 2013 10:53:17 AM
>>> Subject: Re: [Users] engine-setup's forcing update
>>>
>>>
>>>
>>> From: "lof yer" <lofyer(a)gmail.com>
>>> To: "users" <users(a)ovirt.org>
>>> Sent: Sunday, August 18, 2013 10:46:46 AM
>>> Subject: [Users] engine-setup's forcing update
>>>
>>> If it detected some updates online, it will force me to choose
'Yes'.
>>> If I choose 'No', I'll be 'quitted'
>>> Must I update?
>>>
>>> Yes.
>>> A simple workaround: Change the relevant yum repo(s) to 'enabled=0'.
>>> --
>>> Didi
>> You can use the --offline parameter for engine-setup.
>>
>> Alon
>>
Got that, thank you very much.