Why I did it
1.57.x SDK based incremental drop that addresses a few egress ACL and drop counter failures. Hostname, vtysh, and incorrect queue watermark issue are addressed too.
How I did it
Update cisco-8000 submodule to v0.2.3
How to verify it
Which release branch to backport (provide reason below if selected)
* Fix kube mode to local mode long duration issue
* Remove IPV6 parameters which is not necessary
* Fix read node labels bug
* Tag the running image to latest if it's stable
* Disable image_version_higher check
* Change image_version_higher checker test case
Signed-off-by: Yun Li <yunli1@microsoft.com>
#### Why I did it
Include below commits
```
00b4dc0 2022-11-14 | Remove error logging on "failed in fdb_vlanmac" (#272) [Qi Luo]
792afe8 2022-11-14 | Don't cache the vlan-id if it is not valid from DB (#273) [zhenggen-xu]
```
Add dualtor test jobs using TestbedV2 in 202012 branch.
Why I did it
Add dualtor test jobs using TestbedV2 in 202012 branch.
How I did it
Add dualtor test jobs using TestbedV2 in 202012 branch.
Signed-off-by: Yutong Zhang <yutongzhang@microsoft.com>
Why I did it
nameserver and domain entries from build system fsroot gets into sonic image.
How I did it
Clear /etc/resolv.conf before building image
How to verify it
Built image with it and verified with install that /etc/resolv.conf is empty
git log --oneline aacb772..202012
these commits are added in sonic-platform-daemons
8ec96c0 (HEAD -> 202012, origin/202012) [ycabled] fix exception-handling logic for ycabled (#312)
3d5470d [ycabled] move swsscommon API's from subroutines to call them exactly once per task_worker/thread (#310)
Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com>
Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com>
- Why I did it
ethtool is not able to read certain pages(eg. page 11h) of CMIS cables.
SDK provides a set of sysfs to expose the transceiver EEPROM, now we migrate from using ethtool to read these sysfs for transceiver EEPROM reading.
- How I did it
replace ethtool with accessing the SDK sysfs for cable EEPROM reading.
Adjust the offset according to the SDK sysfs memory map.
- How to verify it
run sonic-mgmt sfp-related regression test case.
Signed-off-by: Kebo Liu <kebol@nvidia.com>
- Why I did it
Update SDK/FW version - 4.5.3186/2010_3186 in order to have the following changes:
New functionality:
1. Added support for 6.5W (Class 8) in ports 49-50, 53-54, 57-58, and 61-62 on SN4600 system
Fix the following issues:
1. On very rare occasion (~1/100K), during I2C transaction with MMS1V50-WM and MMS1V90-WR modules on SN4700 system, the module may send unexpected stop which violate the I2C specification, possibly affecting the link up flow
2. When running 1GbE speeds on SN4600 system, the port remained active while peer side was closed
3. While toggling the cable with ‘sfputil lpmode on/off’, error msg like “ERR pmon#xcvrd: Receive PMPE error event on module 1: status {X} error type {y}” could be received
4. When toggling many ports of the Spectrum devices while raising 10GbE link up and link maintenance is enabled, the switch may get stuck and may need to be rebooted
5. When trying to reconfigure the Flex Parser header and Flex transition parameters after ISSU, the switch will returned an error even if the configuration was identical to that done before performing the ISSU
6. While moving from lossless to lossy mode while shared headroom was used, reduction of the shared headroom can only be done prior to pool type change and when shared headroom is not utilized
7. SLL configuration is missing in SDK dump
8. If TTL_CMD_COPY is used in Encap direction for a packet with no TTL, then the value passed in the ttl data structure will be used if non-zero (default 255 if zero)
9. PCI calibration changes from a static to a dynamic mechanism
10. Layer 4 port information is not initialized for BFD packet event. To address the issue, remote peer UDP port information was added in BFD packet event
11. SDK returned error when FEC mode is set on twisted pair, when FEC was set to None
- How I did it
Update pointer for the SDK/FW
- How to verify it
Run regression tests
Signed-off-by: dprital <drorp@nvidia.com>
* [TestbedV2]Migrate t0 and t1-lag to TestbedV2 (#12383)
signed-off-by: jianquanye@microsoft.com
Migrate the t0 and t1-lag test jobs in buildimage repo to TestbedV2.
Why I did it
Migrate the t0 and t1-lag test jobs in buildimage repo to TestbedV2.
How I did it
Migrate the t0 and t1-lag test jobs in buildimage repo to TestbedV2.
Remove ceos type setting
Use 202012 branch as sonic-mgmt branch
* Modify template to use 202012 branch
Update sonic-swss submodule pointer to include the following:
* 08711a8 [orchdaemon]: Fixed sairedis record file rotation ([#2481](https://github.com/sonic-net/sonic-swss/pull/2481))
Signed-off-by: dprital <drorp@nvidia.com>
* Fix to improve hostname handling
If config_db.json is missing hostname entry, hostname-config.sh ends
up deleting existing entry too and hostname changes to default 'localhost'
* default hostname to 'sonic` if missing in config file
- Skip the interface status check if the interface does not exist. In the future, when the interface is created/comes up this check will be triggered again.
Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
Why I did it
Cherry pick #9519.
when we remove a port and add it back immediately - lldp is keep failing
warning message keeps appearing:
[WARN/lldp] unable to send packet on real device for Ethernet4: No such device or address
How I did it
on delete link events it will immediately execute delete without using aggregate events mechanism.
How to verify it
Run autorestart/test_container_autorestart.py in sonic-mgmt repo
Or manual test steps:
sudo config feature autorestart swss disabled
docker exec swss supervisorctl status
docker exec swss kill -SIGKILL 111(orchagent)
docker inspect -f {{.State.Running}} swss => make sure swss is running
docker exec swss supervisorctl start orchagent
Signed-off-by: Zhaohui Sun <zhaohuisun@microsoft.com>
Why I did it
Cherry-pick from #8950
Sonic-swss-common requires gmock for staged unit tests
How I did it
Installed dependency in sonic-buster-build docker file
How to verify it
rebuild the build container
