Description of problem:
A live merge completed on the host, but not on the engine. The engine was just waiting on the merge to complete, and after two days the operation was terminated, and "failed".
There were no obvious communication issues between the engine and the host. The host was not non-responsive and there were no connection or heartbeat timeouts, etc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Engine never realised the merge had completed on the host.
Engine should have realised the merge had completed on the host and continued with the next steps.
Any chance we have a `virsh dumpxml` type of output for the VM 'fbf06769-2808-4471-812c-8f04464a391b'?
No, unfortunately we don't. The VM was shutdown before the customer contacted us.
That's a shame, as it is unclear why engine thought the job was still running? Is there anything in the vm_jobs table?
I know there was a bug a while ago where there was a sync issue between the vm xml and the internal vdsm configuration stored which affected live merge as well.
I'll try to find it, but I think it happened when using engine 4.2 and a 4.1 cluster (because DomainXML was introduced in 4.2), is that the case here?
Liran, will the async snapshot resolve this from the virt side?
Unfortunately, it's irreverent to async snapshot.
Benny, do we have a clear verification scenario on this one?
(In reply to Avihai from comment #30)
> Benny, do we have a clear verification scenario on this one?
Created attachment 1700308 [details]
After discussing this bug today again with the storage team, we decided to close this Insufficient Data.
If you would like to reopen it, please provide reproducer steps or output from the script provided by engineering earlier here in comment#35 and reproducibe on RHV 4.4, currently supported version.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (RHV Manager (ovirt-engine) [ovirt-4.4.8]), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.