-
Bug
-
Resolution: Done-Errata
-
Major
-
4.18
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
Rejected
-
Telco kube-compare Sprint 262, Telco kube-compare Sprint 263, Telco kube-compare Sprint 264, Telco kube-compare Sprint 265, Telco kube-compare Sprint 268, Telco kube-compare Sprint 269
-
6
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
If I change the name of a CR (Like PerformanceProfile) which has a hard-coded name in the template, cluster-compare doesn't detect the name change other than to claim that the PerformanceProfile is missing
Version-Release number of selected component (if applicable):
4.18
How reproducible:
100%
Steps to Reproduce:
1. Deploy an SNO with DU profile, but edit the PerformanceProfile name 2. Run cluster-compare with the RAN reference
Actual results:
PerformanceProfile is listed as "missing" and not misnamed, making it harder to assess other potential differences in the reference.
Expected results:
PerformanceProfile should show up as a difference, with the object name highlighted as one of the differences
- is cloned by
-
OCPBUGS-53199 cluster-compare cannot differentiate between multiply-matched templates
-
- Closed
-
- is related to
-
OCPBUGS-54764 Allow customers to change CR names in ZTP cluster-compare reference
-
- New
-
- links to
-
RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update