Unexpected openshift_ptp_clock_state metric added with status code 0 (FREERUN) after bringing down and up a ptp slave interface in boundary clock config. 

Before test:
# TYPE openshift_ptp_clock_state gauge
openshift_ptp_clock_state{iface="CLOCK_REALTIME",node="helix49.ptp.lab.eng.bos.redhat.com",process="phc2sys"} 1
openshift_ptp_clock_state{iface="eno1239x",node="helix49.ptp.lab.eng.bos.redhat.com",process="ptp4l"} 1

After test:
# TYPE openshift_ptp_clock_state gauge
openshift_ptp_clock_state{iface="CLOCK_REALTIME",node="helix49.ptp.lab.eng.bos.redhat.com",process="phc2sys"} 1
openshift_ptp_clock_state{iface="eno12399",node="helix49.ptp.lab.eng.bos.redhat.com",process="phc2sys"} 0
openshift_ptp_clock_state{iface="eno1239x",node="helix49.ptp.lab.eng.bos.redhat.com",process="ptp4l"} 1

4.10.52

100%

1. Configure boundary clock using 4.10 ptp
2. Ensure all the metrics look good before testing
3. ssh to DUT, and bring down a ptp slave interface
4. wait for FREE RUN ptp metric and events
5. bring up ptp slave interface

5. An extra metric gets added that indicates the ptp slave interface is in FREERUN state: 

openshift_ptp_clock_state{iface="eno12399",node="helix49.ptp.lab.eng.bos.redhat.com",process="phc2sys"} 0

5. The metric should not be added at all.

Did not see this issue in ptp 4.11 and 4.12.