-
Bug
-
Resolution: Done-Errata
-
Minor
-
4.17.z, 4.16.z, 4.18.z, 4.19.0, 4.20.0
-
None
-
1
-
MCO Sprint 271
-
1
-
False
-
-
Release Note Not Required
-
In Progress
I ran into this while debugging https://issues.redhat.com/browse/OCPBUGS-54692.
The error returned by this function has two concatenated elements:
- the reconciliation error of the old and new rendered MCs
- the first reconciliation error encountered between the old rendered MC and new base MCs
(2) was meant to be surgical about specifying the problematic base MC, but it can mistakenly catch false positives. This is because the base MCs can override each other and an earlier MC being irreconcilable to the old rendered MC does not necessarily mean that it is the issue. For example, in https://issues.redhat.com/browse/OCPBUGS-54692,
FIPS is only set to true in 99-worker-fips, and every other base MC has has it set to false. This causes the function to determine that 00-worker is the problematic base MC when the actual issue was a new MC that the user added(luks-worker). This is mostly cosmetic and should be easy to deduce from the first error, but we should fix it anyway to avoid confusion.
- blocks
-
OCPBUGS-56170 error from generateAndValidateRenderedMachineConfig function can be misleading
-
- Closed
-
- depends on
-
OCPBUGS-54697 error from generateAndValidateRenderedMachineConfig function can be misleading
-
- Verified
-
- is cloned by
-
OCPBUGS-56170 error from generateAndValidateRenderedMachineConfig function can be misleading
-
- Closed
-
- links to
-
RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update