Bug 1575919
| Summary: | set ansible option openshift_portal_net but it always use default value | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Hongan Li <hongli> | ||||
| Component: | Installer | Assignee: | Russell Teague <rteague> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Johnny Liu <jialiu> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.10.0 | CC: | aos-bugs, jokerman, mmccomas | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.10.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-05-08 18:12:25 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: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 1571992 *** |
Created attachment 1433112 [details] installation log with inventory file Description of problem: configure openshift-ansible option 'openshift_portal_net: "172.30.0.0/20"' when launch flexy job, but the serviceNetworkCIDR still use the default value "172.30.0.0/16" after installation. Version-Release number of the following components: openshift-ansible-3.10.0-0.36.0.git.0.521f0ef.el7.noarch How reproducible: always Steps to Reproduce: 1. Set openshift_portal_net: "172.30.0.0/20" then trigger installation 2. 3. Actual results: # oc get clusternetwork NAME CLUSTER NETWORKS SERVICE NETWORK PLUGIN NAME default 10.128.0.0/16:14 172.30.0.0/16 redhat/openshift-ovs-subnet Expected results: Service Network should use the pre-configured option: 172.30.0.0/20. Additional info: 1. full installation log attached. 2. no this issue in 3.9.