Bug 1889701 - Network Operator CRD updated in openshift/api is not copied to release payload.
Summary: Network Operator CRD updated in openshift/api is not copied to release payload.
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Ricardo Carrillo Cruz
QA Contact: zhaozhanqi
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-20 12:16 UTC by Venkata Siva Teja Areti
Modified: 2020-12-03 14:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Venkata Siva Teja Areti 2020-10-20 12:16:05 UTC
Description of problem:
Network Operator CRD in openshift/api is not copied to release payload. But instead another CRD present in cluster-network-operator repo is copied. This is causing a mismatch in CRD spec.

For example, log level validation in CRD spec is not seen in a 4.7 cluster. 

> $ oc get crd networks.operator.openshift.io -o jsonpath="{.spec.versions[0].schema.openAPIV3Schema.properties.spec.properties.logLevel}"
> map[description:logLevel allows configuring the logging level of the components deployed by the operator. Currently only Kuryr SDN is affected by this setting. Please note that turning on extensive logging may affect performance. The default value is "Normal". type:string]


As I understand, this file is copied to the cluster.


Comment 1 Stefan Schimanski 2020-10-20 12:33:58 UTC
Background: openshift/api is the source of thruth for our API definitions. Every operator is supposed to copy from there into their manifests/ directory DURING image builds.

Comment 2 Ricardo Carrillo Cruz 2020-11-11 12:26:55 UTC
will look into this today

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