When more than one ptp profiles are configured on a cluster, only one should be configured with phc2sys. 

However, even if we set phc2sysOpts to empty string for a second ptp config, ptp operator still keeps trying to start phc2sys. 

Error from ptp linux daemon log: 

E0209 17:11:12.127674   13194 daemon.go:487] cmdRun() error waiting for phc2sys: exit status 255
I0209 17:11:12.127946   13194 daemon.go:362] phc2sys[1675962672]:[phc2sys.3.config] PTP_PROCESS_STATUS:0I0209 17:11:12.138632   13194 daemon.go:501] Recreating phc2sys...
I0209 17:11:12.138676   13194 daemon.go:390] Starting phc2sys...
I0209 17:11:12.138681   13194 daemon.go:391] phc2sys cmd: /bin/chrt -f 10 /usr/sbin/phc2sys -f /var/run/phc2sys.2.config   
I0209 17:11:12.138929   13194 daemon.go:362] phc2sys[1675962672]:[phc2sys.2.config] PTP_PROCESS_STATUS:1autoconfiguration or valid source clock must be selected.usage: phc2sys [options]
 automatic configuration:
 -a             turn on autoconfiguration
 -r             synchronize system (realtime) clock
                repeat -r to consider it also as a time source
 manual configuration:
 -c [dev|name]  slave clock (CLOCK_REALTIME)
 -d [dev]       master PPS device
 -s [dev|name]  master clock
 -O [offset]    slave-master time offset (0)
 -w             wait for ptp4l
 common options:
 -f [file]      configuration file
 -E [pi|linreg] clock servo (pi)
 -P [kp]        proportional constant (0.7)
 -I [ki]        integration constant (0.3)
 -S [step]      step threshold (disabled)
 -F [step]      step threshold only on start (0.00002)
 -R [rate]      slave clock update rate in HZ (1.0)
 -N [num]       number of master clock readings per update (5)
 -L [limit]     sanity frequency limit in ppb (200000000)
 -M [num]       NTP SHM segment number (0)
 -u [num]       number of clock updates in summary stats (0)
 -n [num]       domain number (0)
 -x             apply leap seconds by servo instead of kernel
 -z [path]      server address for UDS (/var/run/ptp4l)
 -l [num]       set the logging level to 'num' (6)
 -t [tag]       add tag to log messages
 -m             print messages to stdout
 -q             do not print messages to the syslog
 -v             prints the software version and exits
 -h             prints this message and exitsE0209 17:11:12.140872   13194 daemon.go:487] cmdRun() error waiting for phc2sys: exit status 255
I0209 17:11:12.140893   13194 daemon.go:362] phc2sys[1675962672]:[phc2sys.2.config] PTP_PROCESS_STATUS:0ptp4l[53945.380]: [ptp4l.2.config] master offset         10 s2 freq  -97138 path delay       183
ptp4l[53945.381]: [ptp4l.3.config] master offset          1 s2 freq  -97155 path delay       179
ptp4l[53945.381]: [ptp4l.5.config] master offset          6 s2 freq  -96193 path delay       182
ptp4l[53945.386]: [ptp4l.1.config] master offset         -6 s2 freq   -9475 path delay       139
phc2sys[53945.410]: [ptp4l.0.config] CLOCK_REALTIME phc offset       -11 s2 freq   -3852 delay    510
ptp4l[53945.426]: [ptp4l.4.config] master offset          4 s2 freq  -96196 path delay       179

4.13 (does not happen with 4.12)

100%

1. deploy 4.13 ocp and du profiles via ZTP with more than 1 ptpconfigs
e.g., http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:3000/kni-qe/ztp-site-configs/src/helix49-4.13/policygentemplates/group-du-sno-ranGen.yaml#L181

2. check ptp logs

errors occurred when creating phc2sys for ptpconfig which has it unconfigured via phc2sysOpts: "".

phc2sys should not be started when unconfigured via phc2sysOpts