Bug 1366125 - [networking_public_54]'ingressIPNetworkCIDR' should be added in master-config.yaml by ansilbe installation
Summary: [networking_public_54]'ingressIPNetworkCIDR' should be added in master-config...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.3.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Samuel Munilla
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-11 06:26 UTC by zhaozhanqi
Modified: 2016-10-27 16:12 UTC (History)
6 users (show)

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
Clone Of:
Environment:
Last Closed: 2016-10-27 16:12:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2122 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix update 2016-10-27 20:11:30 UTC

Description zhaozhanqi 2016-08-11 06:26:30 UTC
Description of problem:
there is a new field 'ingressIPNetworkCIDR' did not be found when using the ansilbe install the env.

you can refer to https://github.com/openshift/origin/pull/9454 for detail info

Version-Release number of selected component (if applicable):
openshift version
openshift v3.3.0.18
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Brenton Leanhardt 2016-08-11 19:12:38 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?

Comment 2 Scott Dodson 2016-08-16 15:08:01 UTC
Pushing to upcoming release unless someone identifies a regression without implementing this change.

Comment 3 zhaozhanqi 2016-08-23 02:16:51 UTC
(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

Comment 6 Wenkai Shi 2016-10-24 09:42:21 UTC
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
...

Comment 8 errata-xmlrpc 2016-10-27 16:12:44 UTC
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


Note You need to log in before you can comment on or make changes to this bug.