This is a clone of issue OCPBUGS-2970. The following is the description of the original issue:
—
Description of problem:
Currently all ptp configs in ZTP source-cr includes phc2sysOpts option, thus even if user did not include phc2sysOpts in user PGT, it will end up being added to spoke ptpconfigs.
For PTP dual nic feature, user need to create 2 ptpconfig but only 1 phc2sys should be running.

Suggest to add a new source-cr that is tailored for dual nic feature (modifying existing ptp source-crs may cause problems in upgrade because policies can become NonCompliant unexpectedly).

Version-Release number of selected component (if applicable):
4.11

How reproducible:
100%

Steps to Reproduce:
1. configure ptp with dual nic via PGT (one with phc2sysOpts, and one without)
http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:3000/kni-qe/ztp-site-configs/src/cnfde4-4.11/policygentemplates/group-du-sno-ranGen.yaml#L48-L248

2. deploy spoke using above config
3. Check ptp configs and ensure only 1 phyc2sys is running

Actual results:
3. phc2sysOpts is included in both ptpconfigs

Expected results:
3. For dual NIC configs, phc2sysOpts should not be added if user did not add it in PGT

Additional info:
Note "phc2sysOpts: -a -r -n 24" is not added by user, but by default source-cr.

[kni@registry.kni-qe-17 ~]$ oc get ptpconfigs.ptp.openshift.io -A
NAMESPACE NAME AGE
openshift-ptp du-ptp-bc1 38s
openshift-ptp du-ptp-bc2 38s
[kni@registry.kni-qe-17 ~]$ oc get ptpconfigs.ptp.openshift.io -A -o yaml |grep phc
phc2sysOpts: -a -r -n 24
phc2sysOpts: -a -r -m -n 24 -N 8 -R 16