-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.20
Description of problem:
Cloud event proxy for PTP operator doesn't parse the BF3 NIC names correctly. When the event is published the interface alias name within the "ResourceAddress\": \"/ cluster/node/helix97.telcoqe.eng.rdu2.dc.redhat.com/enP2s2f1npx/master\" isn't formatted correctly.
Version-Release number of selected component (if applicable):
ptp-operator.v4.20.0-202508041346
How reproducible:
100%
Steps to Reproduce:
1.Cause actions on PTP daemon that produce events with the interface alias.
Actual results:
'enP2s2f1npx'
Expected results:
'enP2s2fx'
Additional info:
"plugins/ptp_operator/utils/utils.go" GetAlias() func should be updated to handle more iface names, or at the very least BF3. Here are two BF3 iface names for unit testing, which should have the same output of 'enP2s2fx': enP2s2f0np0, enP2s2f1np1
- depends on
-
OCPBUGS-61518 Cloud event proxy for PTP operator doesn't parse the BF3 NIC names correctly
-
- Verified
-
- is cloned by
-
OCPBUGS-61518 Cloud event proxy for PTP operator doesn't parse the BF3 NIC names correctly
-
- Verified
-
-
OCPBUGS-61581 Linuxptp-daemon doesn't parse the BF3 NIC names correctly
-
- Verified
-
- relates to
-
OCPBUGS-61793 cloud-event-proxy: ptp sidecar is spamming error msg="Interface does not match Intel or Mellanox naming format, using original interface name"
-
- Verified
-
-
OCPBUGS-61830 ptp sidecar is spamming error msg="Interface does not match Intel or Mellanox naming format, using original interface name"
-
- Verified
-
- links to