-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.13, 4.12, 4.11, 4.10, 4.14
-
None
-
Critical
-
No
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-18143. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-18142. The following is the description of the original issue:
—
Description of problem:
IBM VPC CSI Driver failed to provisioning volume in proxy cluster, (if I understand correctly) it seems the proxy in not injected because in our definition (https://github.com/openshift/ibm-vpc-block-csi-driver-operator/blob/master/assets/controller.yaml), we are injecting proxy to csi-driver: config.openshift.io/inject-proxy: csi-driver config.openshift.io/inject-proxy-cabundle: csi-driver but the container name is iks-vpc-block-driver in https://github.com/openshift/ibm-vpc-block-csi-driver-operator/blob/master/assets/controller.yaml#L153 I checked the proxy in not defined in controller pod or driver container ENV.
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-08-11-055332
How reproducible:
Always
Steps to Reproduce:
1. Create IBM cluster with proxy setting 2. create pvc/pod with IBM VPC CSI Driver
Actual results:
It failed to provisioning volume
Expected results:
Provisioning volume works well on proxy cluster
Additional info:
- blocks
-
OCPBUGS-23053 [IBM VPC] failed provisioning volume in proxy cluster
- Closed
- clones
-
OCPBUGS-18143 [IBM VPC] failed provisioning volume in proxy cluster
- Closed
- is blocked by
-
OCPBUGS-18143 [IBM VPC] failed provisioning volume in proxy cluster
- Closed
- is cloned by
-
OCPBUGS-23053 [IBM VPC] failed provisioning volume in proxy cluster
- Closed
- links to
-
RHBA-2023:6842 OpenShift Container Platform 4.12.z bug fix update