Description of problem: Setting HTTP_PROXY, HTTPS_PROXY, and NO_PROXY variables on the Proxy CR, wont rollout new console deployment. Version-Release number of selected component (if applicable): 4.2.0-0.ci-2019-09-17-073113 How reproducible: Always Steps to Reproduce: 1. For the Proxy CR set `noProxy: clusternoproxy.example.com` in the `spec` field 2. 3. Actual results: New console deployment should be rolledout, which pod's should contain NO_PROXY envVar Expected results: New console deployment is not rolledout. Additional info:
PR: https://github.com/openshift/console-operator/pull/297
oc patch proxy.config --type=merge -p '{"spec": "clusternoproxy.example.com"} oc rsh -n openshift-console console-567777b67c-d6cqd sh-4.2$ env |grep PROXY NO_PROXY=.cluster.local,.svc,.us-east-2.compute.internal,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.qe-ui-09230831.qe.devcluster.openshift.com,api.qe-ui-09230831.qe.devcluster.openshift.com,etcd-0.qe-ui-09230831.qe.devcluster.openshift.com,etcd-1.qe-ui-09230831.qe.devcluster.openshift.com,etcd-2.qe-ui-09230831.qe.devcluster.openshift.com,localhost 4.2.0-0.nightly-2019-09-22-171807 Verified this bug
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, 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/RHBA-2019:2922