Actions
Bug #6824
closedRemoval of an OSD that is not down should set non-successful status code
% Done:
0%
Source:
Support
Tags:
Backport:
Dumpling
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
A customer reports that some ceph commands return a status code of 0, even when they failed. The provided example was for removing an OSD that is still up (ceph osd rm). ceph will even return successful when a non-valid OSD id is provided.
An audit should be considered for other ceph sub-commands to ensure that status codes are standardized and accurate.
Updated by Loïc Dachary over 10 years ago
- Status changed from New to 12
- Assignee set to Loïc Dachary
Updated by Loïc Dachary over 10 years ago
- Category changed from ceph cli to Monitor
- Status changed from 12 to Fix Under Review
Updated by Loïc Dachary over 10 years ago
- Status changed from Fix Under Review to Resolved
Updated by Ian Colle over 10 years ago
- Status changed from Resolved to Pending Backport
- Assignee changed from Loïc Dachary to Joao Eduardo Luis
- Backport set to Dumpling
Updated by Sage Weil over 10 years ago
- Status changed from Pending Backport to Resolved
Updated by Greg Farnum over 10 years ago
I missed this when it was going by, but it looks like that patch makes things like "osd down" and "osd out" no longer idempotent?
Actions