Actions
Bug #44756
closeddrivegroups: replacement op will ignore existing wal/dbs
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Since the db/wal is considered "locked/non-avialable" by ceph-volume after the first deployment, the DriveGroup algorithm excludes it from further operations.
We would need a more descriptive label for wals and dbs similar to as requested here: https://tracker.ceph.com/issues/44750
Also, if a db_device field is specified in the drivegroup specs, but the lookup doesn't find a valid db/wal device the deployment should be considered failed
If that works, we're still hitting https://tracker.ceph.com/issues/44749
Updated by Joshua Schmid about 4 years ago
- Related to Bug #44749: lvm batch does not re-use db devices with free space on VGs added
Updated by Joshua Schmid about 4 years ago
- Related to Feature #44750: improve output in the 'rejected reason' field added
Updated by Joshua Schmid almost 4 years ago
- Status changed from New to In Progress
- Pull request ID set to 34740
fixed with https://github.com/ceph/ceph/pull/34740
Updated by Sebastian Wagner almost 4 years ago
- Category changed from cephadm to cephadm/osd
Updated by Sebastian Wagner over 3 years ago
- Status changed from In Progress to Resolved
Actions