10:44 p.m.
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.
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?
Thanks,
-Darrell
9:10 a.m.
Hi,
Restart the VMs is not part of the upgrade procedure.
You can check the upgrade guide :
http://www.ovirt.org/documentation/upgrade-guide/chap-Updating_the_oVirt_...
Regards,
Fred
On Fri, Feb 24, 2017 at 10:44 PM, Darrell Budic <budic(a)onholyground.com>
wrote:
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.
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?
Thanks,
-Darrell
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:39 p.m.
--Apple-Mail=_84359FA6-819A-4AC9-8067-09D38A434D8C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
Not really, not when upgrading to 4.0 at any rate. Take chapter 4 in =
that guide:
=
http://www.ovirt.org/documentation/upgrade-guide/chap-Post-Upgrade_Tasks/ =
<http://www.ovirt.org/documentation/upgrade-guide/chap-Post-Upgrade_Tasks/=
When you perform these steps, you are advised that you now need to =
restart the VMs to enable the new 4.0 compatible configurations.
As there is no 4.1 upgrade guide, I=E2=80=99m 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=E2=80=99t applicable to 3.6, so there=E2=80=99s =
no parallel here. Basically, I=E2=80=99m 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.
FYI, the breadcrumbs on the web site don=E2=80=99t actually work, they =
give you a page with the right number of list items for what you=E2=80=99r=
e reading, but no actual links to the chapters (the href is present, but =
no link text exists).
-Darrell
>
http://lists.ovirt.org/mailman/listinfo/users =
<http://lists.ovirt.org/mailman/listinfo/users <br
class=3D"" My question is =E2=80=9CDo 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=E2=80=9D? Or is that =
unsafe, will I screw them up if I go to 4.1 compatibility in this =
state?<br class=3D"" <br class=3D"" Thanks,<br class=3D"" <br
class=3D"" -Darrell<br
class=3D"" <br class=3D"" ______________________________<wbr
class=3D"">_________________<br =
class=3D"" Users mailing list<br
class=3D"" <a
href=3D"mailto:Users@ovirt.org"
class=3D"">Users(a)ovirt.org</a><br =
class=3D"" <a
href=3D"http://lists.ovirt.org/mailman/listinfo/users" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">http://lists.ovirt.org/<wbr =
class=3D"">mailman/listinfo/users</a><br class=3D"" </blockquote></div><br
class=3D""></div
</div></blockquote></div><br
class=3D""></div></div></div></body></html>=
--Apple-Mail=_84359FA6-819A-4AC9-8067-09D38A434D8C--
On Feb 26, 2017, at 1:10 AM, Fred Rolland <frolland(a)redhat.com>
wrote:
=20
Hi,
=20
Restart the VMs is not part of the upgrade procedure.
You can check the upgrade guide :
=
http://www.ovirt.org/documentation/upgrade-guide/chap-Updating_the_oVirt_E=
nvironment/ =
<http://www.ovirt.org/documentation/upgrade-guide/chap-Updating_the_oVirt_=
Environment/=20
Regards,
Fred
=20
On Fri, Feb 24, 2017 at 10:44 PM, Darrell Budic =
<budic(a)onholyground.com
<mailto:budic@onholyground.com>> wrote:
I=E2=80=99m upgrading my main cluster from 3.6 to 4.1, and
I=E2=80=99m =
currently at 4.0. I=E2=80=99ve 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.
=20
My question is =E2=80=9CDo 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=E2=80=9D? Or is =
that unsafe, will I screw them up if I go to 4.1 compatibility in this =
state?
=20
> Thanks,
=20
> -Darrell
=20
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org=20
--Apple-Mail=_84359FA6-819A-4AC9-8067-09D38A434D8C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Not really, not when upgrading to 4.0 at any rate. Take =
chapter 4 in that guide:<div class=3D""><br
class=3D""></div><div =
class=3D""></div><div class=3D""><a =
href=3D"http://www.ovirt.org/documentation/upgrade-guide/chap-Post-U...
_Tasks/" =
class=3D"">http://www.ovirt.org/documentation/upgrade-guide/...
ade_Tasks/</a></div><div class=3D""><br
class=3D""></div><div =
class=3D"">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=3D""><br
class=3D""></div><div =
class=3D"">As there is no 4.1 upgrade guide, I=E2=80=99m 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=E2=80=99t applicable to 3.6, =
so there=E2=80=99s no parallel here. Basically, I=E2=80=99m 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=3D""><div class=3D""><div
class=3D""><br class=3D""></div><div =
class=3D"">FYI, the breadcrumbs on the web site don=E2=80=99t actually =
work, they give you a page with the right number of list items for what =
you=E2=80=99re reading, but no actual links to the chapters (the href is =
present, but no link text exists).</div><div class=3D""><br =
class=3D""></div><div class=3D"">
-Darrell</div><div class=3D""><br =
class=3D""><div><blockquote type=3D"cite"
class=3D""><div class=3D"">On =
Feb 26, 2017, at 1:10 AM, Fred Rolland <<a =
href=3D"mailto:frolland@redhat.com"
class=3D"">frolland(a)redhat.com</a>&gt;=
wrote:</div><br class=3D"Apple-interchange-newline"><div
class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"">Hi,<br
class=3D""><br =
class=3D"">Restart the VMs is not part of the upgrade procedure.<br =
class=3D""></div><div class=3D"">You can check the
upgrade guide :<br =
class=3D""><a =
href=3D"http://www.ovirt.org/documentation/upgrade-guide/chap-Updati...
_oVirt_Environment/" =
class=3D"">http://www.ovirt.org/documentation/upgrade-guide/...
the_oVirt_Environment/</a><br class=3D""><br
class=3D""></div><div =
class=3D"">Regards,<br class=3D""></div><div
class=3D"">Fred<br =
class=3D""></div></div><div
class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Fri, Feb 24, 2017 at 10:44 PM, Darrell Budic =
<span dir=3D"ltr" class=3D""><<a
href=3D"mailto:budic@onholyground.com"=
target=3D"_blank"
class=3D"">budic(a)onholyground.com</a>&gt;</span> =
wrote:<br class=3D""><blockquote class=3D"gmail_quote"
style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I=E2=80=99m =
upgrading my main cluster from 3.6 to 4.1, and I=E2=80=99m currently at =
4.0. I=E2=80=99ve 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=3D""
2827
days inactive
2829
days old
2 comments
2 participants
participants (2)
-
Darrell Budic -
Fred Rolland