Bug 1317636
| Summary: | [RFE] Deep Flattening | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Federico Lucifredi <flucifre> | |
| Component: | RBD | Assignee: | Jason Dillaman <jdillama> | |
| Status: | CLOSED ERRATA | QA Contact: | Tanay Ganguly <tganguly> | |
| Severity: | medium | Docs Contact: | Bara Ancincova <bancinco> | |
| Priority: | unspecified | |||
| Version: | 1.3.2 | CC: | ceph-eng-bugs, hnallurv, jdillama, kdreyer, kurs | |
| Target Milestone: | rc | Keywords: | FutureFeature | |
| Target Release: | 2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
.The `deep flatten` feature has been added
Without the `deep flatten` feature, it is not possible to dissociate a clone from its parent if the clone has any snapshots. As a consequence, the parent image or snapshot cannot be deleted. With `deep flatten` enabled, it is possible to dissociate a clone from its parent and to delete no longer needed snapshots.
The `deep flatten` feature must be enabled when creating an image. It is not possible to enable it on already existing images.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1343424 (view as bug list) | Environment: | ||
| Last Closed: | 2016-08-23 19:34:25 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1322504, 1343424 | |||
|
Description
Federico Lucifredi
2016-03-14 17:47:32 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions Marking it as Verified. 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-2016:1755 |