Travis Nielsen add3129c12 ceph: continue orchestration on osd update errors ...

During an orchestration if there were failures to update any OSD deployment,
the orchestration would fail and continue trying again. If the OSD(s)
continued failing, the operator would be stuck in a loop and never
respond to other CR updates.

Now the operator will log the OSD errors, if any, and complete the
orchestration. We will rely on K8s to continue to attempt to start
the OSD pods instead of the operator being stuck in the loop.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

2019-12-03 19:16:48 -07:00

..

cassandra

crds: Set annotations pods, deployments and so on

2019-04-16 20:47:05 +02:00

ceph

ceph: continue orchestration on osd update errors

2019-12-03 19:16:48 -07:00

cockroachdb

ownerrefs: set owners based on name instead of namespace

2019-10-14 09:29:45 -06:00

discover

ceph: added priority classes to components

2019-11-15 16:28:41 -06:00

edgefs

edgefs: Additional ISGW configuration

2019-11-11 11:04:14 -08:00

k8sutil

k8sutil: cmdreporter: properly set app name

2019-11-14 15:50:26 -07:00

minio

ownerrefs: set owners based on name instead of namespace

2019-10-14 09:29:45 -06:00

nfs

nfs: set correct owner reference name for garbage collection

2019-10-24 14:24:45 -06:00

test

Ceph: Add unit tests for nfs-ganesha spec

2019-07-22 11:06:04 -06:00

yugabytedb

ownerrefs: set owners based on name instead of namespace

2019-10-14 09:29:45 -06:00