-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.18, 4.19
-
None
This is a clone of issue OCPBUGS-50707. The following is the description of the original issue:
—
Description of problem:
Running the cluster-compare plugin agains the RAN reference produces a large number of warnings about CRs with identical names, and this makes the output harder to interpret, with no value to the end-user.
Version-Release number of selected component (if applicable):
4.18 (pre-GA)
How reproducible:
100%
Steps to Reproduce:
1. Run cluster-compare against the RAN reference
2. Look at all the warnings
3. Try to find the part that's not warnings
Actual results:
W0210 14:38:43.548770 5590 correlator.go:137] More then one template with same apiVersion, metadata_name, metadata_namespace, kind. By Default for each Cluster CR that is correlated to one of these templates the template with the least number of diffs will be used. To use a different template for a specific CR specify it in the diff-config (-c flag) Template names are: optional/ptp-config/PtpConfigDualCardGmWpc.yaml, optional/ptp-config/PtpConfigGmWpc.yaml, optional/ptp-config/PtpConfigMaster.yaml, optional/ptp-config/PtpConfigMasterForEvent.yaml More then one template with same apiVersion, metadata_name, metadata_namespace, kind. By Default for each Cluster CR that is correlated to one of these templates the template with the least number of diffs will be used. To use a different template for a specific CR specify it in the diff-config (-c flag) Template names are: optional/ptp-config/PtpConfigSlave.yaml, optional/ptp-config/PtpConfigSlaveForEvent.yaml More then one template with same apiVersion, metadata_name, metadata_namespace, kind. By Default for each Cluster CR that is correlated to one of these templates the template with the least number of diffs will be used. To use a different template for a specific CR specify it in the diff-config (-c flag) Template names are: optional/ptp-config/PtpOperatorConfig.yaml, optional/ptp-config/PtpOperatorConfigForEvent.yaml More then one template with same apiVersion, metadata_name, metadata_namespace, kind. By Default for each Cluster CR that is correlated to one of these templates the template with the least number of diffs will be used. To use a different template for a specific CR specify it in the diff-config (-c flag) Template names are: optional/ptp-config/PtpConfigBoundary.yaml, optional/ptp-config/PtpConfigBoundaryForEvent.yaml More then one template with same apiVersion, metadata_name, metadata_namespace, kind. By Default for each Cluster CR that is correlated to one of these templates the template with the least number of diffs will be used. To use a different template for a specific CR specify it in the diff-config (-c flag) Template names are: optional/ptp-config/PtpConfigForHA.yaml, optional/ptp-config/PtpConfigForHAForEvent.yaml More then one template with same apiVersion, metadata_name, metadata_namespace, kind. By Default for each Cluster CR that is correlated to one of these templates the template with the least number of diffs will be used. To use a different template for a specific CR specify it in the diff-config (-c flag) Template names are: required/sriov-operator/SriovOperatorConfig.yaml, required/sriov-operator/SriovOperatorConfigForSNO.yaml W0210 14:38:43.553368 5590 compare.go:496] There may be an issue with the API resources exposed by the cluster. Found kind but missing group/version for ClusterRoleBinding.rbac.authorization.k8s.io/v1, StorageClass.storage.k8s.io/v1 W0210 14:38:43.553389 5590 compare.go:425] Reference Contains Templates With Types (kind) Not Supported By Cluster: LVMCluster, PtpConfig, PtpOperatorConfig, SriovFecClusterConfig, SriovVrbClusterConfig W0210 14:38:45.352196 5590 warnings.go:70] v1 is deprecated and should be removed in next three releases, use v2 instead W0210 14:38:45.410737 5590 warnings.go:70] v1alpha1 is deprecated and should be removed in the next release, use v2 instead W0210 14:38:47.401955 5590 warnings.go:70] nmstate.io/v1beta1 NMState is deprecated; use nmstate.io/v1 NMState **********************************Cluster CR: v1_Namespace_openshift-logging Reference File: required/cluster-logging/ClusterLogNS.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components Diff Output: diff -u -N /var/folders/26/f1db78kx5sj6269739_r3w9c0000gn/T/MERGED-1326729486/v1_namespace_openshift-logging /var/folders/26/f1db78kx5sj6269739_r3w9c0000gn/T/LIVE-1544724326/v1_namespace_openshift-logging --- /var/folders/26/f1db78kx5sj6269739_r3w9c0000gn/T/MERGED-1326729486/v1_namespace_openshift-logging 2025-02-11 09:45:58 +++ /var/folders/26/f1db78kx5sj6269739_r3w9c0000gn/T/LIVE-1544724326/v1_namespace_openshift-logging 2025-02-11 09:45:58 @@ -3,6 +3,4 @@ metadata: annotations: workload.openshift.io/allowed: management - labels: - openshift.io/cluster-monitoring: "true" name: openshift-logging********************************** ......Summary CRs with diffs: 8/40 CRs in reference missing from the cluster: 12 required-cluster-logging: cluster-logging: Missing CRs: - required/cluster-logging/ClusterLogForwarder.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components - required/cluster-logging/ClusterLogServiceAccount.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components - required/cluster-logging/ClusterLogServiceAccountAuditBinding.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components - required/cluster-logging/ClusterLogServiceAccountInfrastructureBinding.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components ......
Expected results:
**********************************Cluster CR: v1_Namespace_openshift-logging Reference File: required/cluster-logging/ClusterLogNS.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components Diff Output: diff -u -N /var/folders/26/f1db78kx5sj6269739_r3w9c0000gn/T/MERGED-1326729486/v1_namespace_openshift-logging /var/folders/26/f1db78kx5sj6269739_r3w9c0000gn/T/LIVE-1544724326/v1_namespace_openshift-logging --- /var/folders/26/f1db78kx5sj6269739_r3w9c0000gn/T/MERGED-1326729486/v1_namespace_openshift-logging 2025-02-11 09:45:58 +++ /var/folders/26/f1db78kx5sj6269739_r3w9c0000gn/T/LIVE-1544724326/v1_namespace_openshift-logging 2025-02-11 09:45:58 @@ -3,6 +3,4 @@ metadata: annotations: workload.openshift.io/allowed: management - labels: - openshift.io/cluster-monitoring: "true" name: openshift-logging********************************** ......Summary CRs with diffs: 8/40 CRs in reference missing from the cluster: 12 required-cluster-logging: cluster-logging: Missing CRs: - required/cluster-logging/ClusterLogForwarder.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components - required/cluster-logging/ClusterLogServiceAccount.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components - required/cluster-logging/ClusterLogServiceAccountAuditBinding.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components - required/cluster-logging/ClusterLogServiceAccountInfrastructureBinding.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html#telco-ran-logging_ran-ref-design-components ......
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2025:3066
OpenShift Container Platform 4.18.z bug fix update
