Bug 1901034

When installing a cluster behind proxy, installation get failed.
level=info msg=Cluster operator machine-config Progressing is True with : Working towards 4.7.0-0.nightly-2020-11-23-195308
level=error msg=Cluster operator machine-config Degraded is True with RequiredPoolsFailed: Unable to apply 4.7.0-0.nightly-2020-11-23-195308: timed out waiting for the condition during syncRequiredMachineConfigPools: pool master has not progressed to latest configuration: configuration status for pool master is empty: pool is degraded because nodes fail with "3 nodes are reporting degraded status on sync": "Node ip-10-0-52-10.us-east-2.compute.internal is reporting: \"machineconfig.machineconfiguration.openshift.io \\\"rendered-master-c12bd4e2165c598321688af24bf672b9\\\" not found\", Node ip-10-0-77-145.us-east-2.compute.internal is reporting: \"machineconfig.machineconfiguration.openshift.io \\\"rendered-master-c12bd4e2165c598321688af24bf672b9\\\" not found\", Node ip-10-0-48-13.us-east-2.compute.internal is reporting: \"machineconfig.machineconfiguration.openshift.io \\\"rendered-master-c12bd4e2165c598321688af24bf672b9\\\" not found\"", retrying
level=info msg=Cluster operator machine-config Available is False with : Cluster not available for 4.7.0-0.nightly-2020-11-23-195308
level=error msg=Cluster initialization failed because one or more operators are not functioning properly.
level=error msg=The cluster should be accessible for troubleshooting as detailed in the documentation linked below,
level=error msg=https://docs.openshift.com/container-platform/latest/support/troubleshooting/troubleshooting-installations.html
level=error msg=The 'wait-for install-complete' subcommand can then be used to continue the installation
level=fatal msg=failed to initialize the cluster: Cluster operator machine-config is still updating

After the failure, dig into it, we found the root cause is mismatch of NO_PROXY setting between bootstrap and cluster global setting
<       Environment=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.gpei-471.qe.devcluster.openshift.com,etcd-0.,etcd-1.,etcd-2.,localhost,test.no-proxy.com
---
>       Environment=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.gpei-471.qe.devcluster.openshift.com,etcd-0.gpei-471.qe.devcluster.openshift.com,etcd-1.gpei-471.qe.devcluster.openshift.com,etcd-2.gpei-471.qe.devcluster.openshift.com,localhost,test.no-proxy.com

$ oc get proxies.config.openshift.io cluster  -o yaml
<--snip-->
spec:
  httpProxy: http://user:password@10.0.99.4:3128
  httpsProxy: http://user:password@10.0.99.4:3128
  noProxy: test.no-proxy.com
  trustedCA:
    name: ""
status:
  httpProxy: http://user:password@10.0.99.4:3128
  httpsProxy: http://user:password@10.0.99.4:3128
  noProxy: .cluster.local,.svc,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.miyadav24azur.qe.azure.devcluster.openshift.com,etcd-0.,etcd-1.,etcd-2.,localhost,test.no-proxy.com

Seem like it missing domain for etcd fqdn, while boostrap has it.


Version:
4.7.0-0.nightly-2020-11-23-195308


Platform:
gcp/azure/vsphere/aws


both IPI and UPI

What happened?
After


What did you expect to happen?
When running installation behind proxy, installation get failed.


How to reproduce it (as minimally and precisely as possible)?
1. inject proxy setting into install-config.yaml, such as:
---
apiVersion: v1
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform: {}
  replicas: 3
compute:
- architecture: amd64
  hyperthreading: Enabled
  name: worker
  platform: {}
  replicas: 3
metadata:
  name: gpei-472
platform:
  aws:
    region: us-east-2
    subnets:
    - subnet-0c56d13268c3b8d24
    - subnet-02c73c48c59eca6b0
    - subnet-0908bd983fe473287
    - subnet-080c64ca63b15fb2d
pullSecret: HIDDEN
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  serviceNetwork:
  - 172.30.0.0/16
  machineNetwork:
  - cidr: 10.0.0.0/16
  networkType: OpenShiftSDN
publish: External
proxy:
  httpProxy: http://user:password@proxy.example.com:3128
  httpsProxy: http://user:password@proxy.example.com:3128
  noProxy: test.no-proxy.com
baseDomain: qe.devcluster.openshift.com
2. Run the installation


Anything else we need to know?
1. Did not hit such issues on 4.7.0-0.nightly-2020-11-18-085225
2. We see this issue for the 1st time on 4.7.0-0.nightly-2020-11-20-234717