-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14, 4.16, 4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The current ZTP reference has many CR templates with hard-coded names. This means customers cannot rename their objects.
Version-Release number of selected component (if applicable):
All
How reproducible:
100%
Steps to Reproduce:
1. Deploy a DU, but rename all the CRs
2. Attempt to run cluster-compare
Actual results:
Many objects are not compared against the proper templates, and are shown as "missing" even though they are present.
Expected results:
The objects should be checked against the proper template because the template should allow any object name.
Additional info:
For some objects, like MachineConfig or Tuned, there may be some occasions where there are many objects of the same ApiVersion&Kind where some should be checked and some should not. cluster-compare 4.19 introduces a new 'doNotMatch' template function that can exclude some CRs from consideration.
Example of 'doNotMatch': https://github.com/openshift/kube-compare/blob/main/pkg/compare/testdata/DoNotMatch/reference/d1-anyname.yaml
Customer workaround:
The "manualCorrelation" setting can be used to work around this bug:
- relates to
-
-
- Closed
-