From: "lof yer" <lofyer(a)gmail.= co=3D m>
To: "users" <users(a)ovirt.org>
Sent: Sunda= y,=3D August 18, 2013 10:46:46 AM
Subject: [Users] engine-setup's forc= =3D ing update

If it detected so= me=3D updates online, it will force me to choose 'Yes'.
If I choose 'No= =3D ', I'll be 'quitted'
Must I update?

Yes.

A simple workaround: Change the relevant yum repo(s)= =3D to 'enabled=3D3D0'.

-- <= /spa=3D n>

Didi
=3D

------=3D_Part_192088_1222363890.1376812397573-- --===============7875197186159300259== Content-Type: multipart/alternative MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.bin" LS0tLS0tPV9QYXJ0XzE5MjA4OF8xMjIyMzYzODkwLjEzNzY4MTIzOTc1NzMKQ29udGVudC1UeXBl OiB0ZXh0L3BsYWluOyBjaGFyc2V0PXV0Zi04CkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6IDdi aXQKCj4gRnJvbTogImxvZiB5ZXIiIDxsb2Z5ZXJAZ21haWwuY29tPgo+IFRvOiAidXNlcnMiIDx1 c2Vyc0BvdmlydC5vcmc+Cj4gU2VudDogU3VuZGF5LCBBdWd1c3QgMTgsIDIwMTMgMTA6NDY6NDYg QU0KPiBTdWJqZWN0OiBbVXNlcnNdIGVuZ2luZS1zZXR1cCdzIGZvcmNpbmcgdXBkYXRlCgo+IElm IGl0IGRldGVjdGVkIHNvbWUgdXBkYXRlcyBvbmxpbmUsIGl0IHdpbGwgZm9yY2UgbWUgdG8gY2hv b3NlICdZZXMnLgo+IElmIEkgY2hvb3NlICdObycsIEknbGwgYmUgJ3F1aXR0ZWQnCj4gTXVzdCBJ IHVwZGF0ZT8KClllcy4gCkEgc2ltcGxlIHdvcmthcm91bmQ6IENoYW5nZSB0aGUgcmVsZXZhbnQg eXVtIHJlcG8ocykgdG8gJ2VuYWJsZWQ9MCcuIAotLSAKRGlkaSAKCi0tLS0tLT1fUGFydF8xOTIw ODhfMTIyMjM2Mzg5MC4xMzc2ODEyMzk3NTczCkNvbnRlbnQtVHlwZTogdGV4dC9odG1sOyBjaGFy c2V0PXV0Zi04CkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6IHF1b3RlZC1wcmludGFibGUKCjxo dG1sPjxib2R5PjxkaXYgc3R5bGU9M0QiZm9udC1mYW1pbHk6IHRpbWVzIG5ldyByb21hbiwgbmV3 IHlvcmssIHRpbWVzLCBzZT0KcmlmOyBmb250LXNpemU6IDEycHQ7IGNvbG9yOiAjMDAwMDAwIj48 ZGl2PjwvZGl2PjxibG9ja3F1b3RlIHN0eWxlPTNEImJvcmRlPQpyLWxlZnQ6MnB4IHNvbGlkICMx MDEwRkY7bWFyZ2luLWxlZnQ6NXB4O3BhZGRpbmctbGVmdDo1cHg7Y29sb3I6IzAwMDtmb250LXc9 CmVpZ2h0Om5vcm1hbDtmb250LXN0eWxlOm5vcm1hbDt0ZXh0LWRlY29yYXRpb246bm9uZTtmb250 LWZhbWlseTpIZWx2ZXRpY2EsQT0KcmlhbCxzYW5zLXNlcmlmO2ZvbnQtc2l6ZToxMnB0OyI+PGI+ RnJvbTogPC9iPiJsb2YgeWVyIiAmbHQ7bG9meWVyQGdtYWlsLmNvPQptJmd0Ozxicj48Yj5Ubzog PC9iPiJ1c2VycyIgJmx0O3VzZXJzQG92aXJ0Lm9yZyZndDs8YnI+PGI+U2VudDogPC9iPlN1bmRh eSw9CiBBdWd1c3QgMTgsIDIwMTMgMTA6NDY6NDYgQU08YnI+PGI+U3ViamVjdDogPC9iPltVc2Vy c10gZW5naW5lLXNldHVwJ3MgZm9yYz0KaW5nIHVwZGF0ZTxicj48ZGl2Pjxicj48L2Rpdj48ZGl2 IGRpcj0zRCJsdHIiPjxkaXY+PGRpdj5JZiBpdCBkZXRlY3RlZCBzb21lPQogdXBkYXRlcyBvbmxp bmUsIGl0IHdpbGwgZm9yY2UgbWUgdG8gY2hvb3NlICdZZXMnLjxicj48L2Rpdj5JZiBJIGNob29z ZSAnTm89CicsIEknbGwgYmUgJ3F1aXR0ZWQnPGJyPjwvZGl2Pk11c3QgSSB1cGRhdGU/PC9kaXY+ PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwvZD0KaXY+PGRpdj5ZZXMuPC9kaXY+PGRpdj5BIHNpbXBs ZSB3b3JrYXJvdW5kOiBDaGFuZ2UgdGhlIHJlbGV2YW50IHl1bSByZXBvKHMpPQogdG8gJ2VuYWJs ZWQ9M0QwJy48L2Rpdj48ZGl2PjxzcGFuIHN0eWxlPTNEImZvbnQtc2l6ZTogMTJwdDsiPi0tJm5i c3A7PC9zcGE9Cm4+PC9kaXY+PGRpdj48c3BhbiBuYW1lPTNEIngiPjwvc3Bhbj5EaWRpPHNwYW4g bmFtZT0zRCJ4Ij48L3NwYW4+PGJyPjwvZGl2Pj0KPGRpdj48YnI+PC9kaXY+PC9kaXY+PC9ib2R5 PjwvaHRtbD4KLS0tLS0tPV9QYXJ0XzE5MjA4OF8xMjIyMzYzODkwLjEzNzY4MTIzOTc1NzMtLQo= --===============7875197186159300259==-- From alonbl at redhat.com Sun Aug 18 03:54:45 2013 Content-Type: multipart/mixed; boundary="===============3501547526156127261==" MIME-Version: 1.0 From: Alon Bar-Lev To: users at ovirt.org Subject: Re: [Users] engine-setup's forcing update Date: Sun, 18 Aug 2013 03:54:44 -0400 Message-ID: <1634008206.32043.1376812484062.JavaMail.root@redhat.com> In-Reply-To: 1441332028.192089.1376812397574.JavaMail.root@redhat.com --===============3501547526156127261== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Yedidyah Bar David" > To: "lof yer" > Cc: "users" > Sent: Sunday, August 18, 2013 10:53:17 AM > Subject: Re: [Users] engine-setup's forcing update > = > = > = > From: "lof yer" > To: "users" > 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=3D0'. > -- > Didi You can use the --offline parameter for engine-setup. Alon --===============3501547526156127261==-- From lofyer at gmail.com Sun Aug 18 04:17:05 2013 Content-Type: multipart/mixed; boundary="===============4721654880914834327==" MIME-Version: 1.0 From: lof yer To: users at ovirt.org Subject: Re: [Users] engine-setup's forcing update Date: Sun, 18 Aug 2013 16:17:03 +0800 Message-ID: In-Reply-To: 1634008206.32043.1376812484062.JavaMail.root@redhat.com --===============4721654880914834327== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable thanks, I think it would be better if it was not aborted at this point then. 2013/8/18 Alon Bar-Lev > > > ----- Original Message ----- > > From: "Yedidyah Bar David" > > To: "lof yer" > > Cc: "users" > > Sent: Sunday, August 18, 2013 10:53:17 AM > > Subject: Re: [Users] engine-setup's forcing update > > > > > > > > From: "lof yer" > > To: "users" > > 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=3D0'. > > -- > > Didi > > You can use the --offline parameter for engine-setup. > > Alon > --===============4721654880914834327== Content-Type: text/html MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.html" PGRpdiBkaXI9Imx0ciI+dGhhbmtzLCBJIHRoaW5rIGl0IHdvdWxkIGJlIGJldHRlciBpZiBpdCB3 YXMgbm90IGFib3J0ZWQgYXQgdGhpcyBwb2ludCB0aGVuLjxicj48L2Rpdj48ZGl2IGNsYXNzPSJn bWFpbF9leHRyYSI+PGJyPjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+MjAxMy84LzE4IEFs b24gQmFyLUxldiA8c3BhbiBkaXI9Imx0ciI+Jmx0OzxhIGhyZWY9Im1haWx0bzphbG9uYmxAcmVk aGF0LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFsb25ibEByZWRoYXQuY29tPC9hPiZndDs8L3NwYW4+ PGJyPgo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAg LjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij48ZGl2IGNs YXNzPSJIT0VuWmIiPjxkaXYgY2xhc3M9Img1Ij48YnI+Cjxicj4KLS0tLS0gT3JpZ2luYWwgTWVz c2FnZSAtLS0tLTxicj4KJmd0OyBGcm9tOiAmcXVvdDtZZWRpZHlhaCBCYXIgRGF2aWQmcXVvdDsg Jmx0OzxhIGhyZWY9Im1haWx0bzpkaWRpQHJlZGhhdC5jb20iPmRpZGlAcmVkaGF0LmNvbTwvYT4m Z3Q7PGJyPgomZ3Q7IFRvOiAmcXVvdDtsb2YgeWVyJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86 bG9meWVyQGdtYWlsLmNvbSI+bG9meWVyQGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPgomZ3Q7IENjOiAm cXVvdDt1c2VycyZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnVzZXJzQG92aXJ0Lm9yZyI+dXNl cnNAb3ZpcnQub3JnPC9hPiZndDs8YnI+CiZndDsgU2VudDogU3VuZGF5LCBBdWd1c3QgMTgsIDIw MTMgMTA6NTM6MTcgQU08YnI+CiZndDsgU3ViamVjdDogUmU6IFtVc2Vyc10gZW5naW5lLXNldHVw JiMzOTtzIGZvcmNpbmcgdXBkYXRlPGJyPgomZ3Q7PGJyPgomZ3Q7PGJyPgomZ3Q7PGJyPgomZ3Q7 IEZyb206ICZxdW90O2xvZiB5ZXImcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpsb2Z5ZXJAZ21h aWwuY29tIj5sb2Z5ZXJAZ21haWwuY29tPC9hPiZndDs8YnI+CiZndDsgVG86ICZxdW90O3VzZXJz JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86dXNlcnNAb3ZpcnQub3JnIj51c2Vyc0BvdmlydC5v cmc8L2E+Jmd0Ozxicj4KJmd0OyBTZW50OiBTdW5kYXksIEF1Z3VzdCAxOCwgMjAxMyAxMDo0Njo0 NiBBTTxicj4KJmd0OyBTdWJqZWN0OiBbVXNlcnNdIGVuZ2luZS1zZXR1cCYjMzk7cyBmb3JjaW5n IHVwZGF0ZTxicj4KJmd0Ozxicj4KJmd0OyBJZiBpdCBkZXRlY3RlZCBzb21lIHVwZGF0ZXMgb25s aW5lLCBpdCB3aWxsIGZvcmNlIG1lIHRvIGNob29zZSAmIzM5O1llcyYjMzk7Ljxicj4KJmd0OyBJ ZiBJIGNob29zZSAmIzM5O05vJiMzOTssIEkmIzM5O2xsIGJlICYjMzk7cXVpdHRlZCYjMzk7PGJy PgomZ3Q7IE11c3QgSSB1cGRhdGU/PGJyPgomZ3Q7PGJyPgomZ3Q7IFllcy48YnI+CiZndDsgQSBz aW1wbGUgd29ya2Fyb3VuZDogQ2hhbmdlIHRoZSByZWxldmFudCB5dW0gcmVwbyhzKSB0byAmIzM5 O2VuYWJsZWQ9MCYjMzk7Ljxicj4KJmd0OyAtLTxicj4KJmd0OyBEaWRpPGJyPgo8YnI+CjwvZGl2 PjwvZGl2PllvdSBjYW4gdXNlIHRoZSAtLW9mZmxpbmUgcGFyYW1ldGVyIGZvciBlbmdpbmUtc2V0 dXAuPGJyPgo8c3BhbiBjbGFzcz0iSE9FblpiIj48Zm9udCBjb2xvcj0iIzg4ODg4OCI+PGJyPgpB bG9uPGJyPgo8L2ZvbnQ+PC9zcGFuPjwvYmxvY2txdW90ZT48L2Rpdj48YnI+PC9kaXY+Cg== --===============4721654880914834327==-- From alonbl at redhat.com Sun Aug 18 04:52:07 2013 Content-Type: multipart/mixed; boundary="===============4889375454101160913==" MIME-Version: 1.0 From: Alon Bar-Lev To: users at ovirt.org Subject: Re: [Users] engine-setup's forcing update Date: Sun, 18 Aug 2013 04:52:06 -0400 Message-ID: <1399426131.33296.1376815926117.JavaMail.root@redhat.com> In-Reply-To: CAKUHWYq3TFS8-ongeZKaAmQo3MMB-SB1o8U2LAyOfW25LPo5Ew@mail.gmail.com --===============4889375454101160913== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "lof yer" > To: "Alon Bar-Lev" > Cc: "Yedidyah Bar David" , "users" > 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 th= en. 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 o= f 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 avail= able, it is the safest option. Regards, Alon > = > = > 2013/8/18 Alon Bar-Lev > = > > > > > > ----- Original Message ----- > > > From: "Yedidyah Bar David" > > > To: "lof yer" > > > Cc: "users" > > > Sent: Sunday, August 18, 2013 10:53:17 AM > > > Subject: Re: [Users] engine-setup's forcing update > > > > > > > > > > > > From: "lof yer" > > > To: "users" > > > 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=3D0'. > > > -- > > > Didi > > > > You can use the --offline parameter for engine-setup. > > > > Alon > > >=20 --===============4889375454101160913==-- From lofyer at gmail.com Sun Aug 18 07:46:18 2013 Content-Type: multipart/mixed; boundary="===============0929029397496243487==" MIME-Version: 1.0 From: lofyer To: users at ovirt.org Subject: Re: [Users] engine-setup's forcing update Date: Sun, 18 Aug 2013 19:46:09 +0800 Message-ID: <5210B401.8030809@gmail.com> In-Reply-To: 1399426131.33296.1376815926117.JavaMail.root@redhat.com --===============0929029397496243487== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 2013/8/18 16:52, Alon Bar-Lev wrote: > > ----- Original Message ----- >> From: "lof yer" >> To: "Alon Bar-Lev" >> Cc: "Yedidyah Bar David" , "users" >> 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 t= hen. > There is a conflict... which is not easy to resolve as the upgrade sequen= ce 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 ava= ilable, it is the safest option. > > Regards, > Alon > >> >> 2013/8/18 Alon Bar-Lev >> >>> >>> ----- Original Message ----- >>>> From: "Yedidyah Bar David" >>>> To: "lof yer" >>>> Cc: "users" >>>> Sent: Sunday, August 18, 2013 10:53:17 AM >>>> Subject: Re: [Users] engine-setup's forcing update >>>> >>>> >>>> >>>> From: "lof yer" >>>> To: "users" >>>> 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=3D0'. >>>> -- >>>> Didi >>> You can use the --offline parameter for engine-setup. >>> >>> Alon >>> Got that, thank you very much. --===============0929029397496243487==--