Bug #49294
pacific: pybind/ceph_volume_client: volume authorize/deauthorize crashes with 'volume' key not found
% Done:
0%
Source:
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
VolumeClient
Labels (FS):
Manila
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Note the ceph_volume_client is deprecated in master and available in pacific/octopus/nautilus. Hence raised against pacific and backport targeted to octopus, nautilus
With mgr/volumes, auth-metadata file stores the subvolume meta data with 'subvolume' key. If ceph_volume_client is used
to operate on the same subvolume, it would crash with 'volume' key not found. The ceph_volume_client needs to handle this
and use 'subvolumes' key and update the 'volumes' key to 'subvolumes'.
Related issues
History
#1 Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 39480
#2 Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Description updated (diff)
#3 Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Description updated (diff)
#4 Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Copied to Backport #49447: nautilus: pybind/ceph_volume_client: volume authorize/deauthorize crashes with 'volume' key not found added
#5 Updated by Nathan Cutler about 3 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport changed from octopus,nautilus to pacific,octopus,nautilus
#6 Updated by Nathan Cutler about 3 years ago
- Copied to Backport #49508: octopus: pybind/ceph_volume_client: volume authorize/deauthorize crashes with 'volume' key not found added
#8 Updated by Nathan Cutler about 3 years ago
- Backport changed from pacific,octopus,nautilus to octopus,nautilus
#9 Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".