Bug 1746360 - cluster-network-operator: openshift-sdn mode should not be required
Summary: cluster-network-operator: openshift-sdn mode should not be required
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.2.0
Assignee: Casey Callendrello
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-28 09:26 UTC by Casey Callendrello
Modified: 2019-10-16 06:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:38:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 302 0 None closed Bug 1746360: openshift-sdn: allow empty mode 2020-12-09 02:33:05 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:38:24 UTC

Description Casey Callendrello 2019-08-28 09:26:14 UTC 
As part of the QE of the enable-unidling feature, it was realized that we don't require an openshift-sdn config, but if provided, we require the mode to be set.

This doesn't make any sense, and makes it hard to actually configure. So, remove the requirement.
Comment 2 Anurag saxena 2019-08-29 16:54:19 UTC 
This works fine now on 4.2.0-0.nightly-2019-08-29-062233 and "mode:" is not required now to be present in config

CNO config excerpt -

spec:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  defaultNetwork:
    openshiftSDNConfig:
      enableUnidling: false
    type: OpenShiftSDN
  serviceNetwork:
  - x.x.0.0/16

verified it via same steps taken for Bug 1742207
Comment 3 errata-xmlrpc 2019-10-16 06:38:11 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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.