The current reference for ACM PG config for SNO RAN DU profile will not work for PTPConfigSlave CR
and probably affects other PTPConfigMaster/Slave CRs.

reference ACM PG for SNO:

https://github.com/openshift-kni/telco-reference/blob/379980fe3b1ba7e784f2543c6fa74f1d802b63d7/telco-ran/configuration/argocd/example/acmpolicygenerator/acm-group-du-sno-ranGen.yaml#L65C24-L65C38


Source CR:

https://github.com/openshift-kni/telco-reference/blob/379980fe3b1ba7e784f2543c6fa74f1d802b63d7/telco-ran/configuration/source-crs/PtpConfigSlave.yaml#L121

    recommend:
    - profile: "slave"
      priority: 4
      match:
      - nodeLabel: node-role.kubernetes.io/$mcp

ACM PG will not update $mcp

A solution is to specify the whole 'recommend' block in the ACM PG example:


        - path: source-crs/PtpConfigSlave.yaml
          patches:
            - metadata:
                name: du-ptp-slave
              spec:
                profile:
                # [...]
                recommend:
                  - profile: "slave"
                    priority: 4
                    match:
                     - nodeLabel: node-role.kubernetes.io/worker


    

    1. Deploy spoke cluster with RAN DU profile using example as is from reference configs
    2. Observe deployment
    3.
    

ACM PG does not update $mcp string in generated policy, resulting in non-working PTP config
    

Policy has the current nodeLabel value