Description of problem: see bz#1145188 for more description. When executing a live snapshot, vdsm creates a RAM snapshot of our VM along with a configuration image, those images should be wiped out when removing the last (data) snapshot volume that was associated with that snapshot (from snapshot overview). Version-Release number of selected component (if applicable): vt8 How reproducible: 100% Steps to Reproduce: 1.have a live snapshot 2.delete the snapshot one by one via snapshot-overview Actual results: deleting the last volume that belongs to a live snapshot doesn't prompt RAM & conf snapshots deletion Expected results: RAM & conf snapshots are unusable when not having storage, thus, need to be wiped out with the last volume Additional info:
VM configuration, memory and disks are all separate components of a snapshot. A snapshot with VM configuration or memory only could still be usable in some use-cases (e.g. taking a snapshot in live-cd mode). Hence, I don't think there's a special issue to address here. @Allon - what do you think?
(In reply to Daniel Erez from comment #1) > VM configuration, memory and disks are all separate components of a > snapshot. A snapshot with VM configuration or memory only could still be > usable in some use-cases (e.g. taking a snapshot in live-cd mode). > Hence, I don't think there's a special issue to address here. > > @Allon - what do you think? Indeed, this is not a bug - not only is there merit in keeping this snapshots, you can also /explicitly/ ask to create one.