feedc0de/my-rook-config
1
0
Fork 0
forked from rook/rook
Code Pull Requests Activity
Files
a52948e7f70d7e613cb038b67a96ccbfd9e4d7ae
my-rook-config/pkg
T
History
Travis Nielsen a52948e7f7 ceph: continue orchestration even if osd status update fails 
The communication between the operator and OSD prepare job
is done through updates to the configmap. If an update fails
to the configmap, we are anyway going to need to check the logs
for failure. So let's just log the error and make a best effort
to continue the orchestration. If the failure was temporary,
the next update to the status would succeed and likely continue
working as expected.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2020-03-05 14:08:58 -07:00
..
apis
ceph: Follow up for adding the state variable
2020-03-04 18:57:07 +05:30
client
crds: move supporting types from v1alpha2 to rook.io/v1
2020-02-26 11:18:17 -07:00
clusterd
ceph: osd store refactor
2020-01-23 19:13:09 +01:00
daemon
ceph: continue orchestration even if osd status update fails
2020-03-05 14:08:58 -07:00
operator
ceph: continue orchestration even if osd status update fails
2020-03-05 14:08:58 -07:00
test
mons: use the default port of 6789 instead of 6790
2019-01-17 14:37:58 -07:00
util
ceph: separate controller for CephBlockPool CRD
2020-03-02 17:31:03 +01:00
version
log version, arguments and flags at start up
2017-08-24 14:02:53 -07:00