With 4.15 SNO spoke deployed with Telco DU profile which includes workload partitioning enabled,
The sriov-network-config-daemon pod is not pinned to managment CPUs.

The pod is missing the WLP annotation:

target.workload.openshift.io/management: '{"effect":"PreferredDuringScheduling"}'

$ oc get pods -n openshift-sriov-network-operator sriov-network-config-daemon-8xhdq -o yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    kubectl.kubernetes.io/default-container: sriov-network-config-daemon
    openshift.io/scc: privileged
  creationTimestamp: "2023-12-05T09:30:07Z"
  generateName: sriov-network-config-daemon-
  [...]

    

    OCP 4.15.0-0.nightly-2023-12-04-162702
    sriov-network-operator.v4.15.0-202311291132
    

    Always
    

    1. Deploy SNO spoke with Telco DU profile applied.
    2. Check management pods for WLP annoations
    3.
    

    Pod is missing WLP annotation
$ oc get pods -n openshift-sriov-network-operator sriov-network-config-daemon-8xhdq -o yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    kubectl.kubernetes.io/default-container: sriov-network-config-daemon
    openshift.io/scc: privileged
  creationTimestamp: "2023-12-05T09:30:07Z"
  generateName: sriov-network-config-daemon-
  [...]

    

Pod should have WLP annotation, e.g:
$ oc get pods -n openshift-sriov-network-operator sriov-network-config-daemon-8xhdq -o yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    kubectl.kubernetes.io/default-container: sriov-network-config-daemon
    openshift.io/scc: privileged
    target.workload.openshift.io/management: '{"effect":"PreferredDuringScheduling"}'
  creationTimestamp: "2023-12-05T09:30:07Z"
  generateName: sriov-network-config-daemon-
  [...]
    

    Problem doesn't happen in 4.14.z