Bug 2036951 - [cluster-csi-snapshot-controller-operator] proxy settings is being injected in container
Summary: [cluster-csi-snapshot-controller-operator] proxy settings is being injected i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: aos-storage-staff@redhat.com
QA Contact: Wei Duan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-04 13:54 UTC by Fabio Bertinatto
Modified: 2022-03-12 04:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-12 04:40:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-csi-snapshot-controller-operator pull 108 0 None open Bug 2036951: Don't inject proxy in operator pod 2022-01-04 13:55:29 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:40:22 UTC

Description Fabio Bertinatto 2022-01-04 13:54:22 UTC
There's no need to inject the proxy settings into the operator container because it doesn't access any external APIs/endpoints.

Comment 3 Wei Duan 2022-01-11 13:08:15 UTC
Verified pass with 
1. Install cluster with proxy:
$ oc get proxy cluster -o json | jq .spec
{
  "httpProxy": "http://proxy-user1:JYgU8qRZV4DY4PXJbxJK@10.0.99.4:3128",
  "httpsProxy": "http://proxy-user1:JYgU8qRZV4DY4PXJbxJK@10.0.99.4:3128",
  "noProxy": "test.no-proxy.com",
  "trustedCA": {
    "name": ""
  }
}

2. Proxy did not inject into snapshot pod 
$ oc -n openshift-cluster-storage-operator describe pod csi-snapshot-controller-operator-5c4db47864-p2cph | grep -i proxy
$ oc -n openshift-cluster-storage-operator describe pod csi-snapshot-controller-757544df4d-wvgrn | grep -i proxy
$ 

3. Test snapshot test cases passed
$ oc get pod,pvc
NAME                  READY   STATUS    RESTARTS   AGE
pod/mypod-ori         1/1     Running   0          31m
pod/mypod-restore-1   1/1     Running   0          15m

NAME                                  STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
persistentvolumeclaim/pvc-ori         Bound    pvc-8b713809-a971-4c8f-92bf-170a329cc4e5   2Gi        RWO            managed-csi    31m
persistentvolumeclaim/pvc-restore-1   Bound    pvc-4a5bd754-d33f-4730-b041-05748ab32e2f   2Gi        RWO            managed-csi    15m

$ oc get volumesnapshot
NAME         READYTOUSE   SOURCEPVC   SOURCESNAPSHOTCONTENT   RESTORESIZE   SNAPSHOTCLASS       SNAPSHOTCONTENT                                    CREATIONTIME   AGE
mysnapshot   true         pvc-ori                             2Gi           csi-azuredisk-vsc   snapcontent-0356c110-cb65-426f-8283-e447b9e4e7d4   17m            17m

Marked it as Verified.

Comment 6 errata-xmlrpc 2022-03-12 04:40:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056


Note You need to log in before you can comment on or make changes to this bug.