recovering from failed 3.6 -> 4.0 engine upgrade
--Sig_/LLTH9NASuGEOU8UP2Gh7Nzg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello, I'm trying to upgrade to 4.0 from 3.6. I dutify checked that my clusters were set to 3.6 compatibility and started the engine upgrade. unfortunately I forgot to check the unused Default cluser. :-/ So the upgrade failed, but the 4.0 rpms were installed, so the engine won't start. How can I fix the compat level (or delete Default cluster)? I found this message <http://lists.ovirt.org/pipermail/users/2016-June/040801.html> that suggests that the engine should be startable if only the update rpms were installed, but part of the install procedure updates all the rpms, including the engine. I created this bug: https://bugzilla.redhat.com/show_bug.cgi?id=3D1408493 Any help on how to proceed appreciated, either here or on IRC.. Robert --=20 Senior Software Engineer @ Parsons --Sig_/LLTH9NASuGEOU8UP2Gh7Nzg Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlhdc8EACgkQ7/fVLLY1mnilQACgkeIG2oH6zp5BfeiwvV/47Vi3 4okAoJT5p+CfBvJqlgW4ZRtySOQEKHAU =SYd/ -----END PGP SIGNATURE----- --Sig_/LLTH9NASuGEOU8UP2Gh7Nzg--
--Sig_/9p+SAQVuQAoloUkrr6/0GIm Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 23 Dec 2016 13:58:09 -0500 Robert wrote: RS> I'm trying to upgrade to 4.0 from 3.6. I dutify checked that my clusters RS> were set to 3.6 compatibility and started the engine upgrade. unfortuna= tely RS> I forgot to check the unused Default cluser. :-/ So it turns out that it wasn't the cluster compatibility that I missed, but that the data center compatibility level needed to be updated to 3.6 as well. I just didn't read the error message closely enough. RS> So the upgrade failed, but the 4.0 rpms were installed, so the engine w= on't RS> start. How can I fix the compat level (or delete Default cluster)? For the record, I ended up using 'yum history' to roll back the updated packages, and was then able to start the engine, change the datacenter to 3.6, and re-run setup successfully. Robert --=20 Senior Software Engineer @ Parsons --Sig_/9p+SAQVuQAoloUkrr6/0GIm Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlhtCgEACgkQ7/fVLLY1mngSYgCeJMo1ju0UVUYASekdGVgmdVMz YFgAn3xdF5zdTAeoyJIuZYXJ0eQXyF79 =tjZg -----END PGP SIGNATURE----- --Sig_/9p+SAQVuQAoloUkrr6/0GIm--
On Wed, Jan 4, 2017 at 3:43 PM, Robert Story <rstory@tislabs.com> wrote:
On Fri, 23 Dec 2016 13:58:09 -0500 Robert wrote: RS> I'm trying to upgrade to 4.0 from 3.6. I dutify checked that my clusters RS> were set to 3.6 compatibility and started the engine upgrade. unfortunately RS> I forgot to check the unused Default cluser. :-/
So it turns out that it wasn't the cluster compatibility that I missed, but that the data center compatibility level needed to be updated to 3.6 as well. I just didn't read the error message closely enough.
RS> So the upgrade failed, but the 4.0 rpms were installed, so the engine won't RS> start. How can I fix the compat level (or delete Default cluster)?
For the record, I ended up using 'yum history' to roll back the updated packages, and was then able to start the engine, change the datacenter to 3.6, and re-run setup successfully.
engine-setup should be completely transactional and it should rollback by itself on failures; could you please share engine-setup logs from your failed attempt?
Robert
-- Senior Software Engineer @ Parsons
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Sig_/gcKXjwi.OE7.mNZByq17Gky Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 4 Jan 2017 16:43:07 +0100 Simone wrote: ST> engine-setup should be completely transactional and it should rollback = by ST> itself on failures; could you please share engine-setup logs from your ST> failed attempt? See https://bugzilla.redhat.com/show_bug.cgi?id=3D1408493 Robert --=20 Senior Software Engineer @ Parsons --Sig_/gcKXjwi.OE7.mNZByq17Gky Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlhtIk4ACgkQ7/fVLLY1mngIzACbBlfzL47NeCP4tQZ7sIkAZeWS qCUAoIsO819O0Cp3E7/i4etmyzj0jRPI =oXqU -----END PGP SIGNATURE----- --Sig_/gcKXjwi.OE7.mNZByq17Gky--
On Wed, Jan 4, 2017 at 5:26 PM, Robert Story <rstory@tislabs.com> wrote:
On Wed, 4 Jan 2017 16:43:07 +0100 Simone wrote: ST> engine-setup should be completely transactional and it should rollback by ST> itself on failures; could you please share engine-setup logs from your ST> failed attempt?
OK, thanks. I commented on the bug.
Robert
-- Senior Software Engineer @ Parsons
participants (2)
-
Robert Story -
Simone Tiraboschi