Ceph device inventory with reject reasons — bootstrap-admin.

GET

/v1/admin/storage/ceph/devices

Code sample: Shell / cURL

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

• A Stratum cluster endpoint.

Cephadm’s per-host device inventory (ceph orch device ls). The reject reasons answer “why won’t my disk become an OSD” — “LVM detected” means in-use by an existing OSD (expected on a converged cluster); “No such file or directory” or “Insufficient space” are real provisioning problems. Install-scope; gates on storage:ListCephDevices.

Authorizations

• bearerAuth

Responses

200

Devices across all cluster hosts.

Media typeapplication/json

object

items

Array<object>

One physical device in cephadm’s inventory. rejectReasons explains a non-available disk — “LVM detected” = consumed by an existing OSD (expected); anything else is a real provisioning problem.

object

host

Hostname the device is attached to.

string

path

Device node path (e.g. /dev/nvme0n1).

string

model

string

sizeBytes

integer format: int64

available

Cephadm considers it consumable for a new OSD.

boolean

rejectReasons

Array<string>

osdIds

OSD id(s) currently backed by this device (empty when unconsumed).

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"
  }
}

403

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"
    }
  ]
}

503

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"
    }
  ]
}