Replies: 4 comments 1 reply
-
Stange. After error seams this initilization loop stopped
And now reporting only |
Beta Was this translation helpful? Give feedback.
-
🤔 seems the operator is still in the init loop. Still getting in logs these messages:
Seams every two minutes initialization is started |
Beta Was this translation helpful? Give feedback.
-
I'm seeing quite ugly error messages:
|
Beta Was this translation helpful? Give feedback.
-
The errors about "failed to update cluster condition" should not be causing the reconcile to restart. If the reconcile keeps restarting, I would expect some other error message to indicate why the reconcile was restarted. Can you attach a more complete log? What version of Rook is running? |
Beta Was this translation helpful? Give feedback.
-
Hello,
Today I booted up Kubernetes cluster with the rook ceph cluster and noticed that
rook-ceph-osd-prepare
,rook-ceph-detect-version
, and other containers appearing and disappearing. After checking operators logs I have noticed that it constantly checks for monitors, sets OSDs and etc.There is a fragment of the logs:
And while watching the pod I noticed that containers are coming up and down... Like Christmas tree
However, ceph status seams healthy
Is this behavior expected or I have managed to get in some cluster initialization loop? 🤔
Beta Was this translation helpful? Give feedback.
All reactions