The failure/recovery flow for Live Merge has gaps in its effectiveness to successfully detect failures and write the database records in such a way as to make Live Merge succeed upon retry without manual fixup.
For one example, see bug 1227497 and bug 1302215 - the fix here helps avoid failure from vdsm not being able to report the status of DestroyImageCommand, but may still fail if the SPM is unavailable during the verification.
This bug is for investigating a more thorough, long-term fix wherein the Live Merge failure flow is made more predicable and (we hope) simplified.
This is a dedicated research task that should be examined together with the refactoring efforts of 4.0.
When specific items are discovered (e.g., the aforementioned bug 1227497 and bug 1302215), their targeting should be discussed individually.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Do you think there is still any action items on this?
Not for the short term
Moving to ON_QA based on this assessment.
Ala, I'm pretty any doctext requirements are handled by the dependent bugs, just wanted to verify this though - please keep me honest here.
Actually, doctext requirements are handled in BZ 1323629, which is dedicated for LM recovery documentation
anything to test here? is it tracker only?
(In reply to Ala Hino from comment #11)
> A tracker
Can you add all the BZs it's supposed to track? I see just two bugs (BZ#1227497 and BZ#1302215, which were handled in 3.6.3), but I know you did a bunch of work in 3.6.5 and 3.6.6.
Verified that there is no action item on this bz. This is only a tracker