[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?

------=_Part_192088_1222363890.1376812397573 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit
From: "lof yer" <lofyer@gmail.com> To: "users" <users@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 ------=_Part_192088_1222363890.1376812397573 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: times new roman, new york, times, se= rif; font-size: 12pt; color: #000000"><div></div><blockquote style=3D"borde= r-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-w= eight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,A= rial,sans-serif;font-size:12pt;"><b>From: </b>"lof yer" <lofyer@gmail.co= m><br><b>To: </b>"users" <users@ovirt.org><br><b>Sent: </b>Sunday,= August 18, 2013 10:46:46 AM<br><b>Subject: </b>[Users] engine-setup's forc= ing update<br><div><br></div><div dir=3D"ltr"><div><div>If it detected some= updates online, it will force me to choose 'Yes'.<br></div>If I choose 'No= ', I'll be 'quitted'<br></div>Must I update?</div></blockquote><div><br></d= iv><div>Yes.</div><div>A simple workaround: Change the relevant yum repo(s)= to 'enabled=3D0'.</div><div><span style=3D"font-size: 12pt;">-- </spa= n></div><div><span name=3D"x"></span>Didi<span name=3D"x"></span><br></div>= <div><br></div></div></body></html> ------=_Part_192088_1222363890.1376812397573--

----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "lof yer" <lofyer@gmail.com> Cc: "users" <users@ovirt.org> Sent: Sunday, August 18, 2013 10:53:17 AM Subject: Re: [Users] engine-setup's forcing update
From: "lof yer" <lofyer@gmail.com> To: "users" <users@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

thanks, I think it would be better if it was not aborted at this point then. 2013/8/18 Alon Bar-Lev <alonbl@redhat.com>
----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "lof yer" <lofyer@gmail.com> Cc: "users" <users@ovirt.org> Sent: Sunday, August 18, 2013 10:53:17 AM Subject: Re: [Users] engine-setup's forcing update
From: "lof yer" <lofyer@gmail.com> To: "users" <users@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

----- Original Message -----
From: "lof yer" <lofyer@gmail.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Yedidyah Bar David" <didi@redhat.com>, "users" <users@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@redhat.com>
----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "lof yer" <lofyer@gmail.com> Cc: "users" <users@ovirt.org> Sent: Sunday, August 18, 2013 10:53:17 AM Subject: Re: [Users] engine-setup's forcing update
From: "lof yer" <lofyer@gmail.com> To: "users" <users@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

On 2013/8/18 16:52, Alon Bar-Lev wrote:
----- Original Message -----
From: "lof yer" <lofyer@gmail.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Yedidyah Bar David" <didi@redhat.com>, "users" <users@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@redhat.com>
----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "lof yer" <lofyer@gmail.com> Cc: "users" <users@ovirt.org> Sent: Sunday, August 18, 2013 10:53:17 AM Subject: Re: [Users] engine-setup's forcing update
From: "lof yer" <lofyer@gmail.com> To: "users" <users@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.
participants (4)
-
Alon Bar-Lev
-
lof yer
-
lofyer
-
Yedidyah Bar David