-
Bug
-
Resolution: Done-Errata
-
Major
-
ACM 2.9.0, Submariner 0.16.0
-
False
-
None
-
False
-
-
-
Submariner Sprint 2023-10, Submariner Sprint 2023-11, Submariner Sprint 2023-12
-
Moderate
-
No
Description of problem:
On OCP 4.14 clusters being configured for RDR, after installing Submariner add-ons, observed that submariner-metrics-proxy goes into CreateContainerError on both managed clusters.
submariner-metrics-proxy-w42jz 0/2 CreateContainerError 0 90m 10.133.2.21 compute-1 <none> <none>
Version-Release number of selected component (if applicable):
OCP: 4.14.0-0.nightly-2023-07-31-181848
ACM: 2.9.0-75 (quay.io:443/acm-d/acm-custom-registry:2.9.0-DOWNSTREAM-2023-08-04-03-03-30)
Submariner: 0.16.0 (brew.registry.redhat.io/rh-osbs/iib:549402)
How reproducible:
1/1
Steps to Reproduce:
- Deploy 3 OCP 4.14 clusters
- Install RHACM on hub cluster
- Using RHACM console, import other two clusters and connect using Submariner add-ons with globalnet enabled
- Observe the pod status in submariner-operator namespace
Actual results:
submariner-metrics-proxy pod in CreateContainerError state
In RHACM console, Degraded Multicluster network status and Agent status
Expected results:
All pods in running state and Healthy status in console.
Additional info:
Pod output:
$ oc get pod -n submariner-operator -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES submariner-addon-5c68bc9c69-zllnt 1/1 Running 0 101m 10.133.2.19 compute-1 <none> <none> submariner-gateway-5xfv4 1/1 Running 0 99m 10.1.114.66 compute-1 <none> <none> submariner-globalnet-2wsxb 1/1 Running 0 99m 10.1.114.66 compute-1 <none> <none> submariner-lighthouse-agent-cfbc9dc8-bhrwb 1/1 Running 0 99m 10.135.0.21 compute-2 <none> <none> submariner-lighthouse-coredns-5897d59676-7rgzm 1/1 Running 0 99m 10.133.2.22 compute-1 <none> <none> submariner-lighthouse-coredns-5897d59676-qnvwq 1/1 Running 0 99m 10.135.0.22 compute-2 <none> <none> submariner-metrics-proxy-w42jz 0/2 CreateContainerError 0 99m 10.133.2.21 compute-1 <none> <none> submariner-networkplugin-syncer-7c56549dd5-xswl8 1/1 Running 0 99m 10.135.0.20 compute-2 <none> <none> submariner-operator-7cddbc9b96-lq4xq 1/1 Running 0 100m 10.135.0.19 compute-2 <none> <none> submariner-routeagent-5dvpg 1/1 Running 0 99m 10.1.114.66 compute-1 <none> <none> submariner-routeagent-5qqkx 1/1 Running 0 99m 10.1.114.69 control-plane-0 <none> <none> submariner-routeagent-6x7tl 1/1 Running 0 99m 10.1.114.65 compute-0 <none> <none> submariner-routeagent-7ll8z 1/1 Running 0 99m 10.1.114.57 control-plane-2 <none> <none> submariner-routeagent-9hgzg 1/1 Running 0 99m 10.1.114.70 control-plane-1 <none> <none> submariner-routeagent-wlgvn 1/1 Running 0 99m 10.1.114.58 compute-2 <none> <none>
Error message seen in Events:
Error: container create failed: time="2023-08-04T10:22:56Z" level=error msg="runc create failed: unable to start container process: exec: \"/app/metricsproxy\": permission denied"
- duplicates
-
ACM-6782 Submariner - submariner-metrics-proxy pod crash on startup
-
- Closed
-
- links to
-
RHEA-2023:114022 RHEA: Submariner 0.16.0 - bug fix and enhancement update