upgrade ceos to version 4.25.5.1M, fix the issue of arista endless loop#4252
upgrade ceos to version 4.25.5.1M, fix the issue of arista endless loop#4252yejianquan wants to merge 9 commits intosonic-net:masterfrom
Conversation
|
please investigate the test error |
…pp (sonic-net#4228) Description of PR Summary: Fixes # (issue) Type of change Bug fix Testbed and Framework(new/improvement) Approach What is the motivation for this PR? cEOS containers' mgmt-ip occasionally unavaillable, upgrade cEOS image version will fix that cEOS terminal behavior slightly different from vEOS, enhance arista.py to avoid endless loop How did you do it? upgrade cEOS image version break loop if ssh connect returns merely an 'exit', as for other commands who relies on the return e.g. 'show interfaces po1 | json', 'exit' won't appear in input_buffer, so the change won't influence it. How did you verify/test it? Run platform_tests/test_advanced_reboot.py test on physical testbed and it didn't stuck again. Tried run command 'show interfaces po1 | json', it's not influenced. Co-authored-by: Jianquan Ye <[email protected]>
63a2e3c to
578af0d
Compare
1c8c09d to
255cd02
Compare
'show lacp neighbor' command is deprecated by 'show lacp peer', fixed |
|
Compatible with older EOS version by execute both 'show lacp neighbor' and 'show lacp peer', and select success returned one as result. So choose to execute all equivalent commands to have the most robust. |
255cd02 to
ddb1b3a
Compare
|
Something stuck platform_tests/test_advanced_reboot.py::test_warm_reboot, I'm investigating it. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
85797eb to
671348e
Compare
671348e to
6ff65a9
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
split into three prs to reduce the possible affection, close this one |
…atically (#25250) #### Why I did it src/sonic-utilities ``` * 0315da21 - (HEAD -> 202511, origin/202511) [LACP retry-count] Syntax Fix for Trixie (sonic-net#4280) (6 hours ago) [Yair Raviv] * 4420954e - Fix dump port state CLI command crash on multi-asic platforms (#4276) (5 days ago) [mssonicbld] * a3ad30be - [Mellanox] Add restricted sysfs list for fw control modules (sonic-net#4202) (13 days ago) [mssonicbld] * 16390921 - Fix j2 files not getting packaged (sonic-net#4252) (13 days ago) [mssonicbld] * 6b9b0dce - [hft]: HFT config/show cli (sonic-net#4243) (2 weeks ago) [mssonicbld] * 529b6479 - [sfputil] Fix issue: should not do low power mode or reset for non-present ports (sonic-net#4241) (2 weeks ago) [mssonicbld] * ad70c8f2 - Update bash completions for sonic-utilities commands (sonic-net#4234) (3 weeks ago) [mssonicbld] * 667f4b32 - [202511][GCU] Update WRED_PROFILE and BUFFER_POOL validators for GCU (sonic-net#4226) (3 weeks ago) [Dev Ojha] * 88b3899d - Fix sonic-kdump-config for running commands with pipe (sonic-net#4220) (3 weeks ago) [mssonicbld] * e4881b02 - Skip IP range duplicate check in validate_bgp_peer_group for different vnets (sonic-net#4215) (4 weeks ago) [mssonicbld] * 9c24925a - Fix syntax and semantic errors in kdump remote feature (sonic-net#4212) (4 weeks ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation