Project

General

Profile

Bug #44756

drivegroups: replacement op will ignore existing wal/dbs

Added by Joshua Schmid 6 months ago. Updated 2 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
cephadm/osd
Target version:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

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


Related issues

Related to ceph-volume - Bug #44749: lvm batch does not re-use db devices with free space on VGs New
Related to ceph-volume - Feature #44750: improve output in the 'rejected reason' field New

History

#1 Updated by Joshua Schmid 6 months ago

  • Related to Bug #44749: lvm batch does not re-use db devices with free space on VGs added

#2 Updated by Joshua Schmid 6 months ago

  • Related to Feature #44750: improve output in the 'rejected reason' field added

#3 Updated by Joshua Schmid 3 months ago

  • Status changed from New to In Progress
  • Pull request ID set to 34740

#4 Updated by Sebastian Wagner 2 months ago

  • Category changed from cephadm to cephadm/osd

Also available in: Atom PDF