Actions
Bug #44755
closedCreate stronger affinity between drivegroup specs and osd daemons
% Done:
0%
Source:
Development
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
We currently only show the name of the drivegroup spec in `orch ls`
#ceph orch ls NAME RUNNING REFRESHED AGE PLACEMENT IMAGE NAME IMAGE ID osd.test_dg 0/1 - - cephadm-dev <unknown> <unknown>
which isn't able to correctly display the associated osds.
ServiceDescription to track the "service" -> osd.drivegroup_name
DaemonDescription to track the "daemons" -> osd.0
This also allows to track osd if more than one drivegroup per node is applied.
Updated by Joshua Schmid about 4 years ago
- Blocks Bug #44888: Drivegroup's :limit: isn't working correctly added
Updated by Joshua Schmid about 4 years ago
- Status changed from New to In Progress
- Assignee set to Joshua Schmid
Updated by Joshua Schmid about 4 years ago
- Blocked by Feature #44929: Add support DG_AFFINITY env var parsing. added
Updated by Sebastian Wagner almost 4 years ago
- Related to Cleanup #46219: cephadm: remove DaemonDescription.service_id() added
Updated by Sebastian Wagner almost 4 years ago
- Status changed from In Progress to Pending Backport
- Backport set to octopus
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46372: osd: expose osdspec_affinity to osd_metadata added
Updated by Nathan Cutler almost 4 years ago
- Project changed from Orchestrator to RADOS
- Category deleted (
cephadm)
Moving to RADOS project so it can be backported in the usual way.
Updated by Nathan Cutler over 3 years ago
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Nathan Cutler over 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".
Actions