Re: [ovirt-users] Cannot change Cluster Compatibility Version when a VM is active

[Ernest Beinrohr]

On 23.09.2016 16:49, Bruckner, Simone wrote:


Hi all,

  I am trying to upgrade an oVirt installation (3.6.7.5-1.el6) to 4.0. 
My datacenters and clusters have 3.5 compatibility settings.


I just finished this. Only took about 2 weeks for 8 hosts ;) I had to do 
this:


3.5 -> 3.6

- upgrade engine to 3.6
- create a new cluster with CL 3.6
- for each host:
  - maintenance
  - reinstall to el7 + RPMs (yay for puppet)
  - add to new 3.6 cluster
  - activate
  - migrate some machines to new cluster (no way back!)
- elevate CL of old (empty) cluster to 3.6
- migrate everything back for each host

3.6 -> 4.0
- for each host:
  - maintenance
  - upgrade RPMS to 4.0
  - activate
- elevate CL to 4.0 (can be done with running VMs)

--
Ernest Beinrohr, AXON PRO
Ing , RHCE 
, RHCVA 
, LPIC 
, VCA ,

+421-2-62410360 +421-903-482603
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cannot change Cluster Compatibility Version when a VM is active

[Bruckner, Simone]

Michal,

  thanks!

All the best,
Simone

Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Michal Skrivanek
Gesendet: Freitag, 23. September 2016 17:22
An: Albl, Oliver <oliver.a...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot change Cluster Compatibility Version when a 
VM is active


On 23 Sep 2016, at 17:16, Albl, Oliver 
<oliver.a...@fabasoft.com<mailto:oliver.a...@fabasoft.com>> wrote:

Michal,

  thank you for your quick response! I am running 300+ VMs so any other (safe) 
option would be very welcome…

and are they all in a 3.5 cluster?
Your priority should be to get them to 3.6 compatibility prior upgrading to 
4.0, then once in 4.0.3+ there is a safe-enough way how to properly update 3.6 
to a 4.0 cluster level.

otherwise, any <3.6.7 would allow you to do that or there is a manual postgres 
workaround mentioned in that bug which you can try/risk - basically as long as 
you can reboot those VMs in a foreseeable future(prior to use any of the new 
features) you can follow the manual workaround and upgrade to 3.6….just make 
sure you stop and start them eventually



All the best,
Simone

Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org] Im Auftrag von Michal Skrivanek
Gesendet: Freitag, 23. September 2016 16:57
An: Bruckner, Simone 
<simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>>
Cc: users@ovirt.org<mailto:users@ovirt.org>
Betreff: Re: [ovirt-users] Cannot change Cluster Compatibility Version when a 
VM is active


On 23 Sep 2016, at 16:49, Bruckner, Simone 
<simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>> wrote:

Hi all,

  I am trying to upgrade an oVirt installation (3.6.7.5-1.el6) to 4.0. My 
datacenters and clusters have 3.5 compatibility settings.

I followed the instructions from 
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/ but cannot 
proceed in engine-setup as 3.5 compatibility is not supported.

When trying to change cluster compatibility from 3.5 to 3.6 I receive “Cannot 
change Cluster Compatibility Version when a VM is active. Please shutdown all 
VMs in the Cluster.” According 
tohttps://bugzilla.redhat.com/show_bug.cgi?id=1341023 this should be fixed in 
3.6.7. Any ideas?

this bug is blocking it, later bugs
(linked from there) allows it, though there are other issues…so if you have an 
option to shut them down please do so.
note those are RHEV bugs, not oVirt bugs so the exact build may differ

Thanks,
michal




Best Regards,
Simone Bruckner

___
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cannot change Cluster Compatibility Version when a VM is active

[Michal Skrivanek]

> On 23 Sep 2016, at 17:16, Albl, Oliver <oliver.a...@fabasoft.com> wrote:
> 
> Michal,
>  
>   thank you for your quick response! I am running 300+ VMs so any other 
> (safe) option would be very welcome…

and are they all in a 3.5 cluster?
Your priority should be to get them to 3.6 compatibility prior upgrading to 
4.0, then once in 4.0.3+ there is a safe-enough way how to properly update 3.6 
to a 4.0 cluster level.

otherwise, any <3.6.7 would allow you to do that or there is a manual postgres 
workaround mentioned in that bug which you can try/risk - basically as long as 
you can reboot those VMs in a foreseeable future(prior to use any of the new 
features) you can follow the manual workaround and upgrade to 3.6….just make 
sure you stop and start them eventually

