From fsayd at uncu.edu.ar Wed Jul 20 19:48:51 2016 Content-Type: multipart/mixed; boundary="===============6252472458622702499==" MIME-Version: 1.0 From: Federico Sayd To: users at ovirt.org Subject: [ovirt-users] Upgrade 3.6 to 4.0 and "ghost" incompatible cluster version Date: Wed, 20 Jul 2016 20:41:09 -0300 Message-ID: <7eab-57900c00-7b9-278f27c0@161679876> --===============6252472458622702499== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ------=3D_=3D-_OpenGroupware_org_NGMime-32427-1469058069.132924-816------ content-type: text/plain; charset=3Dutf-8 content-length: 794 content-transfer-encoding: quoted-printable Hello: I'm trying to upgrade ovirt 3.6.3 to 4.0, but engine-setup complaints a=3D bout upgrading from incompatible version 3.3 I see in the engine-setup log that=3DC2=3DA0 vds=3D5Fgroups table is checke= d =3D to determine the compatibility version. The logs shows that engine-setu=3D p detects 2 clusters versions: 3.3 and 3.6. Indeed, there is 2 clusters=3D registered in the table: "cluster-3.6" and "Default" "Cluster-3.6" (version 3.6)=3DC2=3DA0 is the only cluster in DC in my ovirt= =3D setup. "Default" (version 3.3)=3DC2=3DA0 should be a cluster that surely I deleted= =3D in a past upgrade. Why a cluster named "Default" (with compatibility version 3.3) is still=3D present in vds=3D5Fgroup table? Cluster "Default" isn't displayed anywhe= =3D re in the web interface. Any clue to solve this issue? Thanks ------=3D_=3D-_OpenGroupware_org_NGMime-32427-1469058069.132924-816------ content-type: text/html; charset=3Dutf-8 content-length: 951 content-transfer-encoding: quoted-printable Hello:

I'm trying to upgrade ovirt 3.6.3 to 4.0, b=3D ut engine-setup complaints about upgrading from incompatible version 3.=3D 3

I see in the engine-setup log that  vds=3D5Fgroups tabl= =3D e is checked to determine the compatibility version. The logs shows tha=3D t engine-setup detects 2 clusters versions: 3.3 and 3.6. Indeed, there =3D is 2 clusters registered in the table: "cluster-3.6" and &quo=3D t;Default"

"Cluster-3.6" (version 3.6)  =3D is the only cluster in DC in my ovirt setup.
"Default" (=3D version 3.3)  should be a cluster that surely I deleted in a past =3D upgrade.

Why a cluster named "Default" (with compa=3D tibility version 3.3) is still present in vds=3D5Fgroup table? Cluster &q= =3D uot;Default" isn't displayed anywhere in the web interface.
Any clue to solve this issue?

