Bug #49374
mgr/volumes: Bump up the AuthMetadataManager's version to 6
% Done:
0%
Source:
Tags:
Backport:
pacific,octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/volumes
Labels (FS):
Manila
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
With ceph_volume_client and mgr/volumes co-existing for sometime, the version of ceph_volume_client
and mgr-volume's AuthMetadataManager needs to be same. And with 'volumes' key changed to 'subvolumes'
in auth-metadata file, the version has to be bumped up from version 5 to version 6 to handle version
in compatibility.
Related issues
History
#1 Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Assignee set to Kotresh Hiremath Ravishankar
#2 Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Component(FS) mgr/volumes added
- Labels (FS) Manila added
#3 Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 39572
#4 Updated by Ramana Raja about 3 years ago
- Status changed from Fix Under Review to Pending Backport
#5 Updated by Backport Bot about 3 years ago
- Copied to Backport #49429: pacific: mgr/volumes: Bump up the AuthMetadataManager's version to 6 added
#6 Updated by Backport Bot about 3 years ago
- Copied to Backport #49430: nautilus: mgr/volumes: Bump up the AuthMetadataManager's version to 6 added
#7 Updated by Backport Bot about 3 years ago
- Copied to Backport #49431: octopus: mgr/volumes: Bump up the AuthMetadataManager's version to 6 added
#8 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".