+++ This bug was initially created as a clone of Bug #2005221 +++

Hi
we are unable to do the cluster compatibility version upgrade from 4.5 to 4.6 because it can't change the compatibility for the HostedEngine vm:

from engine.log
2021-09-01 15:37:17,271+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [28a98510] EVENT_ID: CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Cannot update compatibility version of Vm/Template: [HostedEngine], Message: [No Message]
2021-09-01 15:37:17,457+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [28a98510] EVENT_ID: USER_UPDATE_CLUSTER_FAILED(812), Failed to update Host cluster (User: admin@internal-authz)

from web ui:
Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: HostedEngine. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change (or other changes). If the problem still persists, you may refer to the engine.log file for further details.

Thank you in advance!

Lorenzo

--- Additional comment from RHEL Program Management on 2021-09-17 09:52:08 CEST ---

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

--- Additional comment from Martin Perina on 2021-09-17 14:35:25 CEST ---

Could you please provide complete logs from your engine machine gathered by sos-logcollector?

--- Additional comment from Lorenzo Sartoratti on 2021-09-17 15:25:35 CEST ---

Hi,
could you be more specific in the files to provide? sos-collector collects too much information and even through the clean function I cannot check all sensitive information.
Thanks

Lorenzo

--- Additional comment from Martin Perina on 2021-09-17 15:34:42 CEST ---

(In reply to Lorenzo Sartoratti from comment #3)
> Hi,
> could you be more specific in the files to provide? sos-collector collects
> too much information and even through the clean function I cannot check all
> sensitive information.
> Thanks
> 
> Lorenzo

We ask for sos-logcollector, because then we can investigate thoroughly what happened.

If you don't want to share all logs, then please share engine.log and server.log and let's see what we can find.

Thanks

--- Additional comment from Lorenzo Sartoratti on 2021-09-17 16:01:30 CEST ---

Hi,
steps done:
logrotate -f
launched compatibility update

server.log is an empty file
engine.log non empty file (attaching)

Lorenzo

--- Additional comment from Martin Perina on 2021-09-20 10:06:40 CEST ---

Please don't use logrotate to rotate logs file generated by WildFly (server.log/engine.log/ui.log under /var/log/ovirt-engine). Doing that you might loose logged data and even WildFly might not work correctly.

To fix that issue I suggest to restart ovirt-engine service.

So anyway if you have any older engine.log files, could you please share them?

--- Additional comment from Fabio Futigami on 2021-09-20 16:24:01 CEST ---

Hi, I have a customer from case 03036833 with the same issue. It seems we have all the logs (engine.log and server.log). Is there anything we can provide to assist in this bugzilla?