-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.14
-
Important
-
No
-
CNF RAN Sprint 239, CNF RAN Sprint 240
-
2
-
False
-
-
Description of problem:
When deploying SNO spoke with ptp operator, policy violation is reported:
- eventName: ztp-install.helix48-group-du-sno-config-policy-26x9p.1768a7ba6ce9ad81
lastTimestamp: "2023-06-14T22:41:19Z"
message: 'NonCompliant;
violation - Error updating the object `default`, the error is `admission webhook "vptpoperatorconfig.kb.io"
denied the request: for HTTP transport, ptpEventConfig.storageType must be
set to the name of StorageClass providing persist storage`;
Configmap does exist, linuxptp-daemonlog is running, but no cloud-events container is present:
[kni@registry.kni-qe-28 ~]$ oc logs -n openshift-ptp linuxptp-daemon-n2x5m kube-rbac-proxy linuxptp-daemon-container
Adding storageType: "emptyDir" to ptpEventConfig causes cloud-events to be created and resolves the violation.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
100%
Steps to Reproduce:
1. Deploy RAN DU spoke cluster with ptp operator. PGT should specify PtpOperatorforConfigEvent as follows:
- fileName: PtpOperatorConfigForEvent.yaml
policyName: "post-config-policy"
spec:
ptpEventConfig:
enableEventPublisher: true
transportHost: http://ptp-event-publisher-service-NODE_NAME.openshift-ptp.svc.cluster.local:9043
2. Monitor spoke enforce policies for NonCompliance
3. Check linuxptp-daemonlog for cloud-events container
Actual results:
Policy violation, Error "ptpEventConfig.storageType must be set to the name of StorageClass providing persist storage", linuxptp-daemonlog pod lacks cloud-events container
Expected results:
ptpOperatorConfig with HTTP event config can be applied without specifying storageType. And default to use configmap.
Additional info:
