[action] [PR:14025] added log ignore to ignore BFD session creation failure logs. On mlnx…#14280
Merged
mssonicbld merged 1 commit intosonic-net:202405from Sep 2, 2024
Merged
Conversation
… platofrms, the syncd retries in sucha a case and passes. (sonic-net#14025)
8 tasks
Collaborator
Author
|
Original PR: #14025 |
Collaborator
Author
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On Mlnx paltforms, while running this test BFD session creation can fail sometime resulting in the following logs.
THe syncd retries in such a case and is able to create the BFD session subsequently. So these errors can be ignored.
E Jun 9 14:12:41.474573 strtk5-msn2700-06 ERR kernel: [35758.641097] sxd_kernel: [error] Failed to bind BFD socket to local_addr (ip:10.1.0.32 ,port:49171) (err:-98). E E Jun 9 14:12:41.474603 strtk5-msn2700-06 ERR kernel: [35758.760511] sxd_kernel: [error] Failed to create TX socket for session 8165 (err:-5). E E Jun 9 14:12:41.552788 strtk5-msn2700-06 ERR kernel: [35758.854304] sxd_kernel: [error] Parsing BFD command 0 failed (err:-5). E E Jun 9 14:12:41.553068 strtk5-msn2700-06 ERR syncd#SDK: [BFD.ERR] ioctl failed, error description: Input/output error E E Jun 9 14:12:41.553203 strtk5-msn2700-06 ERR syncd#SDK: [CORE_API.ERR] Failed in bfd_offload_set() , error: Internal Error E E Jun 9 14:12:41.553454 strtk5-msn2700-06 ERR syncd#SDK: [SAI_BFD.ERR] ./src/mlnx_sai_bfd.c[393]- mlnx_set_offload_bfd_tx_session: Error create TX BFD session: Internal Error. E E Jun 9 14:12:41.554748 strtk5-msn2700-06 ERR syncd#SDK: :- sendApiResponse: api SAI_COMMON_API_CREATE failed in syncd mode: SAI_STATUS_FAILURE E E Jun 9 14:12:41.555685 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_TYPE: SAI_BFD_SESSION_TYPE_ASYNC_ACTIVE E E Jun 9 14:12:41.555751 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_LOCAL_DISCRIMINATOR: 20 E E Jun 9 14:12:41.555792 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_UDP_SRC_PORT: 49171 E E Jun 9 14:12:41.555891 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_REMOTE_DISCRIMINATOR: 0 E E Jun 9 14:12:41.556028 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_BFD_ENCAPSULATION_TYPE: SAI_BFD_ENCAPSULATION_TYPE_NONE E E Jun 9 14:12:41.556076 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_IPHDR_VERSION: 4 E E Jun 9 14:12:41.556191 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_SRC_IP_ADDRESS: 10.1.0.32 E E Jun 9 14:12:41.556239 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_DST_IP_ADDRESS: 100.0.27.1 E E Jun 9 14:12:41.556322 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_MIN_TX: 1000000 E E Jun 9 14:12:41.556451 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_MIN_RX: 1000000 E E Jun 9 14:12:41.556451 strtk5-msn2700-06 ERR swss#orchagent: :- create: create status: SAI_STATUS_FAILURE E E Jun 9 14:12:41.556510 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_MULTIPLIER: 10 E E Jun 9 14:12:41.556549 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_TOS: 192 E E Jun 9 14:12:41.556627 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_MULTIHOP: true E E Jun 9 14:12:41.556669 strtk5-msn2700-06 ERR syncd#SDK: :- processQuadEvent: attr: SAI_BFD_SESSION_ATTR_VIRTUAL_ROUTER: oid:0x3000000000002Description of PR
Summary:
Fixes # (issue)
Type of change
Testfix
Back port request
Approach
What is the motivation for this PR?
This PR is added to ignore the BFD session creation failure messages as these messages lead to test failure due to unexpected logs. The Mlnx platform has the capability to retry the BFD session creation.The 2nd attempt passes and the test works fine,
In the event the platform fails to create the BFD session, the test would eventually fail so by ignoring these these logs we are not impacting the test itself.
How did you do it?
Added log ignore for these messages.
How did you verify/test it?
Ran this multiple times to check for failure.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation