Project

General

Profile

Actions
Copy link

Bug #6824

closed

Removal of an OSD that is not down should set non-successful status code

Added by Brian Andrus over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Joao Eduardo Luis
Category:
Monitor
Target version:
-
% 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.

Actions
Copy link
 #1

Updated by Loïc Dachary over 10 years ago

  • Status changed from New to 12
  • Assignee set to Loïc Dachary
Actions
Copy link
 #2

Updated by Loïc Dachary over 10 years ago

  • Category changed from ceph cli to Monitor
  • Status changed from 12 to Fix Under Review
Actions
Copy link
 #3

Updated by Loïc Dachary over 10 years ago

  • Status changed from Fix Under Review to Resolved
Actions
Copy link
 #4

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

Updated by Ian Colle over 10 years ago

Request to backport fix to Dumpling.

Actions
Copy link
 #6

Updated by Sage Weil over 10 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link
 #7

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
Copy link

Also available in: Atom PDF