[ovirt-users] Re: Unable to change cluster and data center compatibility version
Hi Jonathon,
it's difficult to say as it's so long since I ran that
version.
I notice on 4.2 nodes that they have
Cluster Compatibility Version: 3.6,4.0,4.1,4.2
Would it to be better to update the hosts first?
Regards,
Paul S.
From: Jonathan Mathews
Sent: 25 February 2019 11:11
To: Staniforth, Paul
Cc: Shani Leviim; Ovirt Users
Subject: Re: [ovirt-users] Re: Unable to change cluster and data center
compatibility version
Hi Paul
Thank you for bringing this to my attention.
It does look like I will need to upgrade all my hosts to CentOS 7.
But would the prevent me from changing my cluster compatibility version to 3.6?
Thanks
On Wed, Feb 20, 2019 at 11:59 AM Staniforth, Paul
mailto:p.stanifo...@leedsbeckett.ac.uk>> wrote:
Does oVirt 4.0 support Centos6 hosts?
Regards,
Paul S.
From: Jonathan Mathews mailto:jm3185...@gmail.com>>
Sent: 20 February 2019 06:25
To: Shani Leviim
Cc: Ovirt Users
Subject: [ovirt-users] Re: Unable to change cluster and data center
compatibility version
Hi Shani
Yes, I did try and change the cluster compatibility first, and that's when I
got the error: Ovirt: Some of the hosts still use legacy protocol which is not
supported by cluster 3.6 or higher. In order to change it a host needs to be
put to maintenance and edited in advanced options section.
I did go through the article you suggested, however, I did not see anything
that would help.
Thanks
On Tue, Feb 19, 2019 at 3:46 PM Shani Leviim
mailto:slev...@redhat.com>> wrote:
Hi Jonathan,
Did you try first to change the compatibility of all clusters and then change
the data center's compatibility?
This once seems related: https://bugzilla.redhat.com/show_bug.cgi?id=1375567
Regards,
Shani Leviim
On Tue, Feb 19, 2019 at 11:01 AM Jonathan Mathews
mailto:jm3185...@gmail.com>> wrote:
Good Day
I have been trying to upgrade a clients oVirt from 3.6 to 4.0 but have run into
an issue where I am unable to change the cluster and data center compatibility
version.
I get the following error in the GUI:
Ovirt: Some of the hosts still use legacy protocol which is not supported by
cluster 3.6 or higher. In order to change it a host needs to be put to
maintenance and edited in advanced options section.
This error was received with all VM's off and all hosts in maintenance.
The environment has the following currently installed:
Engine - CentOS 7.4 - Ovirt Engine 3.6.7.5
Host1 - CentOS 6.9 - VDSM 4.16.30
Host2 - CentOS 6.9 - VDSM 4.16.30
Host3 - CentOS 6.9 - VDSM 4.16.30
I also have the following from engine.log
[root@ovengine ~]# tail -f /var/log/ovirt-engine/engine.log
2018-09-22 07:11:33,920 INFO
[org.ovirt.engine.core.vdsbroker.VmsStatisticsFetcher]
(DefaultQuartzScheduler_Worker-93) [7533985f] Fetched 0 VMs from VDS
'd82a026c-31b4-4efc-8567-c4a6bdcaa826'
2018-09-22 07:11:34,685 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand]
(DefaultQuartzScheduler_Worker-99) [4b7e3710] FINISH,
DisconnectStoragePoolVDSCommand, log id: 1ae6f0a9
2018-09-22 07:11:34,687 INFO
[org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand]
(DefaultQuartzScheduler_Worker-99) [2a6aa6f6] Running command:
DisconnectHostFromStoragePoolServersCommand internal: true. Entities affected :
ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool
2018-09-22 07:11:34,706 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand]
(DefaultQuartzScheduler_Worker-99) [2a6aa6f6] START,
DisconnectStorageServerVDSCommand(HostName = ovhost3,
StorageServerConnectionManagementVDSParameters:{runAsync='true',
hostId='d82a026c-31b4-4efc-8567-c4a6bdcaa826',
storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageType='NFS',
connectionList='[StorageServerConnections:{id='3fdffb4c-250b-4a4e-b914-e0da1243550e',
connection='172.16.0.10:/raid0/data/_NAS_NFS_Exports_/STORAGE1', iqn='null',
vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null',
nfsTimeo='null', iface='null', netIfaceName='null'},
StorageServerConnections:{id='4d95c8ca-435a-4e44-86a5-bc7f3a0cd606',
connection='172.16.0.20:/data/ov-export', iqn='null', vfsType='null',
mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null',
iface='null', netIfaceName='null'},
StorageServerConnections:{id='82ecbc89-bdf3-4597-9a93-b16f3a6ac117',
connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/4TB', iqn='null',
vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null',
nfsTimeo='null', iface='null', netIfaceName='null'},
StorageServerConnections:{id='29bb3394-fb61-41c0-bb5a-1fa693ec2fe2',
connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/iso', iqn='null',
vfsType='null', mountOptions='null', nfsVersion='V3', nfsRetrans='null',
nfsTimeo='null', iface='null', netIfaceName='null
[ovirt-users] Re: Unable to change cluster and data center compatibility version
Does oVirt 4.0 support Centos6 hosts?
Regards,
Paul S.
From: Jonathan Mathews
Sent: 20 February 2019 06:25
To: Shani Leviim
Cc: Ovirt Users
Subject: [ovirt-users] Re: Unable to change cluster and data center
compatibility version
Hi Shani
Yes, I did try and change the cluster compatibility first, and that's when I
got the error: Ovirt: Some of the hosts still use legacy protocol which is not
supported by cluster 3.6 or higher. In order to change it a host needs to be
put to maintenance and edited in advanced options section.
I did go through the article you suggested, however, I did not see anything
that would help.
Thanks
On Tue, Feb 19, 2019 at 3:46 PM Shani Leviim
mailto:slev...@redhat.com>> wrote:
Hi Jonathan,
Did you try first to change the compatibility of all clusters and then change
the data center's compatibility?
This once seems related: https://bugzilla.redhat.com/show_bug.cgi?id=1375567
Regards,
Shani Leviim
On Tue, Feb 19, 2019 at 11:01 AM Jonathan Mathews
mailto:jm3185...@gmail.com>> wrote:
Good Day
I have been trying to upgrade a clients oVirt from 3.6 to 4.0 but have run into
an issue where I am unable to change the cluster and data center compatibility
version.
I get the following error in the GUI:
Ovirt: Some of the hosts still use legacy protocol which is not supported by
cluster 3.6 or higher. In order to change it a host needs to be put to
maintenance and edited in advanced options section.
This error was received with all VM's off and all hosts in maintenance.
The environment has the following currently installed:
Engine - CentOS 7.4 - Ovirt Engine 3.6.7.5
Host1 - CentOS 6.9 - VDSM 4.16.30
Host2 - CentOS 6.9 - VDSM 4.16.30
Host3 - CentOS 6.9 - VDSM 4.16.30
I also have the following from engine.log
[root@ovengine ~]# tail -f /var/log/ovirt-engine/engine.log
2018-09-22 07:11:33,920 INFO
[org.ovirt.engine.core.vdsbroker.VmsStatisticsFetcher]
(DefaultQuartzScheduler_Worker-93) [7533985f] Fetched 0 VMs from VDS
'd82a026c-31b4-4efc-8567-c4a6bdcaa826'
2018-09-22 07:11:34,685 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand]
(DefaultQuartzScheduler_Worker-99) [4b7e3710] FINISH,
DisconnectStoragePoolVDSCommand, log id: 1ae6f0a9
2018-09-22 07:11:34,687 INFO
[org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand]
(DefaultQuartzScheduler_Worker-99) [2a6aa6f6] Running command:
DisconnectHostFromStoragePoolServersCommand internal: true. Entities affected :
ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool
2018-09-22 07:11:34,706 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand]
(DefaultQuartzScheduler_Worker-99) [2a6aa6f6] START,
DisconnectStorageServerVDSCommand(HostName = ovhost3,
StorageServerConnectionManagementVDSParameters:{runAsync='true',
hostId='d82a026c-31b4-4efc-8567-c4a6bdcaa826',
storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageType='NFS',
connectionList='[StorageServerConnections:{id='3fdffb4c-250b-4a4e-b914-e0da1243550e',
connection='172.16.0.10:/raid0/data/_NAS_NFS_Exports_/STORAGE1', iqn='null',
vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null',
nfsTimeo='null', iface='null', netIfaceName='null'},
StorageServerConnections:{id='4d95c8ca-435a-4e44-86a5-bc7f3a0cd606',
connection='172.16.0.20:/data/ov-export', iqn='null', vfsType='null',
mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null',
iface='null', netIfaceName='null'},
StorageServerConnections:{id='82ecbc89-bdf3-4597-9a93-b16f3a6ac117',
connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/4TB', iqn='null',
vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null',
nfsTimeo='null', iface='null', netIfaceName='null'},
StorageServerConnections:{id='29bb3394-fb61-41c0-bb5a-1fa693ec2fe2',
connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/iso', iqn='null',
vfsType='null', mountOptions='null', nfsVersion='V3', nfsRetrans='null',
nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log id: 48c5ffd6
2018-09-22 07:11:34,991 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand]
(DefaultQuartzScheduler_Worker-99) [2a6aa6f6] FINISH,
DisconnectStorageServerVDSCommand, return:
{3fdffb4c-250b-4a4e-b914-e0da1243550e=0,
29bb3394-fb61-41c0-bb5a-1fa693ec2fe2=0, 82ecbc89-bdf3-4597-9a93-b16f3a6ac117=0,
4d95c8ca-435a-4e44-86a5-bc7f3a0cd606=0}, log id: 48c5ffd6
2018-09-22 07:11:56,367 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand]
(default task-29) [1a31cc53] CanDoAction of action 'UpdateVdsGroup' failed for
user admin@internal. Reasons:
VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION
2018-09-22 07:12:41,017 WARN
[org.ovirt.engine.core.bll.storage.UpdateStoragePoolCommand] (default task-29)
[efd285b] CanDoAction of action 'UpdateStoragePool' fai
[ovirt-users] Re: Unable to change cluster and data center compatibility version
Hi Shani
Yes, I did try and change the cluster compatibility first, and that's when
I got the error: Ovirt: Some of the hosts still use legacy protocol which
is not supported by cluster 3.6 or higher. In order to change it a host
needs to be put to maintenance and edited in advanced options section.
I did go through the article you suggested, however, I did not see anything
that would help.
Thanks
On Tue, Feb 19, 2019 at 3:46 PM Shani Leviim wrote:
> Hi Jonathan,
>
> Did you try first to change the compatibility of all clusters and then
> change the data center's compatibility?
> This once seems related:
> https://bugzilla.redhat.com/show_bug.cgi?id=1375567
>
>
> *Regards,*
>
> *Shani Leviim*
>
>
> On Tue, Feb 19, 2019 at 11:01 AM Jonathan Mathews
> wrote:
>
>> Good Day
>>
>> I have been trying to upgrade a clients oVirt from 3.6 to 4.0 but have
>> run into an issue where I am unable to change the cluster and data center
>> compatibility version.
>>
>> I get the following error in the GUI:
>>
>> Ovirt: Some of the hosts still use legacy protocol which is not supported
>> by cluster 3.6 or higher. In order to change it a host needs to be put to
>> maintenance and edited in advanced options section.
>>
>> This error was received with all VM's off and all hosts in maintenance.
>>
>> The environment has the following currently installed:
>>
>> Engine - CentOS 7.4 - Ovirt Engine 3.6.7.5
>> Host1 - CentOS 6.9 - VDSM 4.16.30
>> Host2 - CentOS 6.9 - VDSM 4.16.30
>> Host3 - CentOS 6.9 - VDSM 4.16.30
>>
>> I also have the following from engine.log
>>
>> [root@ovengine ~]# tail -f /var/log/ovirt-engine/engine.log
>> 2018-09-22 07:11:33,920 INFO
>> [org.ovirt.engine.core.vdsbroker.VmsStatisticsFetcher]
>> (DefaultQuartzScheduler_Worker-93) [7533985f] Fetched 0 VMs from VDS
>> 'd82a026c-31b4-4efc-8567-c4a6bdcaa826'
>> 2018-09-22 07:11:34,685 INFO
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand]
>> (DefaultQuartzScheduler_Worker-99) [4b7e3710] FINISH,
>> DisconnectStoragePoolVDSCommand, log id: 1ae6f0a9
>> 2018-09-22 07:11:34,687 INFO
>> [org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand]
>> (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] Running command:
>> DisconnectHostFromStoragePoolServersCommand internal: true. Entities
>> affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool
>> 2018-09-22 07:11:34,706 INFO
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand]
>> (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] START,
>> DisconnectStorageServerVDSCommand(HostName = ovhost3,
>> StorageServerConnectionManagementVDSParameters:{runAsync='true',
>> hostId='d82a026c-31b4-4efc-8567-c4a6bdcaa826',
>> storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageType='NFS',
>> connectionList='[StorageServerConnections:{id='3fdffb4c-250b-4a4e-b914-e0da1243550e',
>> connection='172.16.0.10:/raid0/data/_NAS_NFS_Exports_/STORAGE1',
>> iqn='null', vfsType='null', mountOptions='null', nfsVersion='null',
>> nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'},
>> StorageServerConnections:{id='4d95c8ca-435a-4e44-86a5-bc7f3a0cd606',
>> connection='172.16.0.20:/data/ov-export', iqn='null', vfsType='null',
>> mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null',
>> iface='null', netIfaceName='null'},
>> StorageServerConnections:{id='82ecbc89-bdf3-4597-9a93-b16f3a6ac117',
>> connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/4TB', iqn='null',
>> vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null',
>> nfsTimeo='null', iface='null', netIfaceName='null'},
>> StorageServerConnections:{id='29bb3394-fb61-41c0-bb5a-1fa693ec2fe2',
>> connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/iso', iqn='null',
>> vfsType='null', mountOptions='null', nfsVersion='V3', nfsRetrans='null',
>> nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log id: 48c5ffd6
>> 2018-09-22 07:11:34,991 INFO
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand]
>> (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] FINISH,
>> DisconnectStorageServerVDSCommand, return:
>> {3fdffb4c-250b-4a4e-b914-e0da1243550e=0,
>> 29bb3394-fb61-41c0-bb5a-1fa693ec2fe2=0,
>> 82ecbc89-bdf3-4597-9a93-b16f3a6ac117=0,
>> 4d95c8ca-435a-4e44-86a5-bc7f3a0cd606=0}, log id: 48c5ffd6
>> 2018-09-22 07:11:56,367 WARN
>> [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-29)
>> [1a31cc53] CanDoAction of action 'UpdateVdsGroup' failed for user
>> admin@internal. Reasons:
>> VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION
>> 2018-09-22 07:12:41,017 WARN
>> [org.ovirt.engine.core.bll.storage.UpdateStoragePoolCommand] (default
>> task-29) [efd285b] CanDoAction of action 'UpdateStoragePool' failed for
>> user admin@internal. Reasons:
>> VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList
>>
[ovirt-users] Re: Unable to change cluster and data center compatibility version
Hi Jonathan,
Did you try first to change the compatibility of all clusters and then
change the data center's compatibility?
This once seems related: https://bugzilla.redhat.com/show_bug.cgi?id=1375567
*Regards,*
*Shani Leviim*
On Tue, Feb 19, 2019 at 11:01 AM Jonathan Mathews
wrote:
> Good Day
>
> I have been trying to upgrade a clients oVirt from 3.6 to 4.0 but have run
> into an issue where I am unable to change the cluster and data center
> compatibility version.
>
> I get the following error in the GUI:
>
> Ovirt: Some of the hosts still use legacy protocol which is not supported
> by cluster 3.6 or higher. In order to change it a host needs to be put to
> maintenance and edited in advanced options section.
>
> This error was received with all VM's off and all hosts in maintenance.
>
> The environment has the following currently installed:
>
> Engine - CentOS 7.4 - Ovirt Engine 3.6.7.5
> Host1 - CentOS 6.9 - VDSM 4.16.30
> Host2 - CentOS 6.9 - VDSM 4.16.30
> Host3 - CentOS 6.9 - VDSM 4.16.30
>
> I also have the following from engine.log
>
> [root@ovengine ~]# tail -f /var/log/ovirt-engine/engine.log
> 2018-09-22 07:11:33,920 INFO
> [org.ovirt.engine.core.vdsbroker.VmsStatisticsFetcher]
> (DefaultQuartzScheduler_Worker-93) [7533985f] Fetched 0 VMs from VDS
> 'd82a026c-31b4-4efc-8567-c4a6bdcaa826'
> 2018-09-22 07:11:34,685 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand]
> (DefaultQuartzScheduler_Worker-99) [4b7e3710] FINISH,
> DisconnectStoragePoolVDSCommand, log id: 1ae6f0a9
> 2018-09-22 07:11:34,687 INFO
> [org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand]
> (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] Running command:
> DisconnectHostFromStoragePoolServersCommand internal: true. Entities
> affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool
> 2018-09-22 07:11:34,706 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand]
> (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] START,
> DisconnectStorageServerVDSCommand(HostName = ovhost3,
> StorageServerConnectionManagementVDSParameters:{runAsync='true',
> hostId='d82a026c-31b4-4efc-8567-c4a6bdcaa826',
> storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageType='NFS',
> connectionList='[StorageServerConnections:{id='3fdffb4c-250b-4a4e-b914-e0da1243550e',
> connection='172.16.0.10:/raid0/data/_NAS_NFS_Exports_/STORAGE1',
> iqn='null', vfsType='null', mountOptions='null', nfsVersion='null',
> nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'},
> StorageServerConnections:{id='4d95c8ca-435a-4e44-86a5-bc7f3a0cd606',
> connection='172.16.0.20:/data/ov-export', iqn='null', vfsType='null',
> mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null',
> iface='null', netIfaceName='null'},
> StorageServerConnections:{id='82ecbc89-bdf3-4597-9a93-b16f3a6ac117',
> connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/4TB', iqn='null',
> vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null',
> nfsTimeo='null', iface='null', netIfaceName='null'},
> StorageServerConnections:{id='29bb3394-fb61-41c0-bb5a-1fa693ec2fe2',
> connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/iso', iqn='null',
> vfsType='null', mountOptions='null', nfsVersion='V3', nfsRetrans='null',
> nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log id: 48c5ffd6
> 2018-09-22 07:11:34,991 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand]
> (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] FINISH,
> DisconnectStorageServerVDSCommand, return:
> {3fdffb4c-250b-4a4e-b914-e0da1243550e=0,
> 29bb3394-fb61-41c0-bb5a-1fa693ec2fe2=0,
> 82ecbc89-bdf3-4597-9a93-b16f3a6ac117=0,
> 4d95c8ca-435a-4e44-86a5-bc7f3a0cd606=0}, log id: 48c5ffd6
> 2018-09-22 07:11:56,367 WARN
> [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-29)
> [1a31cc53] CanDoAction of action 'UpdateVdsGroup' failed for user
> admin@internal. Reasons:
> VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION
> 2018-09-22 07:12:41,017 WARN
> [org.ovirt.engine.core.bll.storage.UpdateStoragePoolCommand] (default
> task-29) [efd285b] CanDoAction of action 'UpdateStoragePool' failed for
> user admin@internal. Reasons:
> VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList
> Default,ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS
> 2018-09-22 07:13:15,717 WARN
> [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-6)
> [4c9f3ee8] CanDoAction of action 'UpdateVdsGroup' failed for user
> admin@internal. Reasons:
> VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION
> 2018-09-22 07:15:21,460 WARN
> [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-28)
> [649bae65] CanDoAction of action 'UpdateVdsGroup' failed for user
> admin@internal. Reasons:
>
