Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1320952

Summary: Ansible default value for clusterNetworkCIDR
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: InstallerAssignee: OCP Installer <ocp-installer>
Installer sub component: openshift-ansible QA Contact: Gaoyun Pei <gpei>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, bhills, bleanhar, jokerman, mmccomas
Version: 3.2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 12:39:36 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 Johnny Liu 2016-03-24 10:58:57 UTC 
Description of problem:
According to https://github.com/openshift/openshift-docs/issues/1700:
<--snip-->
The default values for pod networking have changed:
    clusterNetworkCIDR (osm_cluster_network_cidr in ansible) now defaults to 10.128.0.0/14 (10.128.0.0 - 10.131.255.255) rather than 10.1.0.0/16.
    hostSubnetLength (osm_host_subnet_length in ansible) now defaults to 9 rather than 8 (meaning each node will be assigned a /23 subnet rather than a /24)
<--snip-->

After installation, found ansible is still setting its default value to "10.1.0.0/16" (refer to playbooks/byo/roles/openshift_facts/library/openshift_facts.py)
# cat /etc/origin/master/master-config.yaml
<--snip-->
networkConfig:
  clusterNetworkCIDR: 10.1.0.0/16
  hostSubnetLength: 8
  networkPluginName: redhat/openshift-ovs-subnet
# serviceNetworkCIDR must match kubernetesMasterConfig.servicesSubnet
  serviceNetworkCIDR: 172.30.0.0/16
<--snip-->

Version-Release number of selected component (if applicable):
openshift-ansible-roles-3.0.62-1.git.0.394cb87.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 openshift-github-bot 2016-11-07 21:02:52 UTC 
Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/b50b4ea0b03feb9431abd7294fe4fb6b549ddfc0
Update defaults for clusterNetworkCIDR & hostSubnetLength

Per https://github.com/openshift/openshift-docs/issues/1700:

The default values for pod networking have changed:
    - clusterNetworkCIDR now defaults to 10.128.0.0/14 (10.128.0.0 - 10.131.255.255)
      rather than 10.1.0.0/16.
    - hostSubnetLength now defaults to 9 rather than 8
      (meaning each node will be assigned a /23 subnet rather than a /24)

Fixes Bug 1320952
Comment 4 Johnny Liu 2016-11-09 07:43:23 UTC 
Verified this bug with openshift-ansible-3.4.18-1.git.0.ed7dac0.el7.noarch, and PASS.

# cat /etc/origin/master/master-config.yaml
<--snip-->
networkConfig:
  clusterNetworkCIDR: 10.128.0.0/14
  hostSubnetLength: 9
  networkPluginName: redhat/openshift-ovs-subnet
# serviceNetworkCIDR must match kubernetesMasterConfig.servicesSubnet
  serviceNetworkCIDR: 172.30.0.0/16
  externalIPNetworkCIDRs:
  - 0.0.0.0/0
<--snip-->

New an app, sti build successfully, and new network default setting take effect now.

# oc get po -n install-test
NAME                             READY     STATUS      RESTARTS   AGE
mongodb-1-v3ipr                  1/1       Running     0          1h
nodejs-mongodb-example-1-5rlh3   1/1       Running     0          1h
nodejs-mongodb-example-1-build   0/1       Completed   0          1h

# oc describe po nodejs-mongodb-example-1-5rlh3 -n install-test|grep IP
IP:			10.128.0.20
Comment 6 errata-xmlrpc 2017-01-18 12:39:36 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-2017:0066