Details
-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
4.10.z
-
None
-
Important
-
Rejected
-
False
-
Description
Description of problem:
Red Hat OpenShift distributed tracing data collection keeps reinstalling in OCP 4.10 cluster After every couple of minutes messages like below are seen in the OLM operator pod logs and the reinstall starts. The reinstall completes successfully in a few seconds. However, the reinstall starts again in some time and it keeps repeating. Uninstalling and installing the operator back didn't help. time="2022-09-15T08:47:05Z" level=warning msg="unhealthy component: waiting for deployment opentelemetry-operator-controller-manager to become ready: deployment \"opentelemetry-operator-controller-manager\" not available: Deployment does not have minimum availability." csv=opentelemetry-operator.v0.56.0-1 id=vFOjy namespace=openshift-operators phase=Succeeded strategy=deployment I0915 08:47:05.826465 1 event.go:282] Event(v1.ObjectReference{Kind:"ClusterServiceVersion", Namespace:"openshift-operators", Name:"opentelemetry-operator.v0.56.0-1", UID:"cae3195d-7d0a-4aa4-ba79-d8869e5f5888", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"875049442", FieldPath:""}): type: 'Warning' reason: 'ComponentUnhealthy' installing: waiting for deployment opentelemetry-operator-controller-manager to become ready: deployment "opentelemetry-operator-controller-manager" not available: Deployment does not have minimum availability. time="2022-09-15T08:47:06Z" level=warning msg="needs reinstall: waiting for deployment opentelemetry-operator-controller-manager to become ready: deployment \"opentelemetry-operator-controller-manager\" not available: Deployment does not have minimum availability." csv=opentelemetry-operator.v0.56.0-1 id=SEDcP namespace=openshift-operators phase=Failed strategy=deployment I0915 08:47:06.156419 1 event.go:282] Event(v1.ObjectReference{Kind:"ClusterServiceVersion", Namespace:"openshift-operators", Name:"opentelemetry-operator.v0.56.0-1", UID:"cae3195d-7d0a-4aa4-ba79-d8869e5f5888", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"875061474", FieldPath:""}): type: 'Normal' reason: 'NeedsReinstall' installing: waiting for deployment opentelemetry-operator-controller-manager to become ready: deployment "opentelemetry-operator-controller-manager" not available: Deployment does not have minimum availability. time="2022-09-15T08:47:06Z" level=info msg="scheduling ClusterServiceVersion for install" csv=opentelemetry-operator.v0.56.0-1 id=rgB1a namespace=openshift-operators phase=Pending I0915 08:47:06.367057 1 event.go:282] Event(v1.ObjectReference{Kind:"ClusterServiceVersion", Namespace:"openshift-operators", Name:"opentelemetry-operator.v0.56.0-1", UID:"cae3195d-7d0a-4aa4-ba79-d8869e5f5888", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"875061502", FieldPath:""}): type: 'Normal' reason: 'AllRequirementsMet' all requirements found, attempting install time="2022-09-15T08:47:06Z" level=warning msg="reusing existing cert opentelemetry-operator-controller-manager-service-cert" I0915 08:47:06.731470 1 event.go:282] Event(v1.ObjectReference{Kind:"ClusterServiceVersion", Namespace:"openshift-operators", Name:"opentelemetry-operator.v0.56.0-1", UID:"cae3195d-7d0a-4aa4-ba79-d8869e5f5888", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"875061522", FieldPath:""}): type: 'Normal' reason: 'InstallSucceeded' waiting for install components to report healthy time="2022-09-15T08:47:07Z" level=info msg="install strategy successful" csv=opentelemetry-operator.v0.56.0-1 id=YETBt namespace=openshift-operators phase=Installing strategy=deployment I0915 08:47:07.355798 1 event.go:282] Event(v1.ObjectReference{Kind:"ClusterServiceVersion", Namespace:"openshift-operators", Name:"opentelemetry-operator.v0.56.0-1", UID:"cae3195d-7d0a-4aa4-ba79-d8869e5f5888", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"875061568", FieldPath:""}): type: 'Normal' reason: 'InstallWaiting' installing: waiting for deployment opentelemetry-operator-controller-manager to become ready: deployment "opentelemetry-operator-controller-manager" not available: Deployment does not have minimum availability. time="2022-09-15T08:47:08Z" level=info msg="install strategy successful" csv=opentelemetry-operator.v0.56.0-1 id=jYIF+ namespace=openshift-operators phase=Installing strategy=deployment time="2022-09-15T08:47:09Z" level=info msg="install strategy successful" csv=opentelemetry-operator.v0.56.0-1 id=yc9DF namespace=openshift-operators phase=Installing strategy=deployment waiting for deployment opentelemetry-operator-controller-manager to become ready: deployment "opentelemetry-operator-controller-manager" not available: Deployment does not have minimum availability.
Version-Release number of selected component (if applicable):
Operator version - 0.56.0-1 OCP version - 4.10.21
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
The operator keeps reinstalling
Expected results:
The operator shouldn't reinstall and it should be stable
Additional info:
Cu created must gather but some data is missing in it. Logs are uploaded here -https://drive.google.com/drive/folders/19UFtC0FvZm6vwzRKUbBHrFMkqh5JKH_r?usp=sharing