[ovirt-users] Cluster upgrade from 3.6 to 4.1 fails

[Michal Skrivanek]

> On 17 Mar 2017, at 20:58, Joop <jvdwege at xs4all.nl> wrote:
> 
> On 17-3-2017 20:33, Michal Skrivanek wrote:
>> 
>>> On 17 Mar 2017, at 11:55, jvdwege < <mailto:jvdwege at xs4all.nl>jvdwege at xs4all.nl <mailto:jvdwege at xs4all.nl>> wrote:
>>> 
>>> As per the subject I'm trying to upgrade my ovirt install and sofar the upgrade has been smooth.
>>> I'm running hosted-engine in Centos7.3 and my hosts are running Fedora24 now with ovirt-4.1
>>> If I try to upgrade my cluster from version 3.6 to 4.0 or 4.1 I receive an error message and can't find a solution using google. First I get the following                 message:
>>> 
>>> All running VMs will be temporarily reconfigured to use the previous cluster compatibility version and marked pending configuration change.
>>> In order to change the cluster compatibility version of the VM to a new version, the VM needs to be manually shut down and restarted.
>>> There are 1 running VM(s) affected by this change.
>>> 
>>> Are you sure you want to change the Cluster Compatibility Version?
>>> 
>>> Yes, I want to change version :-) so I click OK
>>> I then get the following error message:
>>>  
>>> Error while executing action: 
>>> 
>>> Cannot edit Cluster. Illegal number of monitors is provided, max allowed number of monitors is 1 for VNC and the max number in the ValidNumOfMonitors                       configuration variable for SPICE.
>>> Cannot edit VM. Illegal number of monitors is provided, max allowed number of monitors is 1 for VNC and the max number in the ValidNumOfMonitors configuration variable for SPICE.
>>>  
>>> Anyone has seen this before and is able to help?
>> 
>> Is that an old VM, perhaps from 3.5 or even earlier? Has it been restarted since? Can you shut it down now and rerun after the cluster change? That would likely be the most simple resolution.
>> If there are troubles even after the VM is Down try to edit and swithc console from VNC to SPICE or vice versa and run again
>> 
>> 
> The problem is that it is the hosted-engine itself that is blocking the upgrade. There is only one VM running but maybe there is one of the shutdown VMs that is blocking this. Will have a look at all of them and save their config to see if that helps.

Ah, right, yes, if you do not have anything else running then it’s failing on one of those Down VMs. If you have a lot of them a direct db query might be fastest to find out (we’re still working on improvement to log the actual VM name that failed)

> 
> Thanks,
> 
> Joop
> 
> _______________________________________________
> 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/20170317/cb55a2b2/attachment.html>