Bug 1366125
| Summary: | [networking_public_54]'ingressIPNetworkCIDR' should be added in master-config.yaml by ansilbe installation | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> |
| Component: | Installer | Assignee: | Samuel Munilla <smunilla> |
| Status: | CLOSED ERRATA | QA Contact: | zhaozhanqi <zzhao> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | aos-bugs, bleanhar, jokerman, mmccomas, weshi, zzhao |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
A new advanced installer configuration variable named 'openshift_master_ingress_ip_network_cidr' has been added to configure the IngressIPNetworkCIDR. For more information on this feature please see https://docs.openshift.com/container-platform/3.3/admin_guide/tcp_ingress_external_ports.html
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-27 16:12:44 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
zhaozhanqi
2016-08-11 06:26:30 UTC
Obviously we need to be able to set this with ansible. Is there a regression without this setting or is it that a new feature cannot be used? Pushing to upcoming release unless someone identifies a regression without implementing this change. (In reply to Brenton Leanhardt from comment #1) > Obviously we need to be able to set this with ansible. Is there a > regression without this setting or is it that a new feature cannot be used? sorry miss your comment. this is new feature, if the ingressIPNetworkCIDR did not set in master-config.yaml, then the user will cannot use the ingress ip feature. for example, if the ingressIPNetworkCIDR set '10.66.0.0/16' ,the ingress ip will be assigned from the range. if not setting. the ingress ip will be always 'pending'. details you can refer to https://github.com/openshift/origin/pull/9454 Can finish install with field "ingressIPNetworkCIDR", when finished, it can also find in master-config.yaml. [root@ansible ~]# rpm -qa | grep openshift openshift-ansible-3.3.38-1.git.0.2637ed5.el7.noarch openshift-ansible-roles-3.3.38-1.git.0.2637ed5.el7.noarch openshift-ansible-docs-3.3.38-1.git.0.2637ed5.el7.noarch openshift-ansible-callback-plugins-3.3.38-1.git.0.2637ed5.el7.noarch openshift-ansible-lookup-plugins-3.3.38-1.git.0.2637ed5.el7.noarch openshift-ansible-playbooks-3.3.38-1.git.0.2637ed5.el7.noarch openshift-ansible-filter-plugins-3.3.38-1.git.0.2637ed5.el7.noarch atomic-openshift-utils-3.3.38-1.git.0.2637ed5.el7.noarch [root@master ~]# openshift version openshift v3.3.1.3 kubernetes v1.3.0+52492b4 etcd 2.3.0+git [root@ansible ~]# cat hosts ... openshift_master_ingress_ip_network_cidr=172.46.0.0/16 ... [root@ansible ~]# ansible-playbook -i hosts -v /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml [root@master ~]# cat /etc/origin/master/master-config.yaml ... ingressIPNetworkCIDR: 172.46.0.0/16 ... 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-2016:2122 |