<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Not really, not when upgrading to 4.0 at any rate. Take chapter 4 in that guide:<div class=""><br class=""></div><div class=""></div><div class=""><a href="http://www.ovirt.org/documentation/upgrade-guide/chap-Post-Upgrade_Tasks/" class="">http://www.ovirt.org/documentation/upgrade-guide/chap-Post-Upgrade_Tasks/</a></div><div class=""><br class=""></div><div class="">When you perform these steps, you are advised that you now need to restart the VMs to enable the new 4.0 compatible configurations.</div><div class=""><br class=""></div><div class="">As there is no 4.1 upgrade guide, I’m left to interpret Chapter 1 to imply that you need to be at 4.0 to go to 4.1. But does that mean just having the Cluster and DC levels at 4.0, or also having your VMs running at 4.0? This wasn’t applicable to 3.6, so there’s no parallel here. Basically, I’m concerned that a similar procedure for setting Cluster & DC compatibility to 4.1 will not properly handle VMs still running with 3.6 configs, and hoping someone has concrete knowledge of this step that can chime in.<br class=""><div class=""><div class=""><br class=""></div><div class="">FYI, the breadcrumbs on the web site don’t actually work, they give you a page with the right number of list items for what you’re reading, but no actual links to the chapters (the href is present, but no link text exists).</div><div class=""><br class=""></div><div class=""> -Darrell</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 26, 2017, at 1:10 AM, Fred Rolland <<a href="mailto:frolland@redhat.com" class="">frolland@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi,<br class=""><br class="">Restart the VMs is not part of the upgrade procedure.<br class=""></div><div class="">You can check the upgrade guide :<br class=""><a href="http://www.ovirt.org/documentation/upgrade-guide/chap-Updating_the_oVirt_Environment/" class="">http://www.ovirt.org/documentation/upgrade-guide/chap-Updating_the_oVirt_Environment/</a><br class=""><br class=""></div><div class="">Regards,<br class=""></div><div class="">Fred<br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Feb 24, 2017 at 10:44 PM, Darrell Budic <span dir="ltr" class=""><<a href="mailto:budic@onholyground.com" target="_blank" class="">budic@onholyground.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I’m upgrading my main cluster from 3.6 to 4.1, and I’m currently at 4.0. I’ve upgraded the cluster and datacenter compatibility versions to 4.0, and now all my VMs are pending restart to update their configs to 4.0.<br class="">
<br class="">
My question is “Do I need to do this here, or can I go ahead and update the engine and host nodes to 4.1, update compatibility to 4.1, and then restart all the VMs to get them on 4.1”? Or is that unsafe, will I screw them up if I go to 4.1 compatibility in this state?<br class="">
<br class="">
Thanks,<br class="">
<br class="">
-Darrell<br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
Users mailing list<br class="">
<a href="mailto:Users@ovirt.org" class="">Users@ovirt.org</a><br class="">
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" class="">http://lists.ovirt.org/<wbr class="">mailman/listinfo/users</a><br class="">
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></div></body></html>