-
Bug
-
Resolution: Done
-
Major
-
None
-
4.17.z, 4.16.z, 4.18.z
Description of problem:
cluster-compare (and our CI) identifies a difference in sriovNetworkNodePolicy.yaml
Version-Release number of selected component (if applicable):
cluster-compare 4.19 pre-release (or 0.9.0 upstream)
How reproducible:
100%
Steps to Reproduce:
1. Upgrade cluster-compare tool 2. make -C telco-core/configuration/ check
Actual results:
Cluster CR: sriovnetwork.openshift.io/v1_SriovNetworkNodePolicy_openshift-sriov-network-operator_$name Reference File: required/networking/sriov/sriovNetworkNodePolicy.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/core/telco-core-ref-design-components.html#telco-core-sriov_core-ref-design-components Diff Output: diff -u -N /tmp/MERGED-3832947135/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_-name /tmp/LIVE-2036955131/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_-name --- /tmp/MERGED-3832947135/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_-name 2025-04-10 17:17:01.213734283 -0400 +++ /tmp/LIVE-2036955131/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_-name 2025-04-10 17:17:01.213734283 -0400 @@ -3,4 +3,3 @@ metadata: name: $name namespace: openshift-sriov-network-operator -spec: null
Expected results:
No difference detected
- blocks
-
OCPBUGS-54973 telco-core reference identifies difference between 'spec: null' and 'spec: {}'
-
- Closed
-
- is cloned by
-
OCPBUGS-54973 telco-core reference identifies difference between 'spec: null' and 'spec: {}'
-
- Closed
-
- links to
- mentioned on