Description of problem: A storage read or write error when modifying storage domain metadata may leave storage domain metadata in inconsistent state. There are 2 issues: - Read error may leave metadata object in transaction state. After that no data will be written to storage until the storage domain is refreshed (usually every 5 minutes). - Write error does not rollback the changes, so the metadata keeps values modified during a transaction, while state on storage was not modified. Both issues can cause different hosts to see different metadata at the same time. I don't know if how to reproduce this with the real system, but it is easy to reproduce in vdsm automated tests when we can inject both read and write errors. Version-Release number of selected component (if applicable): Any How reproducible: Always in vdsm tests, should be very hard in real system. Steps to Reproduce: Inject read or write errors when accessing storage domain metadata.
Hi Nir, As this is already verified on vdsm tests and there is no real system scenario, can you please verify this bug?
Verified in VDSM test as it is (almost) impossible to reproduce in a running system
This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.