With WPC card configured as GM or BC, phc2sys clock lock state is shown as FREERUN in ptp metrics while it should be LOCKED

When phc2sysOpts is configured in the GM ptp profile, ptp metrics show phc2sys as FREERUN. 

It is likely due to GM config does not have slave interface as per Aneesh.

# HELP openshift_ptp_clock_state 0 = FREERUN, 1 = LOCKED, 2 = HOLDOVER
# TYPE openshift_ptp_clock_state gauge
openshift_ptp_clock_state{iface="CLOCK_REALTIME",node="helix48.ptp.lab.eng.bos.redhat.com",process="phc2sys"} 0
openshift_ptp_clock_state{iface="ens5fx",node="helix48.ptp.lab.eng.bos.redhat.com",process="ptp4l"} 1
openshift_ptp_clock_state{iface="ens7fx",node="helix48.ptp.lab.eng.bos.redhat.com",process="ts2phc"} 1

4.13

100%

1. Configure GM on a cluster with phc2sysOpts
2. check ptp metrics
3.

openshift_ptp_clock_state for phc2sys is in FREERUN

openshift_ptp_clock_state should be in LOCKED state