Bug 1797894
| Summary: | [4.5]machineNetwork in noProxy list is flushed by Network-Operator | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | weiwei jiang <wjiang> | |
| Component: | Networking | Assignee: | Juan Luis de Sousa-Valadas <jdesousa> | |
| Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | aconstan, danw, gpei, jialiu, pdhamdhe, wsun, yanyang | |
| Version: | 4.4 | Keywords: | Regression, TestBlocker | |
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause:
When the installer introduced machineNetwork the cluster network operator ignored wasn't modified to add it to proxy.status.noProxy.
Consequence:
proxy.status.noProxy missing machineNetwork
Fix:
Add it to proxy.status.noProxy
Result:
noProxy contains the expected fields.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1805726 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:13:54 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1806403 | |||
|
Description
weiwei jiang
2020-02-04 07:39:53 UTC
Also this this issue in upi on aws install with proxy enabled. `machineNetwork` filed in install-config.yaml: proxy: httpProxy: http://proxy-user1:xxx@QE_PROXY_PLACEHOLDER:3128 httpsProxy: http://proxy-user1:xxx@QE_PROXY_PLACEHOLDER:3128 noProxy: test.no-proxy.com networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 serviceNetwork: - 172.30.0.0/16 networkType: OVNKubernetes machineNetwork: - cidr: 10.0.0.0/16 Trigger installation, failed. $ ./openshift-install wait-for install-complete --dir '/home/installer3/workspace/Launch Environment Flexy/workdir/install-dir' level=info msg="Waiting up to 30m0s for the cluster at https://api.jialiu-25822.qe.devcluster.openshift.com:6443 to initialize..." level=info msg="Cluster operator insights Disabled is False with : " level=info msg="Cluster operator machine-config Available is False with : Cluster not available for 4.4.0-0.nightly-2020-02-03-081920" level=error msg="Cluster operator machine-config Degraded is True with RequiredPoolsFailed: Failed to resync 4.4.0-0.nightly-2020-02-03-081920 because: 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-61-87.us-east-2.compute.internal is reporting: \\\"machineconfig.machineconfiguration.openshift.io \\\\\\\"rendered-master-fdb913d94892563827998728eb2d3557\\\\\\\" not found\\\", Node ip-10-0-59-238.us-east-2.compute.internal is reporting: \\\"machineconfig.machineconfiguration.openshift.io \\\\\\\"rendered-master-fdb913d94892563827998728eb2d3557\\\\\\\" not found\\\", Node ip-10-0-70-4.us-east-2.compute.internal is reporting: \\\"machineconfig.machineconfiguration.openshift.io \\\\\\\"rendered-master-fdb913d94892563827998728eb2d3557\\\\\\\" not found\\\"\", retrying" level=fatal msg="failed to initialize the cluster: Cluster operator machine-config is reporting a failure: Failed to resync 4.4.0-0.nightly-2020-02-03-081920 because: 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-61-87.us-east-2.compute.internal is reporting: \\\"machineconfig.machineconfiguration.openshift.io \\\\\\\"rendered-master-fdb913d94892563827998728eb2d3557\\\\\\\" not found\\\", Node ip-10-0-59-238.us-east-2.compute.internal is reporting: \\\"machineconfig.machineconfiguration.openshift.io \\\\\\\"rendered-master-fdb913d94892563827998728eb2d3557\\\\\\\" not found\\\", Node ip-10-0-70-4.us-east-2.compute.internal is reporting: \\\"machineconfig.machineconfiguration.openshift.io \\\\\\\"rendered-master-fdb913d94892563827998728eb2d3557\\\\\\\" not found\\\"\", retrying" After installation failure, compare noProxy list between bootstrap and cluster, found some difference. # sdiff b.log c.log .cluster.local .cluster.local .svc .svc .us-east-2.compute.internal .us-east-2.compute.internal 10.0.0.0/16 < 10.128.0.0/14 10.128.0.0/14 127.0.0.1 127.0.0.1 169.254.169.254 169.254.169.254 172.30.0.0/16 172.30.0.0/16 api-int.jialiu-25822.qe.devcluster.openshift.com api-int.jialiu-25822.qe.devcluster.openshift.com etcd-0.jialiu-25822.qe.devcluster.openshift.com etcd-0.jialiu-25822.qe.devcluster.openshift.com etcd-1.jialiu-25822.qe.devcluster.openshift.com etcd-1.jialiu-25822.qe.devcluster.openshift.com etcd-2.jialiu-25822.qe.devcluster.openshift.com etcd-2.jialiu-25822.qe.devcluster.openshift.com localhost localhost test.no-proxy.com test.no-proxy.com b.log is the noProxy list captured by running `env |grep -i proxy`, c.log is the noProxy list captured by running `oc get proxy cluster -o yaml`. Verified this bug on 4.5.0-0.nightly-2020-03-06-190457
# oc get cm cluster-config-v1 -n kube-system -o yaml | grep cidr -A 2
- cidr: 10.128.0.0/14
hostPrefix: 23
machineNetwork:
- cidr: 10.0.0.0/16
networkType: OpenShiftSDN
serviceNetwork:
# oc get proxy cluster -o yaml
apiVersion: config.openshift.io/v1
kind: Proxy
metadata:
creationTimestamp: "2020-03-09T06:40:15Z"
generation: 1
name: cluster
resourceVersion: "680"
selfLink: /apis/config.openshift.io/v1/proxies/cluster
uid: 6d53c4fd-ddc3-4ad1-a6d0-3b3f4f83d5fc
spec:
httpProxy: http://proxy-user1:JYgU8qRZV4DY4PXJbxJK@ec2-3-12-160-4.us-east-2.compute.amazonaws.com:3128
httpsProxy: http://proxy-user1:JYgU8qRZV4DY4PXJbxJK@ec2-3-12-160-4.us-east-2.compute.amazonaws.com:3128
noProxy: test.no-proxy.com
trustedCA:
name: ""
status:
httpProxy: http://proxy-user1:JYgU8qRZV4DY4PXJbxJK@ec2-3-12-160-4.us-east-2.compute.amazonaws.com:3128
httpsProxy: http://proxy-user1:JYgU8qRZV4DY4PXJbxJK@ec2-3-12-160-4.us-east-2.compute.amazonaws.com:3128
noProxy: .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.zzhao45.qe.devcluster.openshift.com,etcd-0.zzhao45.qe.devcluster.openshift.com,etcd-1.zzhao45.qe.devcluster.openshift.com,etcd-2.zzhao45.qe.devcluster.o
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-2020:2409 |