Bug 1951891 - [migration] cannot change ClusterNetwork CIDR during migration
Summary: [migration] cannot change ClusterNetwork CIDR during migration
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Peng Liu
QA Contact: huirwang
Depends On:
TreeView+ depends on / blocked
Reported: 2021-04-21 06:28 UTC by Peng Liu
Modified: 2021-07-27 23:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 23:02:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1067 0 None open Bug 1951891: Allow changing cluster network cidr during a migration 2021-04-21 07:00:16 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:02:40 UTC

Description Peng Liu 2021-04-21 06:28:48 UTC
Description of problem:

The cluster network doesn't allow changing the cluster network CIDR, and print log:

I0421 06:07:58.559363       1 log.go:184] Reconciling Network.operator.openshift.io cluster
I0421 06:07:58.560423       1 log.go:184] Not applying unsafe change: invalid configuration: [cannot change ClusterNetwork]

Version-Release number of selected component (if applicable):

How reproducible:

Trigger an SDN migration with:

oc patch Network.config.openshift.io cluster --type=merge --patch '{"spec":{"networkType":"OVNKubernetes","clusterNetwork":[{"cidr":"","hostPrefix":23}]}}'

Actual results:

CNO didn't deploy OVNKubernetes in the cluster.

Expected results:
OVNKubernetes can be deployed in the cluster.

Additional info:

Comment 6 errata-xmlrpc 2021-07-27 23:02:20 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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