-
Bug
-
Resolution: Done
-
Major
-
4.12.z, 4.11.z, 4.10.z, 4.9.z, 4.8.z
-
None
-
Proposed
-
False
-
This is a clone of issue OCPBUGS-6175. The following is the description of the original issue:
—
Description of problem:
When the cluster is configured with Proxy the swift client in the image registry operator is not using the proxy to authenticate with OpenStack, so it's unable to reach the OpenStack API. This issue became evident since recently the support was added to not fallback to cinder in case swift is available[1].
[1]https://github.com/openshift/cluster-image-registry-operator/pull/819
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Deploy a cluster with proxy and restricted installation 2. 3.
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-6175 Image registry Operator does not use Proxy when connecting to openstack
- Closed
- is blocked by
-
OCPBUGS-6175 Image registry Operator does not use Proxy when connecting to openstack
- Closed
- is cloned by
-
OCPBUGS-6907 Image registry Operator does not use Proxy when connecting to openstack
- Closed
- is depended on by
-
OCPBUGS-6907 Image registry Operator does not use Proxy when connecting to openstack
- Closed
- links to