Bug 1432020
| Summary: | Advanced installation cookbook advanced installation fails with no proxy settings | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Vítor Corrêa <vcorrea> |
| Component: | Installer | Assignee: | Vadim Rutkovsky <vrutkovs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Johnny Liu <jialiu> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.4.0 | CC: | aos-bugs, bleanhar, jkaur, jokerman, mmccomas, myllynen, vrutkovs, wmeng, wsun |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 3.10.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-08-27 18:15:45 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: | |||
|
Description
Vítor Corrêa
2017-03-14 10:45:08 UTC
(In reply to Vítor Corrêa from comment #0) > > openshift_master_cluster_hostname=cluster.domain > openshift_master_cluster_public_hostname=cluster.domain > > This was Working on 3.3, but for OCP 3.4, we must specify: > openshift_no_proxy=subdomain.domain,cluster.domain > > Wouldn't it make sense to add openshift_master_cluster_hostname to the list > of automated augmented list as described in > https://docs.openshift.com/container-platform/3.4/install_config/install/ > advanced_install.html#advanced-install-configuring-global-proxy I think so, too, yes. FWIW, somewhat related: https://bugzilla.redhat.com/show_bug.cgi?id=1414749. Thanks. Tested in master branch, no fix for it now. openshift_master_cluster_hostname not added into no_proxy list *** Bug 1568694 has been marked as a duplicate of this bug. *** *** Bug 1462652 has been marked as a duplicate of this bug. *** The two bugs I just duped against this are all because openshift_master_cluster_hostname is not added to the noproxy list by default. We need to fix that. Created PR for master (3.11) - https://github.com/openshift/openshift-ansible/pull/8809 (In reply to Vadim Rutkovsky from comment #14) > I think its being added correctly, it uses actual cluster hostname - > qe-wmeng310proxy3-nrr-1 - when adding it to a noproxy list. Please see the attachment in comment 12: openshift_master_cluster_hostname=qe-wmeng310proxy3-lb-nfs-1 > > In 3.10 internal hostnames are very important, these should be the same as > hostnames defined in inventory. Could you make sure these match and try > again? > I don't think it matters, if we have internal hostname set correctly (could be resolved to internal IP) on the nodes, we don't have to specify `openshift_hostname`. Created a PR which fixes the previous one - https://github.com/openshift/openshift-ansible/pull/8863. This should append openshift_master_cluster_hostname correctly. https://github.com/openshift/openshift-ansible/pull/8865 release-3.10 pick The PR is merged to v3.10.2-1,please check it. Verified in openshift-ansible-3.10.7-1.git.220.50204c4.el7.noarch.rpm While "openshift_master_cluster_hostname=ghuang-bug-lb-nfs-1" specified in inventory file, the hostname now could be added into NO_PROXY list correctly. # grep "ghuang-bug-lb-nfs-1" /etc/origin/master/master.env NO_PROXY=.centralci.eng.rdu2.redhat.com,.cluster.local,.lab.sjc.redhat.com,.svc,10.14.89.4,169.254.169.254,172.16.120.31,172.16.120.61,172.16.120.79,172.31.0.1,ghuang-bug-lb-nfs-1,ghuang-bug-master-etcd-1,ghuang-bug-master-etcd-2,ghuang-bug-master-etcd-3,ghuang-bug-node-1,ghuang-bug-node-2,ghuang-bug-node-registry-router-1,172.31.0.0/16,10.2.0.0/16 But the installation didn't complete, instead failed at task "Wait for all control plane pods to become ready". Tracking in Bug 1594726. |