Bug 1370295 - RFE - Changing the servicesSubnet and the serviceNetworkCIDR after installation fails
Summary: RFE - Changing the servicesSubnet and the serviceNetworkCIDR after installati...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.11.0
Assignee: Dan Winship
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 20:32 UTC by Eric Jones
Modified: 2021-12-10 14:43 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-11 16:11:13 UTC
Target Upstream Version:
mcurry: needinfo-
mcurry: needinfo-

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Eric Jones 2016-08-25 20:32:01 UTC 
Description of problem:
Customer needs to have application (inside OpenShift) access an application (external to Openshift) that is running on an IP address that falls within the servicesSubnet range for their OpenShift Cluster. The only way to correct this would be to change the servicesSubnet and serviceNetworkCIDR values, which appears to be unsupported as well as breaking various services if you change it on a currently running cluster.

Steps to Reproduce:
1. Change the servicesSubnet and serviceNetworkCIDR values in the master-config file
2. Restart atomic-openshift-master services 

Actual results:
Cluster does not respond properly (oc only works ~50% of the time)

Expected results:
Cluster adjusts properly and continues to work.
Comment 7 Dan Winship 2016-08-26 13:18:32 UTC 
This is currently showing up on the blocker report but should not be since it is an RFE
Comment 12 Dan Winship 2016-10-25 15:25:03 UTC 
Docs PR for 3.4: https://github.com/openshift/openshift-docs/pull/3112
Comment 21 Michael Burke 2018-09-12 20:29:23 UTC 
Eric and Dan --

If you think this issue should go into the 3.11 Release Notes, please enter Doc Text above. I am not clear on what the resolution is. 

"Because changing the `servicesSubnet` and `serviceNetworkCIDR` values is not supported in openshift-sdn, changing those values in the master configuration file and restarting will result in OpenShift failing. Changing the IPs addresses is supported by OVN." ??

Thank you
Michael
Comment 22 Dan Winship 2018-09-13 13:01:24 UTC 
There does not need to be anything in the 3.11 release notes; the feature was not implemented, so nothing changed in 3.11.
Note You need to log in before you can comment on or make changes to this bug.