my-rook-config

Files

T

Sébastien Han 88048cc4e8 ceph: do not check ok-to-stop when OSDs are in CLBO

This handles the scenario where the OSDs have been created but not yet
started due to a wrong CR configuration.
For instance, when OSDs are encrypted and Vault is used to store
encryption keys, if the KV version is incorrect during the cluster
initialization the OSDs will fail to start and stay in CLBO until the
CR is updated again with the correct KV version so that it can start.

For this scenario, if the CRUSH map has no host registered yet it's fair
to assume the initialization broke and we need to fix it. So when don't
need to call ok-to-stop since it will always fail and eventually force
pass but let's not wait for nothing.

Signed-off-by: Sébastien Han <seb@redhat.com>

2021-08-25 09:30:38 +02:00

apis

ceph: make storage device config nullable

2021-08-17 12:21:32 -06:00

client

build: refactor to consolidate the rook.io/v1 package

2021-05-18 19:55:37 -06:00

clusterd

ceph: remove old network types

2021-08-04 10:56:01 +02:00

daemon

ceph: do not check ok-to-stop when OSDs are in CLBO