Description of problem:
Discovered while investigating bug 1302215, the master branch code doesn't update the database properly when Live Merge fails. The images with data merged into it should be illegal; however, it is left as OK. (I believe this is caused by something outside the immediate live merge code, but could be mistaken as I haven't investigated too deeply.)
This bz is to ensure we don't forget to fix/check this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run Live Merge
2. Make it fail
3. Notice the image in the snapshot is OK
Image is OK
Image is illegal
This bug does not reproduce on the 3.6.z branch, pushing out to 4.0, where it (of course) needs to be fixed.
(In reply to Allon Mureinik from comment #1)
> This bug does not reproduce on the 3.6.z branch, pushing out to 4.0, where
> it (of course) needs to be fixed.
Liron/Ala - based on recent conversations, I am not sure this statement is correct.
Could you either confirm or refute (in which case, this BZ probably needs to be retargeted to 3.6.3.*).
Allon, this bug is relevant to v4.0.
After a failed live merge, the snapshot disk (volume) is marked as illegal.
1caae771ff' images '94db6296-3480-40ff-a3eb-1f7f62e6ca1c'..'8dd4dbb2-7eba-42fe-b846-40036ad34869' merged, but volume removal failed. Some or all of the following volumes may be orphaned:
[94db6296-3480-40ff-a3eb-1f7f62e6ca1c]. Please retry Live Merge on the snapshot to complete the operation
<disk_snapshot href= "/ovirt-engine/api/storagedomains/6ba7f20b-4209-4909-b67f-a7590fa45081/disksnapshots/94db6296-3480-40ff-a3eb-1f7f62e6ca1c" id="94db6296-3480-40ff-a3eb-1f7f62e6ca1c">
oVirt 4.0.0 has been released, closing current release.