*** Bug 2071686 has been marked as a duplicate of this bug. ***

Verified using ipi aws deployment with version: 
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2022-05-25-223510   True        False         45m     Error while reconciling 4.9.0-0.nightly-2022-05-25-223510: an unknown error has occurred: MultipleErrors


Verification steps:

1. Configure a proxy in the cluster

oc edit proxy cluster
...
  spec:
    httpProxy: http://user:pass@proxy-fake:1111
    httpsProxy: http://user:pass@proxy-fake:1111
    noProxy: test.no-proxy.com
    trustedCA:
      name: ""

2. Verfify that the proxy has been added to MCD pods environment variables
$ oc get pods -o yaml machine-config-daemon-6snvk | grep env -A 9
    env:
    - name: NODE_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: spec.nodeName
    - name: HTTP_PROXY
      value: http://user:pass@proxy-fake:1111
    - name: HTTPS_PROXY
      value: http://user:pass@proxy-fake:1111

3. Remove the proxy from the cluster

oc edit proxy cluster
...
spec:
  trustedCA:
    name: ""

4. Verify that the proxy has been removed from MCD pods environmnet variables

$ oc get pods machine-config-daemon-4gv8c -o yaml | grep env -A 9
...
    env:
    - name: NODE_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: spec.nodeName
    image: quay.io/openshift-release-d.....


Fake proxies will break the nodes (they cant get ready) and will cause the daemonset pods to be stuck in terminating status. It's better to use a real proxy to execute the verification steps.



We move the status to VERIFIED.

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 (OpenShift Container Platform 4.9.36 bug fix 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/RHBA-2022:4741