Actions
Bug #44755
closedCreate stronger affinity between drivegroup specs and osd daemons
% Done:
0%
Source:
Development
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v16.0.0-2690-g9a8b4fd6b7
Released In:
v16.2.0~2243
Upkeep Timestamp:
2025-07-15T01:17:07+00:00
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 almost 6 years ago
- Blocks Bug #44888: Drivegroup's :limit: isn't working correctly added
Updated by Joshua Schmid almost 6 years ago
- Status changed from New to In Progress
- Assignee set to Joshua Schmid
Updated by Joshua Schmid almost 6 years ago
- Blocked by Feature #44929: Add support DG_AFFINITY env var parsing. added
Updated by Sebastian Wagner over 5 years ago
- Related to Cleanup #46219: cephadm: remove DaemonDescription.service_id() added
Updated by Sebastian Wagner over 5 years ago
- Status changed from In Progress to Pending Backport
- Backport set to octopus
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #46372: osd: expose osdspec_affinity to osd_metadata added
Updated by Nathan Cutler over 5 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 5 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 5 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".
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 9a8b4fd6b7b4ae219d9a7829ed7ab3bfc097eb10
- Fixed In set to v16.0.0-2690-g9a8b4fd6b7
- Released In set to v16.2.0~2243
- Upkeep Timestamp set to 2025-07-15T01:17:07+00:00
Actions