From bc6381169ee99815e8fd2507ccce367cf2e34213 Mon Sep 17 00:00:00 2001 From: Travis Nielsen Date: Thu, 3 Mar 2022 14:36:27 -0700 Subject: [PATCH] core: disruption controller log ceph errors in debug level The controller for disruption budgets is verbose at cluster creation when the cluster is not yet created, which generates a lot of noise in the log that makes the cluster look unhealthy. This is an expected condition, so we can change this logging to debug level. Signed-off-by: Travis Nielsen --- pkg/operator/ceph/disruption/clusterdisruption/osd.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/pkg/operator/ceph/disruption/clusterdisruption/osd.go b/pkg/operator/ceph/disruption/clusterdisruption/osd.go index 563591306..2fb2dd0f5 100644 --- a/pkg/operator/ceph/disruption/clusterdisruption/osd.go +++ b/pkg/operator/ceph/disruption/clusterdisruption/osd.go @@ -329,10 +329,11 @@ func (r *ReconcileClusterDisruption) reconcilePDBsForOSDs( // If the error contains that message, this means the cluster is not up and running // No monitors are present and thus no ceph configuration has been created if strings.Contains(err.Error(), opcontroller.UninitializedCephConfigError) { - logger.Infof("Ceph %q cluster not ready, cannot check Ceph status yet.", request.Namespace) + logger.Debugf("ceph %q cluster not ready, cannot check status yet.", request.Namespace) return opcontroller.WaitForRequeueIfOperatorNotInitialized, nil } - return reconcile.Result{}, errors.Wrapf(err, "failed to check cluster health") + logger.Debugf("ceph %q cluster failed to check cluster health. %v", request.Namespace, err) + return opcontroller.WaitForRequeueIfCephClusterNotReady, nil } switch {