>  
> All the best,
> Simone
>  
> Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
> Michal Skrivanek
> Gesendet: Freitag, 23. September 2016 16:57
> An: Bruckner, Simone <simone.bruck...@fabasoft.com>
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Cannot change Cluster Compatibility Version when a 
> VM is active
>  
>  
> On 23 Sep 2016, at 16:49, Bruckner, Simone <simone.bruck...@fabasoft.com 
> <mailto:simone.bruck...@fabasoft.com>> wrote:
>  
> Hi all,
>  
>   I am trying to upgrade an oVirt installation (3.6.7.5-1.el6) to 4.0. My 
> datacenters and clusters have 3.5 compatibility settings.
>  
> I followed the instructions from 
> http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/ 
> <http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/> but cannot 
> proceed in engine-setup as 3.5 compatibility is not supported.
>  
> When trying to change cluster compatibility from 3.5 to 3.6 I receive “Cannot 
> change Cluster Compatibility Version when a VM is active. Please shutdown all 
> VMs in the Cluster.” According 
> tohttps://bugzilla.redhat.com/show_bug.cgi?id=1341023 
> <https://bugzilla.redhat.com/show_bug.cgi?id=1341023> this should be fixed in 
> 3.6.7. Any ideas?
>  
> this bug is blocking it, later bugs 
> (linked from there) allows it, though there are other issues…so if you have 
> an option to shut them down please do so.
> note those are RHEV bugs, not oVirt bugs so the exact build may differ
>  
> Thanks,
> michal
> 
> 
>  
> Best Regards,
> Simone Bruckner
>  
> ___
> Users mailing list
> Users@ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users 
> <http://lists.ovirt.org/mailman/listinfo/users>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cannot change Cluster Compatibility Version when a VM is active

[Albl, Oliver]

Michal,

  thank you for your quick response! I am running 300+ VMs so any other (safe) 
option would be very welcome…

All the best,
Simone

Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Michal Skrivanek
Gesendet: Freitag, 23. September 2016 16:57
An: Bruckner, Simone <simone.bruck...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot change Cluster Compatibility Version when a 
VM is active


On 23 Sep 2016, at 16:49, Bruckner, Simone 
<simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>> wrote:

Hi all,

  I am trying to upgrade an oVirt installation (3.6.7.5-1.el6) to 4.0. My 
datacenters and clusters have 3.5 compatibility settings.

I followed the instructions from 
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/ but cannot 
proceed in engine-setup as 3.5 compatibility is not supported.

When trying to change cluster compatibility from 3.5 to 3.6 I receive “Cannot 
change Cluster Compatibility Version when a VM is active. Please shutdown all 
VMs in the Cluster.” According 
tohttps://bugzilla.redhat.com/show_bug.cgi?id=1341023 this should be fixed in 
3.6.7. Any ideas?

this bug is blocking it, later bugs
(linked from there) allows it, though there are other issues…so if you have an 
option to shut them down please do so.
note those are RHEV bugs, not oVirt bugs so the exact build may differ

Thanks,
michal



Best Regards,
Simone Bruckner

___
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cannot change Cluster Compatibility Version when a VM is active

[Michal Skrivanek]

> On 23 Sep 2016, at 16:49, Bruckner, Simone  
> wrote:
> 
> Hi all,
>  
>   I am trying to upgrade an oVirt installation (3.6.7.5-1.el6) to 4.0. My 
> datacenters and clusters have 3.5 compatibility settings.
>  
> I followed the instructions from 
> http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/ 
>  but cannot 
> proceed in engine-setup as 3.5 compatibility is not supported.
>  
> When trying to change cluster compatibility from 3.5 to 3.6 I receive “Cannot 
> change Cluster Compatibility Version when a VM is active. Please shutdown all 
> VMs in the Cluster.” According 
> tohttps://bugzilla.redhat.com/show_bug.cgi?id=1341023 
>  this should be fixed in 
> 3.6.7. Any ideas?

this bug is blocking it, later bugs 
(linked from there) allows it, though there are other issues…so if you have an 
option to shut them down please do so.
note those are RHEV bugs, not oVirt bugs so the exact build may differ

Thanks,
michal

>  
> Best Regards,
> Simone Bruckner
>  
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Cannot change Cluster Compatibility Version when a VM is active

[Bruckner, Simone]

Hi all,

  I am trying to upgrade an oVirt installation (3.6.7.5-1.el6) to 4.0. My 
datacenters and clusters have 3.5 compatibility settings.

I followed the instructions from 
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/ but cannot 
proceed in engine-setup as 3.5 compatibility is not supported.

When trying to change cluster compatibility from 3.5 to 3.6 I receive "Cannot 
change Cluster Compatibility Version when a VM is active. Please shutdown all 
VMs in the Cluster." According to 
https://bugzilla.redhat.com/show_bug.cgi?id=1341023 this should be fixed in 
3.6.7. Any ideas?

Best Regards,
Simone Bruckner

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users