-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.18
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
?
-
Done
-
Enhancement
-
-
None
-
None
-
None
-
None
Description of problem:
https://issues.redhat.com//browse/OCPBUGS-42671 introduced strict validation. that should help identify and correct many "broken" config. Feedback said that the new "unknown field" and "duplicate field" checks don't provide enough context; `unknown field \"tolerations\"` r.g. isn't always enough, especially that `tolerations` can occur in many places. this is a limitation of Go "encoding/json" v1, tried to enrich the context in vain https://go-review.googlesource.com/c/go/+/648055/comments/aedcc220_a137107a?tab=comments https://github.com/kubernetes-sigs/json is an enhanced Go "encoding/json" v1 that provides more context and has also a case-sensitive check (which is another limitation of Go "encoding/json" v1 https://pkg.go.dev/encoding/json#Unmarshal) This case-sensitive unmarshalling will be helpful for the transition towards CRD based config, as CRD validation is itself case-sensitive. --- - [ ] Prepare for this in 4.18
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-55005 context-rich and case-sensitive config validation for CMO
-
- Closed
-
- is cloned by
-
OCPBUGS-55005 context-rich and case-sensitive config validation for CMO
-
- Closed
-
- is related to
-
OCPBUGS-42671 Prometheus write_relabel_configs in remotewrite unable to drop metric in Grafana
-
- Closed
-
-
OCPBUGS-47654 CMO configmap validation ignores case senstive components
-
- Closed
-
- links to
-
RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update