Bug #46237: cephadm: Inconsistent exit code - Orchestrator - Ceph

Actions

Copy link

Bug #46237

closed

cephadm: Inconsistent exit code

Added by Ricardo Marques almost 4 years ago. Updated over 3 years ago.

Status:

Won't Fix

Priority:

Low

Assignee:

Category:

cephadm

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

If SSH keys are not available, then `ceph orch status` return code is zero:

master:~ # ceph orch status
Backend: cephadm
Available: False (SSH keys not set. Use `ceph cephadm set-priv-key` and `ceph cephadm set-pub-key` or `ceph cephadm generate-key`)
master:~ # echo $?
0

but if no backend is specified, then the exit code is non zero:

master:~ # ceph orch set backend ''
master:~ # ceph orch status
Error ENOENT: No orchestrator configured (try `ceph orch set backend`)
master:~ # echo $?
2

Shouldn't the exit codes be more consistent here?

Related issues 1 (0 open — 1 closed)