dfd8f99743
Consider volume and snapshots as below:
v1
|
`-- s1
|
`-- v2
|
`-- s2
User initiated deletion of snapshot s1.
It failed with some vague message.
Initially, it was suspected that ...
While copying volume v2 (sometimes an intermediate step to break
volume dependency), we send a request to clone the volume v2 to new
base volume; and the exception [1] isn't handled properly.
[1] Conflict (HTTP 409) 32 - volume has a child
However, on further investigation it was found that ...
after a new volume v2 (omv-<id>) is created and
when we try to delete old volume v2 (osv-<id>),
at this point the exception [1] is thrown as error.
This is now handled gracefully. Appropriate error is thrown
if the volume (v2) has snapshot (s2).
Co-Authored-By: raghavendrat <raghavendra-uddhav.tilay@hpe.com>
Closes-Bug: #1994521
Change-Id: I5e7fb425c92cdf8c16d5a86a58ca1a52421543d7
12 lines
522 B
YAML
12 lines
522 B
YAML
---
|
|
fixes:
|
|
- |
|
|
HPE 3PAR driver `Bug #1994521 <https://bugs.launchpad.net/cinder/+bug/1994521>`_:
|
|
Fixed: While performing a delete snapshot (s1) operation, the volumes (v2)
|
|
dependent on the snapshot (s1) are converted to base volumes. This
|
|
operation fails if these dependent volumes (v2) have their own dependent
|
|
snapshots (s2). The errors during the failure were vague and not helpful.
|
|
With this release, we added conditions to fail this operation early and
|
|
also added useful error message.
|
|
|