Actions
Bug #9912
closedceph osd up # not a valid command in 0.80.7
Status:
Won't Fix
Priority:
Urgent
Assignee:
-
Category:
ceph cli
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
There is a valid command for setting an osd down:
regression@plana15:/tmp$ ceph osd down 17 osd.17 is already down.
But in a recent firefly build (0.80.7-74-g0975ec9) there does not appear to be a corresponding up command:
regression@plana15:/tmp$ ceph osd up 17
no valid command found; 10 closest matches:
osd tier add <poolname> <poolname> {--force-nonempty}
osd tier remove <poolname> <poolname>
osd reweight-by-utilization {<int[100-]>}
osd thrash <int[0-]>
osd pool get-quota <poolname>
osd pool stats {<name>}
osd pool set <poolname> size|min_size|crash_replay_interval|pg_num|pgp_num|crush_ruleset|hashpspool|hit_set_type|hit_set_period|hit_set_count|hit_set_fpp|debug_fake_ec_pool|target_max_bytes|target_max_objects|cache_target_dirty_ratio|cache_target_full_ratio|cache_min_flush_age|cache_min_evict_age|auid <val> {--yes-i-really-mean-it}
osd pool set-quota <poolname> max_objects|max_bytes <val>
osd pool rename <poolname> <poolname>
osd pool get <poolname> size|min_size|crash_replay_interval|pg_num|pgp_num|crush_ruleset|hit_set_type|hit_set_period|hit_set_count|hit_set_fpp|auid|target_max_objects|target_max_bytes|cache_target_dirty_ratio|cache_target_full_ratio|cache_min_flush_age|cache_min_evict_age|erasure_code_profile
Error EINVAL: invalid command
Updated by Sage Weil over 9 years ago
- Status changed from New to Won't Fix
there is no way to administratively make an osd 'up'. the daemon needs to go through it's startup procedure and join the cluster for this to happen. normally it'll do this on it's own when you start it or when you mark it down explicitly (and it notices)
Actions