Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a VM with a regular disk (either block or file), and a cinder disk 2. Take a snapshot of both disks - s1 3. Take a second snapshot of only the regular disk - s2 Actual results: Multiple problems occur: The cinder disk in the first snapshot appears illegal, the active snapshot only contains the cinder disk. According to the DB, the cinder snapshot is part of s2 and no longer a part of s1. This has additional side effects, such as removing the snapshot s2 will also remove cinder disk Expected results: s1 should contain the cinder disk and the regular disk s2 should contain only the regular disk and the active snapshot should contain both without the additional side-effects Additional info:
Performed scenario described in comment 0. * First snapshot contains the cinder disk and the regular disk. * Second snapshot contains only the regular disk. Cinder disk id was: 7b81c8b5-7f75-4560-9f0b-b193316ca558 Cinder disk snapshot id (s1) was: cc84dcae-5e60-4782-ab2a-1b2eec858b2c When looking at the active vm: Status Up Alias cinder_disk Virtual Size 5 GiB Actual Size < 1 GiB Allocation Policy Unassigned Interface N/A Creation Date Apr 23, 2018, 9:34:26 PM Disk Snapshot ID 7b81c8b5-7f75-4560-9f0b-b193316ca558 <-- HERE Type CINDER Description N/A It shows the original cinder disk id, I expected to see the first snapshot id: cc84dcae-5e60-4782-ab2a-1b2eec858b2c Benny, is this part of the fix? or another bug?
This is the expected behavior: In Cinder we always write to the "active image" and snapshots are created separately, unlike in regular images where when creating a snapshot we take the current active image and create a new "active image" Daniel, can you confirm?
(In reply to Benny Zlotnik from comment #2) > This is the expected behavior: In Cinder we always write to the "active > image" and snapshots are created separately, unlike in regular images where > when creating a snapshot we take the current active image and create a new > "active image" > > Daniel, can you confirm? Indeed, the id shouldn't change as we keep the active layer intact for cinder disks when creating snapshots.
Verified (including delete snapshot operations), used builds: rhvm-4.2.3.2-0.1.el7.noarch vdsm-4.20.26-1.el7ev.x86_64
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.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.