<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 4, 2017 at 3:43 PM, Robert Story <span dir="ltr"><<a href="mailto:rstory@tislabs.com" target="_blank">rstory@tislabs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, 23 Dec 2016 13:58:09 -0500 Robert wrote:<br>
RS> I'm trying to upgrade to 4.0 from 3.6. I dutify checked that my clusters<br>
RS> were set to 3.6 compatibility and started the engine upgrade. unfortunately<br>
RS> I forgot to check the unused Default cluser. :-/<br>
<br>
So it turns out that it wasn't the cluster compatibility that I missed, but<br>
that the data center compatibility level needed to be updated to 3.6 as<br>
well. I just didn't read the error message closely enough.<br>
<br>
RS> So the upgrade failed, but the 4.0 rpms were installed, so the engine won't<br>
RS> start. How can I fix the compat level (or delete Default cluster)?<br>
<br>
For the record, I ended up using 'yum history' to roll back the updated<br>
packages, and was then able to start the engine, change the datacenter to<br>
3.6, and re-run setup successfully.<br></blockquote><div><br></div><div>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?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
Robert<br>
<br>
--<br>
Senior Software Engineer @ Parsons<br>
</div></div><br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>