Description of problem: If a snapshot is removed by "rbd snap rm --force" and is used by at least one cloned image that does *not* have the deep-flatten feature enabled and the clone has snapshots, the snapshot will be deleted and the clone's snapshot will most likely be corrupt since the parent image's snapshot has been deleted. Version-Release number of selected component (if applicable): 12.2.x How reproducible: 100% Steps to Reproduce: 1. create a clone w/ deep-flatten disabled 2. create a snapshot within the clone 3. use "rbd snap rm --force <parent-snap-spec>" Actual results: The parent snapshot will be removed while the clone's snapshot still references the parent snapshot. Expected results: The force removal should be prohibited if deep-flatten isn't enabled on child images w/ snapshots.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1259