Thanks ------=3D_=3D-_OpenGroupware_org_NGMime-32427-1469058069.132924-816-------- --===============6252472458622702499== Content-Type: multipart/alternative MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.bin" LS0tLS0tPV89LV9PcGVuR3JvdXB3YXJlX29yZ19OR01pbWUtMzI0MjctMTQ2OTA1ODA2OS4xMzI5 MjQtODE2LS0tLS0tCmNvbnRlbnQtdHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD11dGYtOApjb250 ZW50LWxlbmd0aDogNzk0CmNvbnRlbnQtdHJhbnNmZXItZW5jb2Rpbmc6IHF1b3RlZC1wcmludGFi bGUKCgpIZWxsbzoKCkknbSB0cnlpbmcgdG8gdXBncmFkZSBvdmlydCAzLjYuMyB0byA0LjAsIGJ1 dCBlbmdpbmUtc2V0dXAgY29tcGxhaW50cyBhPQpib3V0IHVwZ3JhZGluZyBmcm9tIGluY29tcGF0 aWJsZSB2ZXJzaW9uIDMuMwoKSSBzZWUgaW4gdGhlIGVuZ2luZS1zZXR1cCBsb2cgdGhhdD1DMj1B MCB2ZHM9NUZncm91cHMgdGFibGUgaXMgY2hlY2tlZCA9CnRvIGRldGVybWluZSB0aGUgY29tcGF0 aWJpbGl0eSB2ZXJzaW9uLiBUaGUgbG9ncyBzaG93cyB0aGF0IGVuZ2luZS1zZXR1PQpwIGRldGVj dHMgMiBjbHVzdGVycyB2ZXJzaW9uczogMy4zIGFuZCAzLjYuIEluZGVlZCwgdGhlcmUgaXMgMiBj bHVzdGVycz0KIHJlZ2lzdGVyZWQgaW4gdGhlIHRhYmxlOiAiY2x1c3Rlci0zLjYiIGFuZCAiRGVm YXVsdCIKCiJDbHVzdGVyLTMuNiIgKHZlcnNpb24gMy42KT1DMj1BMCBpcyB0aGUgb25seSBjbHVz dGVyIGluIERDIGluIG15IG92aXJ0PQogc2V0dXAuCiJEZWZhdWx0IiAodmVyc2lvbiAzLjMpPUMy PUEwIHNob3VsZCBiZSBhIGNsdXN0ZXIgdGhhdCBzdXJlbHkgSSBkZWxldGVkPQogaW4gYSBwYXN0 IHVwZ3JhZGUuCgpXaHkgYSBjbHVzdGVyIG5hbWVkICJEZWZhdWx0IiAod2l0aCBjb21wYXRpYmls aXR5IHZlcnNpb24gMy4zKSBpcyBzdGlsbD0KIHByZXNlbnQgaW4gdmRzPTVGZ3JvdXAgdGFibGU/ IENsdXN0ZXIgIkRlZmF1bHQiIGlzbid0IGRpc3BsYXllZCBhbnl3aGU9CnJlIGluIHRoZSB3ZWIg aW50ZXJmYWNlLgoKQW55IGNsdWUgdG8gc29sdmUgdGhpcyBpc3N1ZT8KClRoYW5rcwoKLS0tLS0t PV89LV9PcGVuR3JvdXB3YXJlX29yZ19OR01pbWUtMzI0MjctMTQ2OTA1ODA2OS4xMzI5MjQtODE2 LS0tLS0tCmNvbnRlbnQtdHlwZTogdGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04CmNvbnRlbnQtbGVu Z3RoOiA5NTEKY29udGVudC10cmFuc2Zlci1lbmNvZGluZzogcXVvdGVkLXByaW50YWJsZQoKPGh0 bWw+SGVsbG86PGJyIC8+PGJyIC8+SSYjMzk7bSB0cnlpbmcgdG8gdXBncmFkZSBvdmlydCAzLjYu MyB0byA0LjAsIGI9CnV0IGVuZ2luZS1zZXR1cCBjb21wbGFpbnRzIGFib3V0IHVwZ3JhZGluZyBm cm9tIGluY29tcGF0aWJsZSB2ZXJzaW9uIDMuPQozPGJyIC8+PGJyIC8+SSBzZWUgaW4gdGhlIGVu Z2luZS1zZXR1cCBsb2cgdGhhdCZuYnNwOyB2ZHM9NUZncm91cHMgdGFibD0KZSBpcyBjaGVja2Vk IHRvIGRldGVybWluZSB0aGUgY29tcGF0aWJpbGl0eSB2ZXJzaW9uLiBUaGUgbG9ncyBzaG93cyB0 aGE9CnQgZW5naW5lLXNldHVwIGRldGVjdHMgMiBjbHVzdGVycyB2ZXJzaW9uczogMy4zIGFuZCAz LjYuIEluZGVlZCwgdGhlcmUgPQppcyAyIGNsdXN0ZXJzIHJlZ2lzdGVyZWQgaW4gdGhlIHRhYmxl OiAmcXVvdDtjbHVzdGVyLTMuNiZxdW90OyBhbmQgJnF1bz0KdDtEZWZhdWx0JnF1b3Q7PGJyIC8+ PGJyIC8+JnF1b3Q7Q2x1c3Rlci0zLjYmcXVvdDsgKHZlcnNpb24gMy42KSZuYnNwOyA9CmlzIHRo ZSBvbmx5IGNsdXN0ZXIgaW4gREMgaW4gbXkgb3ZpcnQgc2V0dXAuPGJyIC8+JnF1b3Q7RGVmYXVs dCZxdW90OyAoPQp2ZXJzaW9uIDMuMykmbmJzcDsgc2hvdWxkIGJlIGEgY2x1c3RlciB0aGF0IHN1 cmVseSBJIGRlbGV0ZWQgaW4gYSBwYXN0ID0KdXBncmFkZS48YnIgLz48YnIgLz5XaHkgYSBjbHVz dGVyIG5hbWVkICZxdW90O0RlZmF1bHQmcXVvdDsgKHdpdGggY29tcGE9CnRpYmlsaXR5IHZlcnNp b24gMy4zKSBpcyBzdGlsbCBwcmVzZW50IGluIHZkcz01Rmdyb3VwIHRhYmxlPyBDbHVzdGVyICZx PQp1b3Q7RGVmYXVsdCZxdW90OyBpc24mIzM5O3QgZGlzcGxheWVkIGFueXdoZXJlIGluIHRoZSB3 ZWIgaW50ZXJmYWNlLjxicj0KIC8+PGJyIC8+QW55IGNsdWUgdG8gc29sdmUgdGhpcyBpc3N1ZT88 YnIgLz48YnIgLz5UaGFua3M8L2h0bWw+CgotLS0tLS09Xz0tX09wZW5Hcm91cHdhcmVfb3JnX05H TWltZS0zMjQyNy0xNDY5MDU4MDY5LjEzMjkyNC04MTYtLS0tLS0tLQoKCg== --===============6252472458622702499==-- From mzamazal at redhat.com Fri Jul 22 05:13:48 2016 Content-Type: multipart/mixed; boundary="===============3026521119431939386==" MIME-Version: 1.0 From: Milan Zamazal To: users at ovirt.org Subject: Re: [ovirt-users] Upgrade 3.6 to 4.0 and "ghost" incompatible cluster version Date: Fri, 22 Jul 2016 11:13:44 +0200 Message-ID: <87eg6m592v.fsf@redhat.com> In-Reply-To: 7eab-57900c00-7b9-278f27c0@161679876 --===============3026521119431939386== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable "Federico Sayd" writes: > I'm trying to upgrade ovirt 3.6.3 to 4.0, but engine-setup complaints abo= ut upgrading from incompatible version 3.3 > > I see in the engine-setup log that=C2=A0 vds_groups table is checked to d= etermine > the compatibility version. The logs shows that engine-setup detects 2 clu= sters > versions: 3.3 and 3.6. Indeed, there is 2 clusters registered in the tabl= e: > "cluster-3.6" and "Default" > > "Cluster-3.6" (version 3.6)=C2=A0 is the only cluster in DC in my ovirt s= etup. > "Default" (version 3.3)=C2=A0 should be a cluster that surely I deleted i= n a past upgrade. > > Why a cluster named "Default" (with compatibility version 3.3) is still p= resent > in vds_group table? Cluster "Default" isn't displayed anywhere in the web > interface. It looks like a bug to me. The cluster should be either missing in the database or present in the web interface. Could you please provide us more details about the problem? It might help us to investigate the issue if you could do the following: - Install ovirt-engine-webadmin-portal-debuginfo package. - Restart Engine. - Go to the main Clusters tab. - Refresh the page in your browser. - Send us the parts of engine.log and ui.log corresponding to the refresh action. > Any clue to solve this issue? As a workaround, if you are sure you don't have anything in Default cluster, you may try to set compatibility_version to "3.6" for "Default" cluster in vds_groups database table. --===============3026521119431939386==-- From fsayd at uncu.edu.ar Fri Jul 22 09:21:50 2016 Content-Type: multipart/mixed; boundary="===============0960692473751065748==" MIME-Version: 1.0 From: Federico Alberto Sayd To: users at ovirt.org Subject: Re: [ovirt-users] Upgrade 3.6 to 4.0 and "ghost" incompatible cluster version Date: Fri, 22 Jul 2016 10:20:56 -0300 Message-ID: <1bdc53bc-3c25-a03d-2da8-09f6e4a737f9@uncu.edu.ar> In-Reply-To: 87eg6m592v.fsf@redhat.com --===============0960692473751065748== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable El 22/07/16 a las 06:13, Milan Zamazal escribi=C3=B3: > "Federico Sayd" writes: > >> I'm trying to upgrade ovirt 3.6.3 to 4.0, but engine-setup complaints ab= out upgrading from incompatible version 3.3 >> >> I see in the engine-setup log that vds_groups table is checked to deter= mine >> the compatibility version. The logs shows that engine-setup detects 2 cl= usters >> versions: 3.3 and 3.6. Indeed, there is 2 clusters registered in the tab= le: >> "cluster-3.6" and "Default" >> >> "Cluster-3.6" (version 3.6) is the only cluster in DC in my ovirt setup. >> "Default" (version 3.3) should be a cluster that surely I deleted in a = past upgrade. >> >> Why a cluster named "Default" (with compatibility version 3.3) is still = present >> in vds_group table? Cluster "Default" isn't displayed anywhere in the web >> interface. > It looks like a bug to me. The cluster should be either missing in the > database or present in the web interface. > > Could you please provide us more details about the problem? It might > help us to investigate the issue if you could do the following: > > - Install ovirt-engine-webadmin-portal-debuginfo package. > - Restart Engine. > - Go to the main Clusters tab. > - Refresh the page in your browser. > - Send us the parts of engine.log and ui.log corresponding to the > refresh action. > >> Any clue to solve this issue? > As a workaround, if you are sure you don't have anything in Default > cluster, you may try to set compatibility_version to "3.6" for "Default" > cluster in vds_groups database table. Hi Milan: I solved the issue. I connected through ovirt-shell. The shell listed = the two clusters and let me to delete the 3.3 "ghost" cluster. I don't know why this cluster was visible by ovirt-shell but not by WebUI. I migrated the engine from Centos 6 to Centos 7 in a new VM. I will try = to install ovirt-engine-webadmin-portal-debuginfo in the old engine VM = (I took a VM snapshot previously to delete the 3.3 cluster) and send = you the debug info. Thanks for your help. Federico --===============0960692473751065748==--