Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2049092

Summary: when removing interface from ptp config - display on the metric as faulty and not removed.
Product: OpenShift Container Platform Reporter: obochan <obochan>
Component: NetworkingAssignee: Aneesh Puttur <aputtur>
Networking sub component: ptp QA Contact: obochan <obochan>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium    
Version: 4.10   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-24 15:57:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description obochan 2022-02-01 14:32:40 UTC 
Description of problem:

i edit the ptp config and remove the slave interface, and check the metric.
the interface i removed was still shown in the metrics with the status faulty.

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

obochan@obochan ptp]$ oc version
Client Version: 4.8.0
Server Version: 4.10.0-fc.1
Kubernetes Version: v1.23.0+50f645e

openshift-ptp                                      ptp-operator.4.10.0-202201210948             PTP Operator                                             4.10.0-202201210948              Succeeded




Steps to Reproduce:

1. oc -n openshift-ptp  edit ptpconfigs.ptp.openshift.io
2  remove one interface and save.
3  oc exec -n openshift-ptp  linuxptp-daemon-*** -c linuxptp-daemon-container -- curl 127.0.0.1:9091/metrics 
4. you will see the interface that was removed in faulty status

Actual results:

 interface that was removed in faulty status

Expected results:

 interface that was removed should be included.
Comment 1 Aneesh Puttur 2022-02-24 15:57:21 UTC 

*** This bug has been marked as a duplicate of bug 2043070 ***