-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.16
-
Critical
-
Yes
-
Rejected
-
False
-
Description of problem:
Fail to create osus instance due to metadata-helper container not found. # ./oc -n openshift-update-service get po NAME READY STATUS RESTARTS AGE graph-data-tag-digest 1/1 Running 0 119s sample-8494c559f4-pqhpw 2/3 CreateContainerError 0 17m sample-8c49666b7-r7cbt 2/3 CreateContainerError 0 17m updateservice-operator-c4987f95b-mzrt5 1/1 Running 0 54m # ./oc -n openshift-update-service describe po sample-8494c559f4-pqhpw ... Normal Created 13m kubelet Created container policy-engine Normal Started 13m kubelet Started container policy-engine Warning Failed 13m (x2 over 13m) kubelet Error: container create failed: time="2024-04-18T01:59:56Z" level=error msg="runc create failed: unable to start container process: exec: \"/usr/bin/metadata-helper\": stat /usr/bin/metadata-helper: no such file or directory" Warning Failed 13m kubelet Error: container create failed: time="2024-04-18T01:59:57Z" level=error msg="runc create failed: unable to start container process: exec: \"/usr/bin/metadata-helper\": stat /usr/bin/metadata-helper: no such file or directory" Warning Failed 13m kubelet Error: container create failed: time="2024-04-18T01:59:58Z" level=error msg="runc create failed: unable to start container process: exec: \"/usr/bin/metadata-helper\": stat /usr/bin/metadata-helper: no such file or directory" Warning ProbeError 13m (x2 over 13m) kubelet Readiness probe error: HTTP probe failed with statuscode: 503 body: Warning Unhealthy 13m (x2 over 13m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503 Warning Failed 13m kubelet Error: container create failed: time="2024-04-18T02:00:09Z" level=error msg="runc create failed: unable to start container process: exec: \"/usr/bin/metadata-helper\": stat /usr/bin/metadata-helper: no such file or directory" # ./oc -n openshift-update-service logs sample-8494c559f4-pqhpw -c metadata Error from server (BadRequest): container "metadata" in pod "sample-8494c559f4-pqhpw" is waiting to start: CreateContainerError
Version-Release number of selected component (if applicable):
cincinnati-operator-container-v5.0.3-2 cincinnati-container-v5.0.3-2
How reproducible:
100%
Steps to Reproduce:
1. create osus operator successfully 2. build graph-data image following the dockerfile in https://docs.openshift.com/container-platform/4.15/updating/updating_a_cluster/updating_disconnected_cluster/disconnected-update-osus.html#update-service-graph-data_updating-restricted-network-cluster-osus 3. create osus instance with following config # ./oc -n openshift-update-service get updateservice sample -ojson|jq .spec { "graphDataImage": "quay.io/openshifttest/graph-data:5.0.3", "releases": "quay.io/openshift-release-dev/ocp-release", "replicas": 1 }
Actual results:
fail to create osus instance
Expected results:
osus instance should be created successfully
Additional info:
osus 5.0.2 works well