Project

General

Profile

Actions
Copy link

Bug #44756

closed

drivegroups: replacement op will ignore existing wal/dbs

Added by Joshua Schmid about 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
cephadm/osd
Target version:
Ceph - v15.0.0
% Done:

0%

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

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 2 (1 open — 1 closed)

Related to ceph-volume - Bug #44749: lvm batch does not re-use db devices with free space on VGsResolved

Actions
Related to ceph-volume - Feature #44750: improve output in the 'rejected reason' fieldNew

Actions
Actions
Copy link
 #1

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
Actions
Copy link
 #2

Updated by Joshua Schmid about 4 years ago

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

Updated by Joshua Schmid almost 4 years ago

  • Status changed from New to In Progress
  • Pull request ID set to 34740
Actions
Copy link
 #4

Updated by Sebastian Wagner over 3 years ago

  • Category changed from cephadm to cephadm/osd
Actions
Copy link
 #5

Updated by Sebastian Wagner over 3 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF