--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 --Sig_/9p+SAQVuQAoloUkrr6/0GIm--

--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 --Sig_/gcKXjwi.OE7.mNZByq17Gky--