Skip to content

List Ceph daemon crash reports — bootstrap-admin.

GET
/v1/admin/storage/ceph/crashes
Code sample: Shell / cURL
curl --request GET \
--url https://stratum.example.com/v1/admin/storage/ceph/crashes \
--header 'Authorization: Bearer <token>'

Daemon crash reports (ceph crash ls): id, entity, timestamp. Install-scope; gates on storage:ListCephCrashes.

Crash reports.

Media typeapplication/json
object
items
Array<object>

A Ceph daemon crash report.

object
id
string
entity

Daemon that crashed, e.g. osd.3.

string
timestamp
string
archived

When an operator acknowledged this crash. Absent while it is still unacknowledged — and an unacknowledged crash is not history, it is an open question: Ceph holds the cluster in HEALTH_WARN via RECENT_CRASH until every crash is archived.

string
host

Host the daemon was running on.

string
cephVersion

Ceph version the daemon was running, so a crash can be told apart from one that predates an upgrade.

string
processName

The binary that crashed (ceph-osd, ceph-mon). Distinct from entity: entity is the daemon’s cluster identity, this is what actually died, and on an unnamed crash it is all there is.

string
stackSig

Ceph’s hash of the stack — the recurrence key. Two crashes sharing a signature are the same bug hitting twice, which is the difference between “a known upstream issue” and “this node is failing”.

string
assertMsg

The assertion text, present only for assertion failures. A segfault has none, so its absence is information rather than a gap.

string
backtrace

The stack as Ceph recorded it, one frame per entry — the field that lets an operator judge a crash rather than only see that one happened.

Carried inline rather than behind a per-crash detail endpoint because ceph crash ls already returns it: a detail endpoint would re-fetch bytes the list call already had. Roughly 1 KB per crash on a real report.

Array<string>
cluster

Present when there is no Ceph cluster to read (not set up, bootstrapping, a failed bootstrap, torn down): the reconciler’s observed state, and the list is then empty (the pool list holds the desired pools). Absent on a live answer. Before Ceph exists these reads answer 200 with it, never 503; 503 means a cluster that exists did not answer.

object
fsid
string
phase
required
string
Allowed values: unconfigured bootstrapping ready degraded error tearing-down
health
string
message
string
reportedAt
string format: date-time
reportedBy

The control plane (node id) that wrote this status.

string
rgwDaemonsRunning

The radosgw daemons the reconciler observed running at its last probe. Absent when not observed (no cluster answered, or the gateway listing failed): unknown, not zero.

integer

Example

{
"cluster": {
"phase": "unconfigured"
}
}

Authenticated but not authorized.

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example

{
"issues": [
{
"code": "ACTION_NOT_APPLICABLE",
"action": "compute:CreateVpc"
}
]
}

Upstream temporarily unavailable (driver / scheduler / dependency).

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example

{
"issues": [
{
"code": "ACTION_NOT_APPLICABLE",
"action": "compute:CreateVpc"
}
]
}