-
Bug
-
Resolution: Done
-
Major
-
None
-
4.13.0
-
No
-
CNF RAN Sprint 234, CNF RAN Sprint 235
-
2
-
False
-
-
Description of problem:
Applying the following source-cr does not generate the expected configuration. https://github.com/openshift-kni/cnf-features-deploy/blob/master/ztp/source-crs/PtpOperatorConfig.yaml The daemonNodeSelector does not update (empty key/value set}
Version-Release number of selected component (if applicable):
OCP 4.13.0-rc.3
How reproducible:
Always
Steps to Reproduce:
1. Install SNO node with OCP 4.13.0-rc.3 with DU profile from ZTP 2. Check PtpOperatorConfig on node and compare with CR 3.
Actual results:
oc get ptpoperatorconfigs.ptp.openshift.io -A -o yaml apiVersion: v1 items: - apiVersion: ptp.openshift.io/v1 kind: PtpOperatorConfig metadata: creationTimestamp: "2023-04-13T16:30:58Z" generation: 1 name: default namespace: openshift-ptp resourceVersion: "23134" uid: 3a32a1b6-c86a-497b-8ee4-00d9973b2e8b spec: daemonNodeSelector: {} kind: List metadata: resourceVersion: ""
Expected results:
oc get ptpoperatorconfigs.ptp.openshift.io -A -o yaml apiVersion: v1 items: - apiVersion: ptp.openshift.io/v1 kind: PtpOperatorConfig metadata: creationTimestamp: "2023-04-13T16:30:58Z" generation: 1 name: default namespace: openshift-ptp resourceVersion: "23134" uid: 3a32a1b6-c86a-497b-8ee4-00d9973b2e8b spec: daemonNodeSelector: node-role.kubernetes.io/master: "" kind: List metadata: resourceVersion: ""
Additional info:
- is blocked by
-
OCPBUGS-11822 PtpOperatorsConfig not applying correctly
- Closed
- is duplicated by
-
OCPBUGS-11798 PtpOperatorsConfig not applying correctly
- Closed
- links to