-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.16.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
It is a continuation of (OCPBUGS-52871). The Engineering Team recommend to open a new card.
A customer is not able to install CloudNativePG Operator.
Version-Release number of selected component (if applicable):
1.25 and 1.26
Steps to Reproduce:
1. Opening a Cluster UI
2. Go to Operators and install CloudNativePG.
3. The message in the conditions is: BundleUnpackFailed --> bundle unpacking failed Reason: DeadlineExceeded, and Message: Job was active longer than specified deadline.
Actual results:
The Operator is not installed properly
Expected results:
Operator installed properly
Additional info:
Checking the "openshift-marketplace" events we can observe: 48m Normal Created pod/redhat-operators-p9vqg Created container: registry-server 48m Normal Started pod/redhat-operators-p9vqg Started container registry-server 48m Normal Killing pod/redhat-operators-p9vqg Stopping container registry-server 60m Normal Killing pod/redhat-operators-pvk87 Stopping container registry-server 72m Normal Scheduled pod/redhat-operators-t7hbg Successfully assigned openshift-marketplace/redhat-operators-t7hbg to ip-10-0-1-48.eu-west-1.compute.internal 72m Normal AddedInterface pod/redhat-operators-t7hbg Add eth0 [10.128.1.124/24] from ovn-kubernetes 72m Normal Pulled pod/redhat-operators-t7hbg Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:79505dcfd7a60dcbadd163223be0e7015159c0c04893c03ee1a3471ee7a112a2" already present on machine 72m Normal Created pod/redhat-operators-t7hbg Created container: extract-utilities 72m Normal Started pod/redhat-operators-t7hbg Started container extract-utilities 72m Normal Pulling pod/redhat-operators-t7hbg Pulling image "registry.redhat.io/redhat/redhat-operator-index:v4.16" 72m Normal Pulled pod/redhat-operators-t7hbg Successfully pulled image "registry.redhat.io/redhat/redhat-operator-index:v4.16" in 725ms (725ms including waiting) 72m Normal Created pod/redhat-operators-t7hbg Created container: extract-content 72m Normal Started pod/redhat-operators-t7hbg Started container extract-content 72m Normal Pulling pod/redhat-operators-t7hbg Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a9e3cf3d5cf92099b02dbf5094a7e8592b92d2ba05b0ce9b2b0f57a2812610e6" 72m Normal Pulled pod/redhat-operators-t7hbg Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a9e3cf3d5cf92099b02dbf5094a7e8592b92d2ba05b0ce9b2b0f57a2812610e6" in 702ms (702ms including waiting) 72m Normal Created pod/redhat-operators-t7hbg Created container: registry-server 72m Normal Started pod/redhat-operators-t7hbg Started container registry-server 72m Normal Killing pod/redhat-operators-t7hbg Stopping container registry-server 43s Normal Scheduled pod/redhat-operators-vxfhq Successfully assigned openshift-marketplace/redhat-operators-vxfhq to ip-10-0-2-61.eu-west-1.compute.internal 43s Normal AddedInterface pod/redhat-operators-vxfhq Add eth0 [10.128.28.124/24] from ovn-kubernetes 42s Normal Pulled pod/redhat-operators-vxfhq Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:79505dcfd7a60dcbadd163223be0e7015159c0c04893c03ee1a3471ee7a112a2" already present on machine 42s Normal Created pod/redhat-operators-vxfhq Created container: extract-utilities 42s Normal Started pod/redhat-operators-vxfhq Started container extract-utilities 42s Normal Pulling pod/redhat-operators-vxfhq Pulling image "registry.redhat.io/redhat/redhat-operator-index:v4.16" 40s Normal Pulled pod/redhat-operators-vxfhq Successfully pulled image "registry.redhat.io/redhat/redhat-operator-index:v4.16" in 1.396s (1.396s including waiting) 40s Normal Created pod/redhat-operators-vxfhq Created container: extract-content 40s Normal Started pod/redhat-operators-vxfhq Started container extract-content 38s Normal Pulling pod/redhat-operators-vxfhq Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a9e3cf3d5cf92099b02dbf5094a7e8592b92d2ba05b0ce9b2b0f57a2812610e6" 37s Normal Pulled pod/redhat-operators-vxfhq Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a9e3cf3d5cf92099b02dbf5094a7e8592b92d2ba05b0ce9b2b0f57a2812610e6" in 1.274s (1.274s including waiting) 36s Normal Created pod/redhat-operators-vxfhq Created container: registry-server 36s Normal Started pod/redhat-operators-vxfhq Started container registry-server 32s Warning Unhealthy pod/redhat-operators-vxfhq Startup probe failed: timeout: failed to connect service ":50051" within 1s 22s Normal Killing pod/redhat-operators-vxfhq Stopping container registry-server It seems that it is not able to connect to the service in port ":50051" and checking the services, these are the "redhat-operators" service in this concrete case: NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/certified-operators ClusterIP 172.30.139.106 <none> 50051/TCP 84d service/community-operators ClusterIP 172.30.108.18 <none> 50051/TCP 84d service/marketplace-operator-metrics ClusterIP 172.30.97.226 <none> 8383/TCP,8081/TCP 574d service/redhat-marketplace ClusterIP 172.30.114.49 <none> 50051/TCP 84d service/redhat-operators ClusterIP 172.30.124.23 <none> 50051/TCP 84d To try to solve the issue, we have tried several times the following solution article without success --> https://access.redhat.com/solutions/6459071 Always the same message appears when trying to install the Operator. If it is not the correct place to allocate this problem or if I should create an OHSS please let me know. Many thanks in advance.
- impacts account
-
-
- Closed
-