Description of problem: As a result of bz 1427104 or bz 1422949, we can get to a state where there are 2 active snapshots on the same disk. This situation will not happen after the fix from above bug. However, in order to fix the existing VMs with this issue we need manual steps to update the DB and clean the storage Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to Fred Rolland from comment #0) > Description of problem: > > As a result of bz 1427104 or bz 1422949, we can get to a state where there > are 2 active snapshots on the same disk. With these two bugs fixed in 4.1.z, such a situation shouldn't happen, and there's no need for the engine to "generically" handle it. We should provide a manual procedure to users that were affected by this bug in earlier versions to recover from it.
We haven't seen any request for this in the field, closing. If the interest arises, we can reopen.