[ovirt-users] recovering from failed 3.6 -> 4.0 engine upgrade

Simone Tiraboschi stirabos at redhat.com
Wed Jan 4 15:43:07 UTC 2017


On Wed, Jan 4, 2017 at 3:43 PM, Robert Story <rstory at 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 at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170104/0d183cba/attachment.html>


More information about the Users mailing list