[ufi-202505-dev] Branch created from 202505#1
Closed
fengkm wants to merge 671 commits into
Closed
Conversation
…-net#22946) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it At the beginning of this year, we transitioned the PR testing approach in the sonic-mgmt repository from a classical model to an impacted area-based model. This new approach enables automatic collection of relevant test cases, eliminating the need for the previously hardcoded `pr_test_scripts.yaml` list, and we no longer maintain it. However, the sonic-buildimage repository has continued to use the classical PR testing model. As a result, any new test cases added in the sonic-mgmt repository are not picked up during PR testing in sonic-buildimage. This PR updates the sonic-buildimage repository to adopt the impacted area-based PR testing model. With this change, all relevant test cases—including newly added ones—will be properly included in the PR testing workflow. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it This PR updates the sonic-buildimage repository to adopt the impacted area-based PR testing model. With this change, all relevant test cases—including newly added ones—will be properly included in the PR testing workflow. #### How to verify it Test by pipeline itself, we can see that, the PR testing adopts the impacted area-based model and collect all relvent test cases. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it DHCPv4 per-interface counter is added by sonic-net/sonic-dhcpmon#36. Current PR is to add CLI to clear counter. HLD: sonic-net/SONiC#1861 ##### Work item tracking - Microsoft ADO **(number only)**: 32751348 #### How I did it 1. Rename `dockers/docker-dhcp-relay/cli/clear/plugins/clear_dhcp6relay_counter.py` to `dockers/docker-dhcp-relay/cli/clear/plugins/clear_dhcp_relay.py` due to it's not only for dhcp6relay 2. Add support for clear DHCPv4 per-interface counter 3. Add UTs #### How to verify it 1. Manually test by running `sudo sonic-clear dhcp_relay ipv4 counters` 2. UTs passed <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Added CMIS host mgmt to SN5600-O128. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Added config files to hwsku that enable CMIS host mgmt by default. #### How to verify it Deploy Mellanox-SN5600-O128 HwSKU on Mellanox SN5600 switch, and check that CMIS host mgmt is enabled <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…sonic-net#22959) #### Why I did it src/dhcpmon ``` * 9f93a22 - (HEAD -> 202505, origin/202505) Fix incorrect counting in for packets related to standby interface in dualtor (sonic-net#44) (2 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…6-64pe-o128 Add support for Arista-7060X6-64PE-B-O128 TH5-512
…tically (sonic-net#22923) #### Why I did it src/sonic-sairedis ``` * e1c4ff4d - (HEAD -> 202505, origin/202505) Revert "[nvidia] Skip SAI discovery on ports (sonic-net#1416)" (sonic-net#1611) (16 hours ago) [mssonicbld] * 718b27c6 - Fix PR testing issue caused by deprecation of Ubuntu 20.04 (sonic-net#1609) (4 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…lly (sonic-net#22907) #### Why I did it src/sonic-swss ``` * 3d0c46dd - (HEAD -> 202505, origin/202505) SRv6: set TTL decap mode to PIPE (sonic-net#3704) (2 days ago) [mssonicbld] * 4d5f5ea4 - [FC] Fix the cache to handle change in stats for the same object type (sonic-net#3702) (3 days ago) [mssonicbld] * 11e52bf3 - [tests]: Fix `test_MirrorDestMoveLag` test failure (sonic-net#3700) (4 days ago) [mssonicbld] * 3feb4c8e - Change Log Level for BFD Offload Capability Implementation (sonic-net#3697) (5 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
… automatically (sonic-net#22906) #### Why I did it src/sonic-platform-common ``` * 7b68cdb - (HEAD -> 202505, origin/202505) [Smartswitch] Add module specific pcie attach/detach functions for smartswitch platforms (sonic-net#576) (5 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Fixing sonic-net#21423 Handling cleanup of static routes on exit. When config reload is done, the static routes appear again eventhough they are not part of new configuration. Cleanup needs to be done so they are removed from FRR and kernel. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Handled cleanup of static routes on bgpcfgd exit. #### How to verify it Manually verified the scenario. Added UT to verify as well. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
… type (sonic-net#22979) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it To have QSFP+C module type in Mellanox media_settings.json #### How I did it - Added needed module with its supported applicationsץ - Update QSFP module to contain up to 4 lanes, as this is Quad SFP and supports up to 4 lanes. - Update all module types with '+' sign, with regex escape, so they would be detected in media_settings_parser. #### How to verify it - deploy image on SN4700 Mellanox switch. - enable cmis host mgmt. - make sure all Serdes SI parameters are valid. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…atically (sonic-net#22925) #### Why I did it src/sonic-utilities ``` * 6bd88046 - (HEAD -> 202505, origin/202505) Support reboot cause: Kernel Panic - Out of memory (sonic-net#3921) (2 days ago) [mssonicbld] * 28ae9cef - [db_migrator] Add version_202411_02 (sonic-net#3912) (5 days ago) [mssonicbld] * 4586e973 - [intfstat] Align output format between cached/non-cached scenarios (sonic-net#3913) (5 days ago) [mssonicbld] * 11b6fc0c - [Mellanox] Collect sai.xml to sysdump (sonic-net#3914) (5 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…D automatically (sonic-net#22960) #### Why I did it src/sonic-platform-daemons ``` * 7af427e - (HEAD -> 202505, origin/202505) Add Robust Exception Handling to pcied Daemon for Improved Stability (sonic-net#625) (3 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…-net#22985) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it We need skip frr_bmp since it's not container just bmp option used by bgpd from service checker. ##### Work item tracking sonic-net#22934 (comment) #### How I did it Skipp frr_bmp from feature table. #### How to verify it after frr_bmp feature is enabled, system-health cli does not report frr_bmp in "Not Running" line any more, other containers are not launched which are irrelevant to frr_bmp  <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…c-net#23014) Signed-off-by: anamehra [anamehra@cisco.com](mailto:anamehra@cisco.com) syseepromg access is slower than getting the mac from eth0 interface and profile.ini file when available. On Chassis supervisor as many swss services spawns around same time and each try to access DEVICE info via sonic-cfggen, these make parallel calls to syseepromg to fetch mac. This sometimes lows the response during high cpu utilization. For multi-asic namespace locations, mac is available from profile.ini and for others, eth0 should provide the correct mac. Limiting the syseeprom access only when the mac is not retrieved from these options. <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it On supervisor, sometimes syncd process start get delayed during boot when parallel swss processes try to access syseeprom to get mac which doing DEVICE_METADATA.localhost.platform call via sonic-cfggen. This in some rare instances causes swss failure when syncd is not ready within 1 min and responds back to INIT_VIEW. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it For multi-asic namespace locations, mac is available from profile.ini and for others, eth0 should provide the correct mac. Limiting the syseeprom access only when the mac is not retrieved from these options. #### How to verify it ``` root@yy39-lc5:/home/cisco# time sonic-cfggen -H -v DEVICE_METADATA.localhost.mac 8c:84:42:90:97:20 real 0m0.532s user 0m0.360s sys 0m0.064s root@yy39-lc5:/home/cisco# ifconfig eth0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 1.75.46.11 netmask 255.255.0.0 broadcast 1.75.255.255 inet6 fc0b::11 prefixlen 64 scopeid 0x0<global> inet6 fe80::8e84:42ff:fe90:9720 prefixlen 64 scopeid 0x20<link> ether 8c:84:42:90:97:20 txqueuelen 1000 (Ethernet) RX packets 7501239 bytes 889985239 (848.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8052387 bytes 646097128 (616.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…H5-64O and Nokia-IXR7220-D4-36D (sonic-net#22984) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Nokia adds support for the following Platforms and Hwskus: Platform: x86_64-nokia_ixr7220_d4-r0 Hwsku: Nokia-IXR7220-D4-36D Platform: x86_64-nokia_ixr7220_h5_64o-r0 Hwsku: Nokia-IXR7220-H5-64O ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it 1) Add new platform Nokia-IXR7220-D4-36D support and device data. platform string: x86_64-nokia_ixr7220_d4-r0 . Hwsku: Nokia-IXR7220-D4-36D 2) Add new platform Nokia-IXR7220-H5-64O. support and device data. platform string: x86_64-nokia_ixr7220_h5_64o-r0 . Hwsku: Nokia-IXR7220-H5-64O This PR requires PR sonic-net#21737 to pass the image build #### How to verify it Image build should be success. And install and run image on these 2 platforms. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 201811 - [ ] 201911 - [ ] 202006 - [ ] 202012 - [ ] 202106 - [ ] 202111 - [ ] 202205 - [ ] 202211 - [ ] 202305 - [x] 202411 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it When the kdump remote feature is enabled by the user, a kernel crash results in an attempt to send the crash report file to an SSH server. However, the network interfaces are down, leading to a "Network Unreachable" error. To resolve this issue, I have added custom scripts to ensure the network interfaces are up and configured correctly during the kdump process. #### How I did it Added network_setup.sh and network_setup.hook file #### How to verify it After this change, the remote SSH kdump file transfer would be possible because a network not reachable issue arose as the default crash kernel image did not change the state of the interfaces to "UP" upon load. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide a tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. -->
…ly (sonic-net#23041) #### Why I did it src/dhcprelay ``` * 3ac08b5 - (HEAD -> 202505, origin/202505) [ci] Upgrade agent pool from ubuntu 20.04 to latest. (sonic-net#70) (21 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…atically (sonic-net#23017) #### Why I did it src/sonic-utilities ``` * 77f05319 - (HEAD -> 202505, origin/202505) Skip checking offload flags for static routes/sids in route check and add check_sids (sonic-net#3924) (3 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…tically (sonic-net#23002) #### Why I did it src/sonic-sairedis ``` * d79bc6da - (HEAD -> 202505, origin/202505) [TAM]: Fix TAM notification and vslib implementation (sonic-net#1615) (4 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
… automatically (sonic-net#23032) #### Why I did it src/sonic-platform-common ``` * cdc9157 - (HEAD -> 202505, origin/202505) [cmis] add read only cache decorator (sonic-net#577) (3 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…igate timeout issues (sonic-net#22992) Why I did it reference: sonic-net#22969 * update pr test pipeline default timeout to 8 hours Signed-off-by: Chun'ang Li <chunangli@microsoft.com> --------- Signed-off-by: Chun'ang Li <chunangli@microsoft.com>
…atically (sonic-net#23050) #### Why I did it src/sonic-utilities ``` * f382bfdc - (HEAD -> 202505, origin/202505) [multi-asic] Fix the 'config reload' flow in case when multiple golden_config.json files provided (sonic-net#3927) (23 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…tically (sonic-net#23049) #### Why I did it src/sonic-sairedis ``` * c7c2692a - (HEAD -> 202505, origin/202505) [TAM]: Add default SAI_TAM_ATTR_TELEMETRY_OBJECTS_LIST of TAM for saivs create operation (sonic-net#1616) (18 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Building for pensando now requires access to a private repo that is currently not available. ##### Work item tracking - Microsoft ADO **(number only)**: 33407145 #### How I did it #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Upgrade xgs SAI to 13.2.0.4 to include the following fixes: - 13.2.0.3: [CS00012408290]Memleak observed in SDK-6.5.32. - 13.2.0.4: [CS00012408922]TH5-512 - SAI INIT is taking 39 Sec with 512x100G configuration ##### Work item tracking - Microsoft ADO **(number only)**: 33386618 #### How I did it Update xgs SAI version in sai.mk file. #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [x] 202412 - [x] 202505 Signed-off-by: zitingguo-ms <zitingguo@microsoft.com>
…utomatically (sonic-net#22660) #### Why I did it src/sonic-host-services ``` * 0206da1 - (HEAD -> 202505, origin/202505) Revert "[featured] fix non existing feature start (sonic-net#234)" (sonic-net#273) (51 minutes ago) [mssonicbld] * d4d624e - Add iptables rules to drop all bgp packets destined for loopback1 IP addresses in dual ToR (sonic-net#269) (10 days ago) [mssonicbld] * 93db579 - Fix PyGObject required version (sonic-net#265) (2 weeks ago) [mssonicbld] * 112acad - [build] Update Azure pipeline to use Ubuntu 24.04 image (sonic-net#266) (2 weeks ago) [mssonicbld] * 1ee792e - Implement Download and Delete For File Service (sonic-net#242) (5 weeks ago) [Dawei Huang] * 00393e3 - [kdump-config] Update kdump default config with pre-defined value in /proc/cmdline (installer.conf) (sonic-net#237) (7 weeks ago) [Marty Y. Lok] * d028745 - [Radius] Add require_message_authenticator option to fix BlastRadius issue. (sonic-net#172) (7 weeks ago) [Julian Chang] * 8237b5d - Monitor rsyslog feature flag change and update rsyslog config by restart rsyslog-config service (sonic-net#245) (7 weeks ago) [Hua Liu] * 55cee71 - Improve Detection Logic for HALT Command in is_halt_command_running() (sonic-net#247) (8 weeks ago) [Vasundhara Volam] * 29b8be8 - [featured] fix non existing feature start (sonic-net#234) (3 months ago) [Stepan Blyshchak] * fe90cb1 - Adding support for filtering by destination IP and/or incoming interface to caclmgrd. (sonic-net#195) (3 months ago) [nyanto] * 6006e05 - caclmgrd interface rules patch 1 (sonic-net#197) (3 months ago) [Nanma Purushotam] * 3ba0c59 - Pin PyGObject to 3.50.0 (sonic-net#228) (3 months ago) [cpackham-atlnz] * 5445cf6 - Radius Access request to use configured src interface (sonic-net#230) (3 months ago) [lakshmi-nexthop] ``` #### How I did it #### How to verify it #### Description for the changelog
Ported the fix FRRouting/frr#18601 from FRR community Tested using static routes, save and reboot. K>* 0.0.0.0/0 [0/0] via 10.59.128.1, eth0, 00:03:58 L failure_prs.log 1.1.1.1/32 is directly connected, Loopback0, 00:03:52 C>* 1.1.1.1/32 is directly connected, Loopback0, 00:03:52 C>* 10.59.128.0/20 is directly connected, eth0, 00:03:58 L> 10.59.142.159/32 is directly connected, eth0, 00:03:58 C>* 11.1.0.0/16 is directly connected, vsh0, 00:03:58 L> 11.1.22.238/32 is directly connected, vsh0, 00:03:58 C>* 20.1.1.0/24 is directly connected, Ethernet0, 00:02:22 L> 20.1.1.2/32 is directly connected, Ethernet0, 00:02:22 S>* 40.1.1.1/32 [1/0] is directly connected, Ethernet0, weight 1, 00:00:16 S>* 40.1.1.2/32 [1/0] is directly connected, Ethernet0, weight 1, 00:00:02 <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 201811 - [ ] 201911 - [ ] 202006 - [ ] 202012 - [ ] 202106 - [ ] 202111 - [ ] 202205 - [ ] 202211 - [ ] 202305 #### Tested branch (Please provide the tested image version) FRR 10.0.1
…lly (sonic-net#23003) #### Why I did it src/sonic-swss ``` * bc1a9bce - (HEAD -> 202505, origin/202505) Merge pull request sonic-net#3706 from prabhataravind/paravind/202505 (4 days ago) [Jianquan Ye] |\ | failure_prs.log skip_prs.log d89b4801 - Add more mock tests for coverage (5 days ago) [Prabhat Aravind] | failure_prs.log skip_prs.log a181b5d9 - Orchagent SAI error handling improvements (5 days ago) [Prabhat Aravind] |/ * 50048e78 - Changes to unblock swss pipeline tests (sonic-net#3708) (5 days ago) [prabhataravind] * 7e15cce2 - Install symlink to Python 3 to work around AzP diff coverage issue (sonic-net#3710) (6 days ago) [mssonicbld] * fd336545 - [ci]: Skip publishing of asan vstest summary (sonic-net#3711) (6 days ago) [mssonicbld] * 1ea80065 - [build] Support optionally using other container registries instead of DockerHub (sonic-net#3709) (6 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…D automatically (sonic-net#23001) #### Why I did it src/sonic-platform-daemons ``` * 8ec7295 - (HEAD -> 202505, origin/202505) xcvrd: Remove SFP API object when SFP is removed (sonic-net#627) (4 days ago) [mssonicbld] * 6794d8a - [Smartswitch] Fix incorrect reporting of data plane and control plane by DPU (sonic-net#626) (6 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it When a route with 512 nexthops is programmed, show ipv6 route shows the route as queued, even though the route gets programmed in the hardware. Porting the fix FRRouting/frr#18919 from FRR as well as aligning dplane_fpm_sponic ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Modifying dplane_fpm_sonic and added patches. #### How to verify it Install routes with 512 nexthops and confirm if they are not queued. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…tect.sh script (sonic-net#23885) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it asic_detect.sh script was added in this PR - sonic-net#23458. It uses lspci command, which can be used only if pciutils package is installed. Syncd docker started to use asic_detect.sh script by this PR - sonic-net/sonic-sairedis#1633 So, syncd of Mellanox and nvidia-bluefield must have pciutils installed. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Added pciutils installation in syncd Dockerfile #### How to verify it Make sure pciutils package is installed in Mellanox switch syncd docker <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…23884) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it To support location_type attribute in DEVICE_METADATA. Sample config: ``` "DEVICE_METADATA": { "localhost": { "bgp_asn": "65100", "buffer_model": "traditional", "cloudtype": "Public", "default_bgp_status": "down", "default_pfcwd_status": "enable", "deployment_id": "1", "docker_routing_config_mode": "separated", "hostname": "bjw2-can-7050c-3", "hwsku": "Arista-7050CX3-32C-S128", "location_type": "Edge", "mac": "68:bf:6c:ad:99:30", "platform": "x86_64-arista_7050cx3_32c", "region": "None", "synchronous_mode": "enable", "timezone": "UTC", "type": "MgmtLeafRouter", "yang_config_validation": "disable" } } ``` ##### Work item tracking - Microsoft ADO **(number only)**: 34655035 #### How I did it Update Yang model. #### How to verify it Verified by unit test. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
sonic-net#23888) #### Why I did it src/linkmgrd ``` * afa62a6 - (HEAD -> 202505, origin/202505) Fix mux port `uninitialized` (sonic-net#311) (3 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…lly (sonic-net#23880) #### Why I did it src/sonic-swss ``` * c0d4be07 - (HEAD -> 202505, origin/202505) Merge pull request sonic-net#3843 from rajkumar1-arista/temp-disable-bulk-req-for-port-cntrs (5 minutes ago) [Jianquan Ye] |\ | failure_prs.log skip_prs.log 354a6313 - minor comment corrections (8 days ago) [rajkumar1] | failure_prs.log skip_prs.log 6720e69f - minor comment corrections (11 days ago) [rajkumar1] | failure_prs.log skip_prs.log a18ffeec - Disable bulk requests for PORT counters (12 days ago) [rajkumar1] * f5c6e021 - [Mux] Clear bulkers when rolling back mux switchover (sonic-net#3855) (4 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…CX3-32C-C28S16 (sonic-net#23895) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it This is the issue tracked in https://github.com/aristanetworks/sonic-qual.msft/issues/701 ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it This PR fixes this issue by fixing the configuration of `Arista-7050CX3-32S-C28S16` and `Arista-7050CX3-32C-C28S16`, based on the configuration of other HWSKUs for the same platforms. #### How to verify it Verified the `routeCheck` is OK with this change, e.g. ``` Monit 5.20.0 uptime: 3h 59m Program 'routeCheck' status Status ok monitoring status Waiting monitoring mode active on reboot start last exit value 0 last output - data collected Thu, 28 Aug 2025 16:28:50 ``` <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [x] 202505 #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…utomatically (sonic-net#23899) #### Why I did it src/sonic-host-services ``` * bf1eb69 - (HEAD -> 202505, origin/202505) [202505] Backport: [reboot-cause] Use UTC to ensure consistent sorting (sonic-net#303) (4 minutes ago) [Jianyue Wu] ``` #### How I did it #### How to verify it #### Description for the changelog
…D automatically (sonic-net#23896) #### Why I did it src/sonic-platform-daemons ``` * 77c70bd - (HEAD -> 202505, origin/202505) xcvrd: gate config publish on syncd.restore_count = 1 (instead of system warm-reboot flag) to prevent post-warm-reboot port flaps (sonic-net#671) (18 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…atically (sonic-net#23905) #### Why I did it src/sonic-utilities ``` * 1761a749 - (HEAD -> 202505, origin/202505) [spm] Rename entry tag variable to docker_image_reference (sonic-net#4050) (2 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…D automatically (sonic-net#23915) #### Why I did it src/sonic-platform-daemons ``` * c5e545e - (HEAD -> 202505, origin/202505) [202505] [xcvrd] Improve logging in case of unable to find appropriate match for optic SI settings (sonic-net#672) (sonic-net#673) (38 minutes ago) [mihirpat1] ``` #### How I did it #### How to verify it #### Description for the changelog
…D automatically (sonic-net#23921) #### Why I did it src/sonic-platform-daemons ``` * 1db213b - (HEAD -> 202505, origin/202505) Revert "xcvrd: gate config publish on syncd.restore_count = 1 (instead of sys…" (sonic-net#675) (4 minutes ago) [Jianquan Ye] ``` #### How I did it #### How to verify it #### Description for the changelog
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Upgrade xgs SAI version to 13.2.1.3 to include the following fix: - [CS00012421016/CS00012421247]: bypass returning error log and error code for accessing trim disabled queue. Sonic currently doesnot have means to avoid accessing invalid trim queues and customer wants to return zero as value of counter. Added the bypass logic under a feat logic. ##### Work item tracking - Microsoft ADO **(number only)**: 34764822 #### How I did it Update sai.mk file. #### How to verify it Signed-off-by: zitingguo-ms <zitingguo@microsoft.com>
…D automatically (sonic-net#23929) #### Why I did it src/sonic-platform-daemons ``` * f661d74 - (HEAD -> 202505, origin/202505) pulling into 202505 (sonic-net#677) (35 minutes ago) [Gregory Boudreau] ``` #### How I did it #### How to verify it #### Description for the changelog
…ght and dark modes (sonic-net#23935) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it The `show platform pcieinfo -c` command fails for Mellanox smartswitch platforms on all DPU power off. This is because the PCIE devices relevant to the DPUs are removed on power off / reboot. During this time there is a state db entry added to indicate that the DPU is being powered off. So we are querying this information to indicate whether the DPU relevant PCIE devices are present or not, if the PCIE devices are not present, and they are relevant for the DPU, we remove the entry from the pcie devices being checked ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Changed pcie.py platform specific implementation to remove the entries relevant to PCIE when it detects the `PCIE_DETACH_INFO` fields in state db. If these keys are detected with the right dpu_state. We do not append these entries to the returned configuration info #### How to verify it Unit test results: ``` tests/test_pcie.py::TestPcie::test_get_pcie_check PASSED [ 20%] tests/test_pcie.py::TestPcie::test_get_pcie_check_bluefield_detaching PASSED [ 40%] tests/test_pcie.py::TestPcie::test_get_pcie_check_bluefield_not_detaching PASSED [ 60%] tests/test_pcie.py::TestPcie::test_get_pcie_check_bluefield_db_error PASSED [ 80%] tests/test_pcie.py::TestPcie::test_create_device_id_to_bus_map PASSED [100%] ``` Before fix the failure is detected on DPU Power Off: ``` root@sonic:/usr# show platform pcieinfo -c | grep Failed PCI Device: Ethernet controller: Mellanox Technologies MT43244 BlueField-3 integrated ConnectX-7 network controller (rev 01) [Failed] PCI Device: DMA controller: Mellanox Technologies MT43244 BlueField-3 SoC Management Interface (rev 01) [Failed] PCI Device: Ethernet controller: Mellanox Technologies MT43244 BlueField-3 integrated ConnectX-7 network controller (rev 01) [Failed] PCI Device: DMA controller: Mellanox Technologies MT43244 BlueField-3 SoC Management Interface (rev 01) [Failed] PCI Device: Ethernet controller: Mellanox Technologies MT43244 BlueField-3 integrated ConnectX-7 network controller (rev 01) [Failed] PCI Device: DMA controller: Mellanox Technologies MT43244 BlueField-3 SoC Management Interface (rev 01) [Failed] PCI Device: Ethernet controller: Mellanox Technologies MT43244 BlueField-3 integrated ConnectX-7 network controller (rev 01) [Failed] PCI Device: DMA controller: Mellanox Technologies MT43244 BlueField-3 SoC Management Interface (rev 01) [Failed] ``` After fix ``` root@sonic:/usr# show platform pcieinfo -c | grep Failed root@sonic:/usr# ``` <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [X] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…ia_settings.json` (sonic-net#23942) Workaround for sonic-net#21902 SWSS startup causes APPL_DB to be flushed. This results in `PORT_TABLE:Ethernet#` losing it's media_settings tunings populated by XCVRD. Without this change (tuning lost): ``` sonic-db-cli -n asic0 APPL_DB hgetall "PORT_TABLE:Ethernet96" {'alias': 'Ethernet13/1', 'asic_port_name': 'Eth96', 'core_id': '0', 'core_port_id': '13', 'index': '13', 'lanes': '40,41,42,43', 'num_voq': '8', 'role': 'Ext', 'speed': '100000', 'admin_status': 'up', 'description': 'ARISTA13T3:Ethernet1', 'fec': 'none', 'mtu': '9100', 'pfc_asym': 'off', 'tpid': '0x8100', 'oper_stat us': 'up', 'flap_count': '1', 'main': '0x4e,0x4e,0x53,0x4b', 'post1': '0xffffffea,0xffffffea,0xffffffea,0xffffffec', 'post2': '0x0,0x0,0x0,0x0', 'post3': '0x0,0x0,0x0,0x0', 'pre1': '0xfffffffb,0xfffffffb,0xfffffffb,0xfffffffb', 'pre2': '0x0,0x0,0x0,0x0', 'last_up_time': 'Thu Apr 03 16:32:03 2025'} systemctl restart swss@0.service sonic-db-cli -n asic0 APPL_DB hgetall "PORT_TABLE:Ethernet96" {'alias': 'Ethernet13/1', 'asic_port_name': 'Eth96', 'core_id': '0', 'core_port_id': '13', 'index': '13', 'lanes': '40,41,42,43', 'num_voq': '8', 'role': 'Ext', 'speed': '100000', 'admin_status': 'up', 'description': 'ARISTA13T3:Ethernet1', 'fec': 'none', 'mtu': '9100', 'pfc_asym': 'off', 'tpid': '0x8100', 'oper_stat us': 'up', 'flap_count': '1', 'last_up_time': 'Thu Apr 03 17:41:08 2025'} ``` With this change (tuning preserved): ``` sonic-db-cli -n asic0 APPL_DB hgetall "PORT_TABLE:Ethernet96" {'alias': 'Ethernet13/1', 'asic_port_name': 'Eth96', 'core_id': '0', 'core_port_id': '13', 'index': '13', 'lanes': '40,41,42,43', 'num_voq': '8', 'role': 'Ext', 'speed': '100000', 'admin_status': 'up', 'description': 'ARISTA13T3:Ethernet1', 'fec': 'none', 'mtu': '9100', 'pfc_asym': 'off', 'tpid': '0x8100', 'oper_stat us': 'up', 'flap_count': '1', 'main': '0x4e,0x4e,0x53,0x4b', 'post1': '0xffffffea,0xffffffea,0xffffffea,0xffffffec', 'post2': '0x0,0x0,0x0,0x0', 'post3': '0x0,0x0,0x0,0x0', 'pre1': '0xfffffffb,0xfffffffb,0xfffffffb,0xfffffffb', 'pre2': '0x0,0x0,0x0,0x0', 'last_up_time': 'Thu Apr 03 16:32:03 2025'} systemctl restart swss@0.service sonic-db-cli -n asic0 APPL_DB hgetall "PORT_TABLE:Ethernet96" {'alias': 'Ethernet13/1', 'asic_port_name': 'Eth96', 'core_id': '0', 'core_port_id': '13', 'index': '13', 'lanes': '40,41,42,43', 'num_voq': '8', 'role': 'Ext', 'speed': '100000', 'admin_status': 'up', 'description': 'ARISTA13T3:Ethernet1', 'fec': 'none', 'mtu': '9100', 'pfc_asym': 'off', 'tpid': '0x8100', 'oper_stat us': 'up', 'flap_count': '1', 'main': '0x4e,0x4e,0x53,0x4b', 'post1': '0xffffffea,0xffffffea,0xffffffea,0xffffffec', 'post2': '0x0,0x0,0x0,0x0', 'post3': '0x0,0x0,0x0,0x0', 'pre1': '0xfffffffb,0xfffffffb,0xfffffffb,0xfffffffb', 'pre2': '0x0,0x0,0x0,0x0', 'last_up_time': 'Fri Apr 04 17:12:59 2025'} ``` I also see the message in syslog that xcvrd is restarted right after the dbs are flushed: ``` NOTICE root: Chassis db clean up for swss0. Number of SYSTEM_LAG_TABLE entries deleted: 2 NOTICE root: Restarting pmon service... NOTICE pmon#xcvrd[5016]: Stop daemon main loop INFO pmon#supervisord 2025-07-11 20:27:09,608 INFO waiting for xcvrd to stop NOTICE pmon#xcvrd[5016]: CMIS: Stopped NOTICE pmon#DomInfoUpdateTask[5016]: Stop event generated during DOM monitoring loop NOTICE pmon#DomInfoUpdateTask[5016]: Stop DOM monitoring loop NOTICE pmon#python3: :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: STATE_DB NOTICE pmon#python3: message repeated 7 times: [ :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: STATE_DB] NOTICE pmon#python3: :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: APPL_DB NOTICE pmon#python3: :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: APPL_DB NOTICE pmon#python3: :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: CONFIG_DB NOTICE pmon#python3: :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: CONFIG_DB NOTICE pmon#python3: :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: STATE_DB NOTICE pmon#python3: message repeated 65 times: [ :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: STATE_DB] NOTICE pmon#python3: :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: CONFIG_DB NOTICE pmon#python3: :- ~RedisPipeline: RedisPipeline dtor is called from another thread, possibly due to exit(), Database: STATE_DB INFO pmon#supervisord 2025-07-11 20:27:11,572 INFO stopped: xcvrd (exit status 0) INFO pmon#supervisord 2025-07-11 20:27:11,575 INFO spawned: 'xcvrd' with pid 5069 NOTICE pmon#xcvrd[5069]: Starting up... NOTICE pmon#xcvrd[5069]: XCVRD INIT: Start daemon init... NOTICE pmon#xcvrd[5069]: XCVRD INIT: Wait for port config is done INFO pmon#supervisord 2025-07-11 20:27:21,590 INFO success: xcvrd entered RUNNING state, process has stayed up for > than 10 seconds (startsecs) INFO swss.sh[747370]: xcvrd: stopped INFO swss.sh[747370]: xcvrd: started ``` #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 201811 - [ ] 201911 - [ ] 202006 - [ ] 202012 - [ ] 202106 - [ ] 202111 - [ ] 202205 - [ ] 202211 - [ ] 202305 - [x] msft-202503
#### Why I did it New prober_type harware is being added to linkmgrd. This is config knob yang addition for the specific field in mUX_CABLE ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 201811 - [ ] 201911 - [ ] 202006 - [ ] 202012 - [ ] 202106 - [ ] 202111 - [ ] 202205 - [ ] 202211 - [ ] 202305 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
…D automatically (sonic-net#23959) #### Why I did it src/sonic-platform-daemons ``` * c0b9ec6 - (HEAD -> 202505, origin/202505) Handle restore_count and system_enable ”NoneType“ value scenario. (sonic-net#680) (6 hours ago) [ryanzhu706] ``` #### How I did it #### How to verify it #### Description for the changelog
…atically (sonic-net#23998) #### Why I did it src/sonic-utilities ``` * 1203b0b1 - (HEAD -> 202505, origin/202505) Add Arista-7060X6-64PE-B-O128S2, Arista-7060X6-16PE-384C-B-O128S2 to GCU (sonic-net#4058) (17 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…lly (sonic-net#23997) #### Why I did it src/sonic-swss ``` * badf36fa - (HEAD -> 202505, origin/202505) fpmsyncd crashes during execution of sonic-mgmt script vxlan/test_vnet_bgp_route_precedence.py (sonic-net#3880) (15 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…sonic-net#23996) #### Why I did it src/dhcpmon ``` * 6aa29ed - (HEAD -> 202505, origin/202505) [init] Init physical interfaces without portchannel in counter (sonic-net#54) (20 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…alidation (sonic-net#24000) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Change VXLAN tunnel YANG model to support 2 tunnels + string validation. This is to allow for newer validation in production. ##### Work item tracking - Microsoft ADO **(number only)**: 33013419 #### How I did it Modify vxlan tunnel list model and add unit tests #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [X] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> Change VXLAN tunnel YANG model to support 2 tunnels + string validation <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
Why I did it Updating cisco-8000-smartswitch.ini file signed-off-by: jianquanye@microsoft.com
…-net#24002) #### Why I did it platform_tests/api/test_component.py was failing due to the hard coded component name in the corresponding platform.json file not matching the component name retrieved from the Arista platform information API. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Changed the component name in the platform.json file to match our platform information API. #### How to verify it Ran the test with and without the change, confirmed that it passes with the change. #### Which release branch to backport (provide reason below if selected) - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202505 #### Tested branch (Please provide the tested image version) - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog #### Link to config_db schema for YANG module changes #### A picture of a cute animal (not mandatory but encouraged)
fengkm
marked this pull request as draft
September 16, 2025 05:52
fengkm
pushed a commit
that referenced
this pull request
Feb 3, 2026
#### Why I did it If one python wheel is already installed inside slave container, it will not install again. Below is a sample log: ``` sed: -e expression #1, char 11: extra characters after command WARNING: The directory '/var/user/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag. Processing ./target/python-wheels/bookworm/sonic_yang_models-1.0-py3-none-any.whl sonic-yang-models is already installed with the same version as the provided wheel. Use --force-reinstall to force an installation of the wheel. WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. [notice] A new release of pip is available: 24.2 -> 25.3 [notice] To update, run: python3 -m pip install --upgrade pip Build end time: Wed Dec 3 22:53:07 UTC 2025 Elapsed time: 0h 0m 1s ``` However, we expect to reinstall the python wheel for target `$(PYTHON_WHEELS_PATH)/%-install` ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Update slave.mk to enasure force install the python wheel. #### How to verify it After this change, local build will successfully force install the python wheel. See new logs: ``` sed: -e expression #1, char 11: extra characters after command WARNING: The directory '/var/qiluo/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag. Processing ./target/python-wheels/bookworm/sonic_yang_models-1.0-py3-none-any.whl Installing collected packages: sonic-yang-models Attempting uninstall: sonic-yang-models Found existing installation: sonic-yang-models 1.0 Uninstalling sonic-yang-models-1.0: Successfully uninstalled sonic-yang-models-1.0 Successfully installed sonic-yang-models-1.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. [notice] A new release of pip is available: 24.2 -> 25.3 [notice] To update, run: python3 -m pip install --upgrade pip Build end time: Wed Dec 3 23:59:31 UTC 2025 ```
fengkm
pushed a commit
that referenced
this pull request
Feb 3, 2026
…logs The `imklog` plugin of rsyslog collects the kernel logs from `/dev/kmsg` and enqueues it to the syslog. With `CONFIG_PRINTK_TIME` the kernel messages are by default prefixed with the elapsed time since boot. The `imklog` plugin parsing these messages have a few options such as to keep the timestamps as such or to interpret and adjust the syslog's reported time accordingly. The rsylog release `8.2312.0` has fixes in interpreting these timestamps, leading to the change in behavior observed in sonic-net#24386. https://salsa.debian.org/debian/rsyslog/-/blob/debian/8.2504.0-1/ChangeLog?ref_type=tags#L619 To restore the earlier behavior or retaining the kernel reported elapsed time, disable `KlogParseKernelTimestamp` as this leads to removal of timestamp from kernel messages and enable `KlogKeepKernelTimestamp` explicitly. The later is required as the default is now to discard the kernel timestamp. With this change, the logs retain the kernel timestamp: root@sonic:~# cat /var/log/syslog | grep "sonic.*kernel:" | head -n 3 2025 Nov 4 05:15:14.918946 sonic NOTICE kernel: [ 0.000000] Linux version 6.12.41+deb13-sonic-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian 6.12.41-1 (2025-08-12) 2025 Nov 4 05:15:14.919533 sonic INFO kernel: [ 0.000000] Command line: BOOT_IMAGE=/image-trixie.0-dirty-20251102.122837/boot/vmlinuz-6.12.41+deb13-sonic-amd64 root=UUID=ac0b6826-f8a3-461f-a8ff-701df60d90b6 rw console=tty0 console=ttyS0,115200n8 quiet processor.max_cstate=1 intel_idle.max_cstate=0 net.ifnames=0 biosdevname=0 loop=image-trixie.0-dirty-20251102.122837/fs.squashfs loopfstype=squashfs apparmor=1 security=apparmor varlog_size=4096 usbcore.autosuspend=-1 intel_iommu=off modprobe.blacklist=gpio_ich,i2c-ismt,i2c_ismt,i2c-i801,i2c_i801 crashkernel=0M-2G:256M,2G-4G:320M,4G-8G:384M,8G-:448M acpi_no_watchdog 2025 Nov 4 05:15:14.919536 sonic INFO kernel: [ 0.000000] BIOS-provided physical RAM map: root@sonic:~# cat /var/log/syslog | grep "sonic.*kernel:" | tail -n 3 2025 Nov 4 05:17:26.831607 sonic WARNING kernel: [ 143.527486] PDDF_LED set_status_led: Set [FANTRAY_LED;1] color[green] 2025 Nov 4 05:17:26.912442 sonic WARNING kernel: [ 143.607086] PDDF_LED set_status_led: Set [FANTRAY_LED;2] color[green] 2025 Nov 4 05:20:32.499634 sonic WARNING kernel: [ 329.195319] PDDF_LED set_status_led: Set [SYS_LED;0] color[amber] root@sonic:~# Signed-off-by: Ramasamy Chandramouli <rachandr@celestica.com> Co-authored-by: Ramasamy Chandramouli <rachandr@celestica.com>
fengkm
pushed a commit
that referenced
this pull request
May 12, 2026
…net#25643) * [build] Add build timing report and dependency analysis tools Add three scripts for build performance instrumentation: - scripts/build-timing-report.sh: Parse per-package timing from build logs (HEADER/FOOTER timestamps), generate sorted duration table, phase breakdown, parallelism timeline, and CSV export. - scripts/build-dep-graph.py: Parse rules/*.mk dependency graph, compute critical path, fan-out/fan-in bottleneck analysis, and generate DOT/JSON output for visualization. - scripts/build-resource-monitor.sh: Sample CPU, memory, disk I/O, and Docker container count during builds for resource utilization analysis. Add "make build-report" target to slave.mk that runs the timing report and dependency analysis after a build completes. Example output from a VS build on 24-core/30GB machine: - 210 packages built in 53m wall time (173m CPU) - Max concurrency: 5 (with SONIC_CONFIG_BUILD_JOBS=4) - Critical path: 14 packages deep (libnl -> libswsscommon -> utilities) - Top bottleneck: LIBSWSSCOMMON with 48 downstream dependents Signed-off-by: Rustiqly <rustiqly@users.noreply.github.com> * Address Copilot review: fix 17 bugs in build analysis scripts - Use free -m with division instead of free -g to avoid rounding (#1) - Add = and ?= to Makefile dependency regex patterns (sonic-net#2, sonic-net#7) - CPU calculation now uses /proc/stat delta (two reads) (sonic-net#3, sonic-net#14) - Fix misleading 'critical path estimate' comment (sonic-net#4) - Fix parallelism timeline comment (60s not 10s) (sonic-net#5) - Include after-relationship packages in fan stats (sonic-net#6) - Guard disk I/O division by zero when INTERVAL<=1 (sonic-net#8) - Remove unused elapsed_line variable (sonic-net#9) - Remove redundant LIBSWSSCOMMON_DBG check (sonic-net#10) - Remove active_make_jobs from CSV header comment (sonic-net#11) - Wire up _RDEPENDS parsing to build reverse deps (sonic-net#12) - Remove unnecessary 'if v' filter on rdeps JSON (sonic-net#13) - Remove unused REPORT_FORMAT parameter (sonic-net#15) - Add cycle detection to critical path algorithm (sonic-net#16) - Add execute permission check for companion scripts (sonic-net#17) Signed-off-by: Rustiqly <rustiqly@users.noreply.github.com> --------- Signed-off-by: Rustiqly <rustiqly@users.noreply.github.com> Co-authored-by: Rustiqly <rustiqly@users.noreply.github.com>
fengkm
pushed a commit
that referenced
this pull request
May 12, 2026
…dating udevd rules (sonic-net#26343) - Why I did it On SONiC SmartSwitch platforms with DPUs, systemd-udevd crashes with SIGABRT on every reboot when DPU firmware initialization is slow. During the initramfs boot phase, a standalone systemd-udevd daemon is started to handle device discovery. If DPU firmware takes longer than the 60-second udevadm settle timeout (BlueField-3 DPUs can take 120 seconds each in the failure case when they are stuck), the initramfs cannot stop this udevd before switch_root. The stale process survives into the real system but is never chrooted into the overlayfs root, leaving it with a broken filesystem view. When dpu-udev-manager.sh writes udev rules, the stale udevd detects the change and crashes on an assertion in systemd's chase() path resolution (assert(path_is_absolute(p)) at chase.c:648), because dir_fd_is_root() returns false for a process whose root still points to the initramfs rootfs rather than the overlayfs. This triggers a systemd issue : systemd/systemd#29559 which maintainers doesn't consider as a bug from systemd side. Raising this fix for our usecase. Core was generated by `/usr/lib/systemd/systemd-udevd --daemon --resolve-names=never'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f29fe7f695c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007f29fe7f695c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f29fe7a1cc2 in raise () from /lib/x86_64-linux-gnu/libc.so.6 sonic-net#2 0x00007f29fe78a4ac in abort () from /lib/x86_64-linux-gnu/libc.so.6 sonic-net#3 0x00007f29fea50c11 in ?? () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#4 0x00007f29feb94a8b in chase () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#5 0x00007f29feb956e2 in chase_and_opendir () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#6 0x00007f29feb9a609 in conf_files_list_strv () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#7 0x00007f29fea913e8 in config_get_stats_by_path () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#8 0x0000559f295519cf in ?? () sonic-net#9 0x0000559f29553a77 in ?? () sonic-net#10 0x00007f29fec36055 in ?? () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#11 0x00007f29fec3668d in sd_event_dispatch () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#12 0x00007f29fec394a8 in sd_event_run () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#13 0x00007f29fec396c7 in sd_event_loop () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-257.so sonic-net#14 0x0000559f29545820 in ?? () sonic-net#15 0x00007f29fe78bca8 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 sonic-net#16 0x00007f29fe78bd65 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 sonic-net#17 0x0000559f29545c51 in ?? () - How I did it Added a kill_stale_udevd() function to dpu-udev-manager.sh that runs before writing the udev rules. It identifies the systemd-managed udevd PID via systemctl show, then kills any other systemd-udevd --daemon process that doesn't match -- these are leftover initramfs instances. If no stale process exists (e.g. DPUs are healthy and the initramfs udevd exited cleanly), the function is a no-op. - How to verify it Deploy the image on a SmartSwitch with DPUs in a state where firmware initialization times out (>60s per DPU) by stopping image installation before firmware install step Reboot the switch Verify no new systemd-udevd coredumps in /var/core/ Verify the stale process was killed: journalctl -b 0 | grep dpu-udev-manager should show killing stale initramfs udevd PID (systemd udevd is PID ) Verify systemd-udevd.service is healthy: systemctl status systemd-udevd should show active (running) Verify DPU udev rules were written: cat /etc/udev/rules.d/92-midplane-intf.rules should contain the DPU interface naming rules Signed-off-by: Hemanth Kumar Tirupati <tirupatihemanthkumar@gmail.com>
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
20 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.
Create a new branch ufi-202505-dev from the 202505 branch of https://github.com/sonic-net/sonic-buildimage.git