Project

General

Profile

Actions
Copy link

Bug #58626

closed

limit filter in python-common/ceph/deployment/drive_selection/selector.py not working when multiple osd service spec are deployed

Added by Guillaume Abrioux over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Guillaume Abrioux
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
backport_processed
Backport:
reef,quincy,pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
49969
Crash signature (v1):
Crash signature (v2):

Description

when trying to apply the following service specs, the second never get applied because the `limit` filter makes it try to pick devices that are already used by the first service spec:

---
service_type: osd
service_id: two_per_nvme
placement:
  label: osd
data_devices:
  size: '200GB:'
  limit: 3
db_devices:
  paths:
    - /dev/vdi
    - /dev/vdj
---
service_type: osd
service_id: three_per_nvme
placement:
  label: osd
data_devices:
  size: '200GB:'
  limit: 3
db_devices:
  paths:
    - /dev/vdk


Feb 01 13:04:30 osd-spec-limit-1 ceph-mgr[686547]: log_channel(cephadm) log [DBG] : skipping apply of osd-spec-limit-1 on DriveGroupSpec.from_json(yaml.safe_load('''service_type: osd
                                                   service_id: three_per_nvme
                                                   service_name: osd.three_per_nvme

Related issues 2 (0 open — 2 closed)

Copied to Orchestrator - Backport #58909: pacific: limit filter in python-common/ceph/deployment/drive_selection/selector.py not working when multiple osd service spec are deployedResolvedGuillaume AbriouxActions
Copied to Orchestrator - Backport #58910: quincy: limit filter in python-common/ceph/deployment/drive_selection/selector.py not working when multiple osd service spec are deployedResolvedGuillaume AbriouxActions
Actions
Copy link

Also available in: Atom PDF