-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20, 4.21
Description of problem:
Events do not clearly differentiate all interfaces for GNR-D, where multiple NICs all start with the same three letters ("eno"). Events are all shown as "enox"
In our test environment, there are 3 NICS:
eno1-eno8 is E825
eno16595 - eno16665 is E830
eno16495 - eno16565 is E830
[root@helix98 /]# ip addr | grep eno 2: eno5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 3: eno6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 4: eno7: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 5: eno8: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 6: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 7: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 8: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 9: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 10: eno16595: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 11: eno16605: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 12: eno16615: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 13: eno16625: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 14: eno16635: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 15: eno16645: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 16: eno16655: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 17: eno16665: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 18: eno16495: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 19: eno16505: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 20: eno16515: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 21: eno16525: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 22: eno16535: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 23: eno16545: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 24: eno16555: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 25: eno16565: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
To demonstrate this issue:
ptp is configured for one OC interface, eno16495. When the interface is taken down, cloud-event-proxy log is showing the event for "/cluster/node/helix98.telcoqe.eng.rdu2.dc.redhat.com/enox/master\"
time="2025-10-06T22:40:27Z" level=info msg="update interface eno16495 with portid 1 from role SLAVE to role FAULTY out ptp4l 7934.424 ptp4l.0.config port 1 (eno16495) SLAVE to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)" time="2025-10-06T22:40:27Z" level=info msg="master process name ptp4l and masteroffsetsource ptp4l" time="2025-10-06T22:40:27Z" level=debug msg="event source /sync/ptp-status/lock-state sent to queue to process" time="2025-10-06T22:40:27Z" level=debug msg="event sent {\n \"id\": \"188fbf92-98ea-48ad-8827-877841c36a76\",\n \"type\": \"event.sync.ptp-status.ptp-state-change\",\n \"source\": \"/sync/ptp-status/lock-state\",\n \"dataContentType\": \"application/json\",\n \"time\": \"2025-10-06T22:40:27.970298381Z\",\n \"data\": {\n \"version\": \"1.0\",\n \"values\": [\n {\n \"ResourceAddress\": \"/cluster/node/helix98.telcoqe.eng.rdu2.dc.redhat.com/enox/master\",\n \"data_type\": \"notification\",\n \"value_type\": \"enumeration\",\n \"value\": \"HOLDOVER\"\n },\n {\n \"ResourceAddress\": \"/cluster/node/helix98.telcoqe.eng.rdu2.dc.redhat.com/enox/master\",\n \"data_type\": \"metric\",\n \"value_type\": \"decimal64.3\",\n \"value\": \"0\"\n }\n ]\n }\n }"
This does not correctly indicate which interface/nic is showing a state change.
Expected results:
Event logs should all accurately reflect which interfaces are affected by state changes.