Build Error in SONiC 202211 branch - Marvell ARM64 #16204

thovikeerthi · 2023-08-18T09:18:33Z

I am trying to compile "SONiC branch 202211 source for the Marvell-ARM64 target platform". Then facing the below compilation/build error. Please advise and share your inputs to address this build issue.

Steps followed:
Step 1: git clone -b 202211 https://github.com/sonic-net/sonic-buildimage.git
Step 2: cd sonic-buildimage
Step 3: git checkout 5ac1051
Step 4: make init
Step 5: NOSTRETCH=1 make configure PLATFORM=marvell-arm64 PLATFORM_ARCH=arm64

Build/Compilation error is seen on executing Step5.

Error Snippet:
"
=> ERROR [internal] load metadata for docker.io/library/sonic-slave-buster-march-arm64:1d6f93e8d09 1.1s

[internal] load metadata for docker.io/library/sonic-slave-buster-march-arm64:1d6f93e8d09:

Dockerfile.cleanup:9

7 |
8 | # Clean up the cache data
9 | >>> FROM sonic-slave-buster-march-arm64:1d6f93e8d09 as final
10 | RUN rm /cache.tgz
11 |

ERROR: failed to solve: sonic-slave-buster-march-arm64:1d6f93e8d09: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

docker rmi tmp-sonic-slave-buster-march-arm64:1d6f93e8d09
Error response from daemon: No such image: tmp-sonic-slave-buster-march-arm64:1d6f93e8d09
docker container rm sonic-slave-buster-march-arm64-1d6f93e8d09
Error response from daemon: No such container: sonic-slave-buster-march-arm64-1d6f93e8d09
make[1]: *** [Makefile.work:543: configure] Error 1
make[1]: Leaving directory '/home/sonic/sonic-marvell/sonic-buildimage'
make: *** [Makefile:94: configure] Error 2
"

FYI: Docker Version Information:
sonic@labuser:~$ docker version
Client: Docker Engine - Community
Version: 23.0.1
API version: 1.42
Go version: go1.19.5
Git commit: a5ee5b1
Built: Thu Feb 9 19:46:56 2023
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 23.0.1
API version: 1.42 (minimum version 1.12)
Go version: go1.19.5
Git commit: bc3805a
Built: Thu Feb 9 19:46:56 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.16
GitCommit: 31aa4358a36870b21a992d3ad2bef29e1d693bec
runc:
Version: 1.1.4
GitCommit: v1.1.4-0-g5fd4c4d
docker-init:
Version: 0.19.0
GitCommit: de40ad0
sonic@labuser:~$ containerd -version
containerd containerd.io 1.6.16 31aa4358a36870b21a992d3ad2bef29e1d693bec

The text was updated successfully, but these errors were encountered:

thovikeerthi · 2023-08-22T07:52:40Z

Any input regarding this error is helpful. please suggest. Facing same issue with Docker version 18 as well.

thovikeerthi · 2023-08-28T07:59:58Z

Hi Team, From Community CI daily builds portal, I could see that ARM based compilation is successful. But, in my local setup facing above error. Please suggest are there any setup specific configurations to be performed ? What is the version of docker & containerd configured in Community Build PC. ?

vmittal-msft · 2023-08-30T15:23:35Z

@kishoreatreya Can you please help take a look ?

kishoreatreya · 2023-08-30T17:06:09Z

We are looking at this.

liushilongbuaa · 2023-09-14T03:33:25Z

@thovikeerthi , these errors are not fatal. Can you provide more logs after these errors?

thovikeerthi · 2023-09-15T07:39:21Z

Thanks @liushilongbuaa for the response. This compilation issue for ARM/marvell platform has become a road-blocker for my activity. Sure, I will update back with the complete set of logs. Thanks.

thovikeerthi · 2023-09-15T08:26:31Z

Hi @liushilongbuaa / @kishoreatreya ,
Please find the build logs captured during compilation (today) as below.

Build Logs:
sonic_202211_marvell_arm64_build_logs_15sep.zip

Error Snapshot:

Please provide your insights and suggestions to resolve this compilation issue for Marvell platform.
Also, any recommendations for host build-system's software's (if anything additional & apart from details captured in community link: https://github.com/sonic-net/sonic-buildimage/blob/202211/README.md#usage-for-arm-architecture).

radha-danda · 2023-09-20T08:25:18Z

Build failures are seen as old (Apr 23) SONIC commits is used
Way to fix the issue is to use the latest SONiC commit. Next step is to resolve hunk failures of the patch script for AC5x SONIC image
We are working on raising the community PRs in few weeks. Will keep you posted once the PRs are raised.

liushilongbuaa · 2023-09-20T09:51:28Z

Hi @liushilongbuaa / @kishoreatreya , Please find the build logs captured during compilation (today) as below.

Build Logs: sonic_202211_marvell_arm64_build_logs_15sep.zip

Error Snapshot:

Please provide your insights and suggestions to resolve this compilation issue for Marvell platform. Also, any recommendations for host build-system's software's (if anything additional & apart from details captured in community link: https://github.com/sonic-net/sonic-buildimage/blob/202211/README.md#usage-for-arm-architecture).

It failed on building sonic-slave-buster-march-arm64 docker image. please find logs before this picture.
It failed on one step. I need logs like:
Step xx/xx:
...
...

radha-danda · 2023-09-20T09:57:21Z

As I mentioned in my previous comment, you are using very old SONIC commit for compilation. Pls move to latest SONiC commit.

Step 3: git checkout 5ac1051 >>>>>> This is old commit (Arp 23)

thovikeerthi · 2023-09-20T11:59:14Z

Okay @radha-danda . I will use the latest 202211 branch code and provide the update. JFYI, I earlier tried all the combinations but same error seen. Anyhow, i will re-verify & capture the logs.

thovikeerthi · 2023-09-20T17:37:21Z

Hi @radha-danda ,
Please find the build failure logs (marvell arm64 platform) for 202211 master branch code, as below. Not switched to any specific SONiC Commit and code is pointing to 202211 master branch. Error appeared while executing Step4 command.

Steps followed:
Step 1: git clone -b 202211 https://github.com/sonic-net/sonic-buildimage.git
Step 2: cd sonic-buildimage
Step 3: make init
Step 4: NOJESSIE=1 NOSTRETCH=1 make configure PLATFORM=marvell-arm64 PLATFORM_ARCH=arm64

Build Logs:
sonic_202211_marvell_arm64_build_logs_20sep.zip

Error Screenshot:

Note FYI:

On the same host PC, I am able to successfully compile and generate X86 SONiC NOS builds for Broadcom ASIC. Issue seen only for Marvell ARM builds.

Please provide your insights and suggestions to resolve this compilation issue for Marvell platform.

radha-danda · 2023-09-21T07:49:51Z

Let me repeat my comment. Find below highlighted my earlier comment.

.
Complete steps must be executed before the error can be debugged

as Marvell arm64 support on 202211 is not ready yet, you can't compile the code without patch script. As I mentioned already we are working on the PRs. Please wait for the same.

liushilongbuaa · 2023-09-21T13:51:56Z

11.61 Err:2 http://debian-archive.trafficmanager.net/debian bullseye-updates InRelease
11.61 The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
15.07 Err:3 http://debian-archive.trafficmanager.net/debian bullseye-backports InRelease
15.07 The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
33.07 Reading package lists...

Here is the failure log.

liushilongbuaa · 2023-09-21T14:01:56Z

https://dev.azure.com/mssonic/build/_build/results?buildId=364116&view=logs&j=c48ed391-8271-570f-5ba3-8247d4561aa1&t=9bba0c5b-4e07-5204-8f7b-aaa7b6c04a19
We have success build officially.
Two ways to debug:

Use the following options to use Azure debian snapshot mirror.
SONIC_VERSION_CONTROL_COMPONENTS=deb,py2,py3,web,git,docker MIRROR_SNAPSHOT=y
Get:12 http://packages.trafficmanager.net/snapshot/debian/20230606T000122Z bullseye-updates/main arm64 Packages [12.1 kB]
Login to the docker to debug. Maybe you need to add gpt keys.
https://chrisjean.com/fix-apt-get-update-the-following-signatures-couldnt-be-verified-because-the-public-key-is-not-available/

By the way. Your log is too long. Use DOCKER_BUILDKIT=0 options to build docker image with old docker build engine.

thovikeerthi · 2023-09-25T17:44:46Z

Hi @liushilongbuaa/ @radha-danda,
Thanks for your feedback and inputs. I will check on these suggested points & verify.

I have few queries in this regard, request to please suggest:

One difference which I noticed in the Community Official build link is, use of build option "PLATFORM=generic", while I have earlier used 'PLATFORM=marvell-arm64'. Does it have any impact ?
As informed in my previous post, I am able to make successful X86/Broadcom builds on the same host PC. This error is seen only for ARM/Marvell builds.
If there is any issue w.r.t PUBKEYS or GPT Keys, then should that not affect X86/Broadcom builds as well ?
Also, the update/response from @radha-danda indicate that, some patch commits are pending for Marvell/ARM compilation for 202211 branch. If yes, how community official builds are successful ? Am I missing anything here ?

thovikeerthi · 2023-10-03T18:14:49Z

Hi @liushilongbuaa , I tried both suggested options, still encountered same issue (as reported in my earlier post) with both 202211 master and 202211 commit-id 5ac1051 .
Please provide your insights on my previous posted queries, which helps to troubleshoot further. Thank you.

liushilongbuaa · 2023-10-07T07:56:14Z

PLATFORM=marvell-arm64

PLATFORM don't work for 'make configure'. PLATFORM_ARCH is required.
X86 and cross platform arm64 used different base image. So they uses different apt sources.
ex: debian:buster vs multiarch/debian:buster
Please refer sonic-slave-buster/Dockerfile.j2 for details.
Official build runs on arm host to build arm image. But you built arm image on amd64 host. They will use different docker base image. And official build used Azure snapshot mirror as apt sources. Official debian jessie/stretch sources may be not supported.

shanshri · 2023-10-11T04:36:22Z

I am seeing the same cross compilation issue in master latest as well.

thovikeerthi · 2023-10-12T05:58:36Z

Hi @liushilongbuaa,
Thanks for your update. This update is helpful. Please find my response as below.

PLATFORM=marvell-arm64

PLATFORM don't work for 'make configure'. PLATFORM_ARCH is required.

==> Yes. As noted in my previous post, I have used PLATFORM_ARCH along with PLATFORM i.e. "PLATFORM=marvell-arm64 PLATFORM_ARCH=arm64". Hope this is an allowed build option for 'make configure' command.

X86 and cross platform arm64 used different base image. So they uses different apt sources.
ex: debian:buster vs multiarch/debian:buster
Please refer sonic-slave-buster/Dockerfile.j2 for details.

==> Thank you. This clarification is informative.

Official build runs on arm host to build arm image. But you built arm image on amd64 host. They will use different docker base image. And official build used Azure snapshot mirror as apt sources. Official debian jessie/stretch sources may be not supported.

==> Request to please share the details of ARM Host used by you, so that I can try to create similar infra in my local setup (if feasible) and attempt to generate the ARM SONiC build.

Hi @shanshri , Thanks for the update. Yes. I am facing this compilation issue on all branches (i.e. 202205, 202211, 202305 & master) of SONiC NOS source code. Hope you are also trying to generate ARM build on X86/AMD64 host.

Hi @radha-danda ,
Please confirm is your earlier claimed patch commit from Marvell, is applicable for 'Compilation of SONiC source on X86/AMD64 host/PC' ?

liushilongbuaa · 2023-10-17T05:53:12Z

@thovikeerthi , 1. It is an allowed build option.
Maybe you can add the following options for try. I don't understand what to share for ARM Host. They are only used for automation.
SONIC_VERSION_CONTROL_COMPONENTS=deb,py2,py3,web,git,docker MIRROR_SNAPSHOT=y

thovikeerthi · 2023-10-19T14:32:58Z

okay @liushilongbuaa thanks.

@radha-danda , Please confirm is your earlier claimed patch commit from Marvell, is applicable for 'Compilation of SONiC source on X86/AMD64 host/PC' ?

radha-danda · 2023-10-19T15:50:08Z

okay @liushilongbuaa thanks.

@radha-danda , Please confirm is your earlier claimed patch commit from Marvell, is applicable for 'Compilation of SONiC source on X86/AMD64 host/PC' ?

Patch is only for arm64

thovikeerthi · 2023-10-19T17:20:58Z

Hi Team,
Does it infer Marvell ARM64 builds cannot be generated on a AMD64 Host PC ?

liushilongbuaa · 2023-10-20T02:09:23Z

Marvell ARM64 builds cannot be generated on a

arm builds can be generated on amd64 PC.
But official build stops building arm image from amd64 PC. If you share errors, I can provide some suggestions.
But I will not actually build locally to debug. Because it takes more than 20 hours in building.

thovikeerthi · 2023-10-24T02:26:43Z

Hi @liushilongbuaa ,
I retried generating Marvell ARM-64 SONIC build from 202305 branch on a AMD64 host PC with Ubuntu OS (18.04.6 LTS (Bionic Beaver)), then I again encountered GPG error as detailed below. Please suggest.

Step1: Clone 202305 source
git clone -b 202305 https://github.com/sonic-net/sonic-buildimage.git

Step2: cd sonic-buildimage; sudo modprobe overlay

Step3: make init

Sep4: NOSTRETCH=1 NOJESSIE=1 make configure SONIC_VERSION_CONTROL_COMPONENTS=deb,py2,py3,web,git,docker MIRROR_SNAPSHOT=y PLATFORM=marvell-arm64 PLATFORM_ARCH=arm64 SONIC_BUILD_JOBS=7

===> Then encountered 'GPG Error' at Step 4 (error snippet given below). To debug the issue further, added those GPG Keys in host PC using below commands:
$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 605C66F00D6C9793
$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 6ED0E7B82643E131
$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 0E98404D386FA1D9

===> Also to add the keys within sonic slave container and to debug further within container, enabled 'KEEP_SLAVE_ON' build option and re-initiated Step4 command i.e.
Sep4: NOSTRETCH=1 NOJESSIE=1 make configure SONIC_VERSION_CONTROL_COMPONENTS=deb,py2,py3,web,git,docker MIRROR_SNAPSHOT=y PLATFORM=marvell-arm64 PLATFORM_ARCH=arm64 SONIC_BUILD_JOBS=7 KEEP_SLAVE_ON=yes

Still encountered same error and couldn't even enter into BULLSEYE's SLAVE Container, so unable to add these GPG Keys within sonic-slave container & debug further.

As noticed this error is seen by other community members as well, while doing cross-compilation in their host setup. So, please suggest does the Cross-platform ARM64 base docker image needs any update to address this issue.

Error Snippet:

Logs:
202305_bullseye_gpg_error.txt

liushilongbuaa · 2023-10-29T14:07:12Z

@thovikeerthi It is not correct failure log. Please scrool up.
Usually it is caused by debian mirror error. Maybe key expired. Maybe mirror dist change.

thovikeerthi · 2023-11-02T11:51:04Z

Hi @liushilongbuaa ,
Thanks for your continuous support to resolve this issue.
Please be informed that, I did verify the logs and noted that, there is an GPG key error (as below).

Error Log Snippet:
"GPG error: http://packages.trafficmanager.net/snapshot/debian/20231021T000212Z bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY 605C66F00D6C9793"

Considering your earlier given suggestions I followed the reference link and added those GPG Keys successfully in the HostPC (where I am doing compilation).

While I was not able to enter into the 'sonic-slave' build docker/container to add these GPG Keys, as it thrown error (shared in screenshot above) and exited. Hence, unable to debug from 'sonic-slave' build docker/container.

If the suspect of this error is in 'mirror distribution change or key expiry', how to resolve this dependency. Please suggest.

liushilongbuaa · 2023-11-03T05:00:15Z

@thovikeerthi , It seems that your docker base image is old.
Check the Dockerfile first line. ex 'FROM debian:bullseye'.
If it is pulled from docker.io, you need pull the latest image.
If you used Azure mirror 'publicmirror.azurecr.io', you need to pull like 'docker pull publicmirror.azurecr.io/debian:bullseye'

thovikeerthi · 2023-11-08T06:55:51Z

@thovikeerthi , It seems that your docker base image is old. Check the Dockerfile first line. ex 'FROM debian:bullseye'. If it is pulled from docker.io, you need pull the latest image. If you used Azure mirror 'publicmirror.azurecr.io', you need to pull like 'docker pull publicmirror.azurecr.io/debian:bullseye'

Hi @liushilongbuaa , I am using community source code (202305) and trying to generate Marvell build locally without modifying any configurations. So, the default configs/URLs are used.

As default configurations are used, should I still need to update the Dockerfile (manually) ?

FYI:

On referring './sonic-buildimage/sonic-slave-bullseye/Dockerfile', first line is as below,
FROM multiarch/qemu-user-static:x86_64-aarch64-6.1.0-8 as qemu
FROM multiarch/debian-debootstrap:arm64-bullseye
On referring './sonic-buildimage/.azure-pipelines/template-variables.yml', i could observe that DEFAULT_CONTAINER_REGISTRY is configured to 'publicmirror.azurecr.io'.

liushilongbuaa · 2023-11-08T08:39:14Z

multiarch/debian-debootstrap:arm64-bullseye

Yes, please update docker image.

docker pull multiarch/debian-debootstrap:arm64-bullseye
arm64-bullseye: Pulling from multiarch/debian-debootstrap
c886de0a4f3f: Pull complete

thovikeerthi · 2023-11-15T02:51:34Z

Hi @liushilongbuaa ,
I tried removing all previously downloaded docker images using 'docker system prune' command in my host PC and then downloaded the above suggested docker images manually i.e. using 'docker pull' command. And then initiated SONiC build process, but still I see the same 'GPG Error', as earlier for bullseye debian during 'make configure' step.

GPG Error Snippet:
#16 18.47 W: GPG error: http://debian-archive.trafficmanager.net/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY 605C66F00D6C9793^M
#16 18.47 E: The repository 'http://debian-archive.trafficmanager.net/debian bullseye InRelease' is not signed.^M
#16 18.47 W: GPG error: http://debian-archive.trafficmanager.net/debian bullseye-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131^M
#16 18.47 E: The repository 'http://debian-archive.trafficmanager.net/debian bullseye-updates InRelease' is not signed.^M

FYI: (Following docker images are manually downloaded before initiating SONiC Build)

docker pull multiarch/debian-debootstrap:arm64-bullseye
docker pull multiarch/qemu-user-static:x86_64-aarch64-6.1.0-8
docker pull publicmirror.azurecr.io/debian:bullseye

Please suggest.

liushilongbuaa · 2023-11-15T08:05:24Z

apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0E98404D386FA1D9
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6ED0E7B82643E131
Run these two command before apt-get update. I tested locally. It works.
Root cause debian-debootstrap:arm64-bullseye is created at 2020-09-21. It is too old.

docker inspect multiarch/debian-debootstrap:arm64-bullseye
[
{
"Id": "sha256:35c96c860d6764bac948e1953dedb7338b440d336879d47314dcc1c759c7f5df",
"RepoTags": [
"multiarch/debian-debootstrap:arm64-bullseye",
"publicmirror.azurecr.io/multiarch/debian-debootstrap:arm64-bullseye"
],
"RepoDigests": [
"multiarch/debian-debootstrap@sha256:c8230abd44855b40a1766e8802a6bdfd850f38475ea39d2bcdfda066cae61ca6",
"publicmirror.azurecr.io/multiarch/debian-debootstrap@sha256:c8230abd44855b40a1766e8802a6bdfd850f38475ea39d2bcdfda066cae61ca6"
],
"Parent": "",
"Comment": "",
"Created": "2020-09-21T13:22:48.648386139Z",

liushilongbuaa · 2023-11-15T08:10:23Z

multiarch/debian-debootstrap:armhf-bullseye is created at 2023

docker inspect multiarch/debian-debootstrap:armhf-bullseye
[
{
"Id": "sha256:d95e0a8173940155291ab418b6352a3af767a5f00196463d09d2f23bcd11d2cd",
"RepoTags": [
"multiarch/debian-debootstrap:armhf-bullseye"
],
"RepoDigests": [
"multiarch/debian-debootstrap@sha256:e12214fecec2d0e9356d6fc49b9c04812ccbc1c9f88bc72e0b836ca1afbdf12a"
],
"Parent": "",
"Comment": "buildkit.dockerfile.v0",
"Created": "2023-09-03T01:03:16.40224224Z",

thovikeerthi · 2023-11-15T09:01:58Z

Hi @liushilongbuaa , Thanks for the update. Sure, I will check with the given suggestions and confirm back.

thovikeerthi · 2023-11-15T11:49:36Z

Hi @liushilongbuaa , I am still seeing the same error after taking above updates.

Parallelly took the updates of 'https://github.com/sonic-net/sonic-buildimage/pull/17167/files' in another instance/copy of source and initiated a build,

Here, this GPG error is not seen and able to cross 'make configure' stage, successfully.
While compilation failed in next command i.e. 'make SONIC_BUILD_JOBS=7 target/sonic-marvell-arm64.bin' with a different error.
Error Snippet:
"time="2023-11-15T10:27:45Z" level=error msg="failure getting variant" error="getCPUInfo for pattern: Cpu architecture: not found""

liushilongbuaa · 2023-11-15T12:23:06Z

@thovikeerthi , I have a draft PR: #17182. Please help review&test.
result:
https://dev.azure.com/mssonic/build/_build/results?buildId=411254&view=logs&j=860fb59d-167a-5476-ac54-417a98eceedc&t=f3d4e4d1-c519-5b6d-2c29-c40b2158db67

liushilongbuaa · 2023-11-15T12:45:33Z

https://hub.docker.com/r/multiarch/debian-debootstrap/tags?page=1&name=arm64-bulls

thovikeerthi · 2023-11-16T11:10:02Z

Hi @liushilongbuaa , Not sure how it is working in Azure setup. In my local setup, i still see the same error with both master branch & 202305 (+ abv fix patch) code.

As informed earlier, patch from 'https://github.com/sonic-net/sonic-buildimage/pull/17167/files' is helping me to avoid this GPG error.

Hi @shanshri , Request to share your observations (if any).

liushilongbuaa · 2023-11-16T12:26:54Z

@thovikeerthi , Maybe it is related with containerd/containerd#4109
Maybe you can add 'DOCKER_BUILDKIT=0' options to use old docker build engine instead of buildx.
If 'make configure' passed, you can add 'KEEP_SLAVE_ON=yes' to debug in sonic-slave-* container.

thovikeerthi · 2023-11-23T04:56:04Z

Hi @liushilongbuaa ,
Please be informed that, above issue is resolved by migrating bullseye & buster docker/containerd versions to latest i.e. 24. Thanks.

… amd64. (sonic-net#17182) Fix sonic-net#16204 Microsoft ADO (number only): 25746782 How I did it multiarch/debian-debootstrap:arm64-bullseye is too old. It needs to add some gpg keys before 'apt-get update'

… amd64. (#17182) (#17828) Fix #16204 Microsoft ADO (number only): 25746782 How I did it multiarch/debian-debootstrap:arm64-bullseye is too old. It needs to add some gpg keys before 'apt-get update'

SudharshanSuresh · 2024-01-24T02:58:23Z

Hi @liushilongbuaa , Please be informed that, above issue is resolved by migrating bullseye & buster docker/containerd versions to latest i.e. 24. Thanks.

hi thovikeerthi,
Could you please elaborate how you fixed this? I am facing exactly the same issue in my setup.

Thanks,
Sudharshan

thovikeerthi · 2024-01-24T09:09:35Z

Hi @SudharshanSuresh ,
Please be informed that, within the corresponding debian version dockerfile, need to specify the required/upgraded docker version details. So that, while building corresponding docker required version will be pulled from docker repo.

In which SONiC release/branch are you facing this issue ? Bcz, master sonic branch is already upgraded to use latest docker version.

Signed-off-by: nonodark <ef67891@yahoo.com.tw> Squashed commit of the following: commit 335ebaa Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Wed Jan 24 16:35:00 2024 +0800 [submodule] Update submodule sonic-platform-daemons to the latest HEAD automatically (sonic-net#17891) src/sonic-platform-daemons ``` * 824c20a - (HEAD -> 202305, origin/202305) Support 800G ifname in xcvrd (sonic-net#420) (20 hours ago) [Anoop Kamath] ``` commit 78e211c Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sun Jan 21 16:32:35 2024 +0800 [submodule] Update submodule sonic-utilities to the latest HEAD automatically (sonic-net#17868) src/sonic-utilities ``` * 83a548de - (HEAD -> 202305, origin/202305) Disable Key Validation feature during sonic-installation for Cisco Platforms (sonic-net#3115) (22 hours ago) [selvipal] ``` commit 5d30151 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 20 16:32:45 2024 +0800 [submodule] Update submodule sonic-snmpagent to the latest HEAD automatically (sonic-net#17863) src/sonic-snmpagent ``` * 6f59d29 - (HEAD -> 202305, origin/202305) Fix SNMP dropping some of the queue counter when create_only_config_db_buffers is set to true (sonic-net#303) (sonic-net#309) (33 minutes ago) [mssonicbld] ``` commit 208c170 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 20 04:32:37 2024 +0800 [submodule] Update submodule sonic-snmpagent to the latest HEAD automatically (sonic-net#17859) src/sonic-snmpagent ``` * 2efaf2e - (HEAD -> 202305, origin/202305) Revert "[action] [PR:303] Fix SNMP dropping some of the queue counter when create_only_config_db_buffers is set to true (sonic-net#303)" (sonic-net#308) (4 minutes ago) [StormLiangMS] ``` commit 306175b Author: Saikrishna Arcot <sarcot@microsoft.com> Date: Fri Jan 19 03:16:04 2024 -0800 dhcrelay: Don't look up the ifindex for the fallback interface (sonic-net#17797) (sonic-net#17840) Currently, whenever isc-dhcp-relay forwards a packet upstream, internally, it will try to send it on a "fallback" interface. My understanding is that this isn't meant to be a real interface, but instead is basically saying to use Linux's regular routing stack to route the packet appropriately (rather than having isc-dhcp-relay specify specifically which interface to use). The problem is that on systems with a weak CPU, a large number of interfaces, and many upstream servers specified, this can introduce a noticeable delay in packets getting sent. The delay comes from trying to get the ifindex of the fallback interface. In one test case, it got to the point that only 2 packets could be processed per second. Because of this, dhcrelay will easily get backlogged and likely get to a point where packets get dropped in the kernel. Fix this by adding a check saying if we're using the fallback interface, then don't try to get the ifindex of this interface. We're never going to have an interface named this in SONiC. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> commit fc7a1ac Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 19 18:36:00 2024 +0800 [submodule] Update submodule sonic-snmpagent to the latest HEAD automatically (sonic-net#17853) src/sonic-snmpagent ``` * b0a4bcc - (HEAD -> 202305, origin/202305) Set the execute bit on sysDescr_pass.py (sonic-net#306) (22 hours ago) [Andre Kostur] ``` commit 30b1f05 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 19 16:34:55 2024 +0800 [submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#17851) src/linkmgrd ``` * f5e9b54 - (HEAD -> 202305, origin/202305) [CodeQL] fix unmet build dependency (sonic-net#222) (10 hours ago) [Jing Zhang] * 2282cc5 - [active-standby] Probe the link in suspend timeout (sonic-net#235) (22 hours ago) [Longxiang Lyu] ``` commit 66ce739 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 19 16:34:46 2024 +0800 [submodule] Update submodule sonic-utilities to the latest HEAD automatically (sonic-net#17855) src/sonic-utilities ``` * 93c42272 - (HEAD -> 202305, origin/202305) [chassis]: Support show ip bgp summary to display without error when no external neighbors are configured on chassis LC (sonic-net#3099) (22 hours ago) [Arvindsrinivasan Lakshmi Narasimhan] ``` commit 076b6c3 Author: zitingguo-ms <zitingguo@microsoft.com> Date: Fri Jan 19 14:56:01 2024 +0800 upgrade xgs SAI to 8.4.39.2 (sonic-net#17842) Why I did it Upgrade the xgs SAI version to 8.4.39.2 to include the following fix: 8.4.36.0: [submodule upgrade] [SAI_BRANCH rel_ocp_sai_8_4] SID: SDK-381039 Cosq control dynamic type changes 8.4.37.0: SID: MMU cosq control configuration with Dynamic Type Check 8.4.38.0: [sbumodule upgrade] [CSP 0001232212][SAI_BRANCH rel_ocp_sai_8_4]back-porting SONIC-82415 to SAI 8.4 8.4.39.0: [CSP CS00012320979] Port SONIC-81867 sai spec compliance for get SAI_SWITCH_ATTR_SWITCH_HARDWARE_INFO 8.4.39.1: changes for phy-re-init of 40G ports for TH platforms CS00012327470 8.4.39.2: fix capability for Hostif queue by change SET operation of SAI_HOSTIF_ATTR_QUEUE to be true Work item tracking Microsoft ADO (number only): 26491005 How I did it Upgrade xgs SAI version in sai.mk file. How to verify it Run basic SONiC test using SAI release pipeline, all cases passed. https://dev.azure.com/mssonic/internal/_build/results?buildId=457869&view=results commit 6d767e5 Author: abdosi <58047199+abdosi@users.noreply.github.com> Date: Thu Jan 18 20:53:26 2024 -0800 [chassis] Support advertisement of Loopback0 of all LC's across all e-BGP peers in TSA mode (sonic-net#16714) (sonic-net#17837) What I did: In Chassis TSA mode Loopback0 Ip's of each LC's should be advertise through e-BGP peers of each remote LC's How I did: - Route-map policy to Advertise own/self Loopback IP to other internal iBGP peers with a community internal_community as define in constants.yml - Route-map policy to match on above internal_community when route is received from internal iBGP peers and set a internal tag as define in constants.yml and also delete the internal_community so we don't send to any of e-BGP peers - In TSA new route-map match on above internal tag and permit the route (Loopback0 IP's of remote LC's) and set the community to traffic_shift_community. - In TSB delete the above new route-map. How I verify: Manual Verification UT updated. sonic-mgmt PR: sonic-net/sonic-mgmt#10239 Signed-off-by: Abhishek Dosi <abdosi@microsoft.com> commit 898f126 Author: Baorong Liu <baorliu@cisco.com> Date: Thu Jan 18 04:08:29 2024 -0800 [staticroutebfd]double commit PR-16450, change bfd to singlehop (sonic-net#17549) Why I did it double commit PR-16450 because of cherry pick conflict for PR#202305 Work item tracking Microsoft ADO (number only): How I did it How to verify it commit d81780b Author: ganglv <88995770+ganglyu@users.noreply.github.com> Date: Thu Jan 18 20:07:40 2024 +0800 Fix host service for 202305 branch (sonic-net#17781) Why I did it When we disable telemetry.service, sonic-hostservice will not start. And root cause is sonic-hostservice is only wanted by telemetry.service. Work item tracking Microsoft ADO (number only): How I did it Add dependency for gnmi.service. How to verify it Disable telemetry.service and build new image, and then check sonic-hostservice with new image. commit b99c46e Author: Liu Shilong <shilongliu@microsoft.com> Date: Thu Jan 18 20:05:04 2024 +0800 [build] Add gpg keys for sonic-slave-bullseye in arm64 cross build on amd64. (sonic-net#17182) (sonic-net#17828) Fix sonic-net#16204 Microsoft ADO (number only): 25746782 How I did it multiarch/debian-debootstrap:arm64-bullseye is too old. It needs to add some gpg keys before 'apt-get update' commit f460347 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Thu Jan 18 16:34:00 2024 +0800 [submodule] Update submodule sonic-swss to the latest HEAD automatically (sonic-net#17821) src/sonic-swss ``` * ac94f0b7 - (HEAD -> 202305, origin/202305) [202305][routeorch] Fixing bug with multiple routes pointing to nhg (sonic-net#3002) (2 hours ago) [Nikola Dancejic] ``` commit ed71c12 Author: abdosi <58047199+abdosi@users.noreply.github.com> Date: Fri Jul 7 11:10:35 2023 -0700 Enable BFD for Static Route for chassis-packet. (sonic-net#15383) *What I did: Enable BFD for Static Route for chassis-packet. This will trigger the use of the feature as defined in here: sonic-net#13789 Signed-off-by: Abhishek Dosi <abdosi@microsoft.com> commit aa01630 Author: abdosi <58047199+abdosi@users.noreply.github.com> Date: Tue Aug 29 13:41:01 2023 -0700 [build]: Added flag in sonic_version.yml to see if image is secured or non-secured (sonic-net#16191) What I did: Added flag in sonic_version.yml to see if compiled image is secured or non-secured. This is done using build/compile time environmental variable SECURE_UPGRADE_MODE as define in HLD: https://github.com/sonic-net/SONiC/blob/master/doc/secure_boot/hld_secure_boot.md This flag does not provide the runtime status of whether the image has booted securely or not. It's possible that compile time signed image (secured image) can boot on non secure platform. Why I did: Flag can be used for manual check or by the test case. ADO: 24319390 How I verify: Manual Verification --- build_version: 'master-16191.346262-cdc5e72a3' debian_version: '11.7' kernel_version: '5.10.0-18-2-amd64' asic_type: broadcom asic_subtype: 'broadcom' commit_id: 'cdc5e72a3' branch: 'master-16191' release: 'none' build_date: Fri Aug 25 03:15:45 UTC 2023 build_number: 346262 built_by: AzDevOps@vmss-soni001UR5 libswsscommon: 1.0.0 sonic_utilities: 1.2 sonic_os_version: 11 secure_boot_image: 'no' Signed-off-by: Abhishek Dosi <abdosi@microsoft.com> commit 9f81d9d Author: snider-nokia <76123698+snider-nokia@users.noreply.github.com> Date: Mon Jan 8 14:38:46 2024 -0500 [Nokia][sonic-platform] Update Nokia sonic-platform submodule and device data (sonic-net#17378) These changes, in conjunction with NDK version >= 22.9.17 address the thermal logging issues discussed at Nokia-ION/ndk#27. While the changes contained at this PR do not require coupling to NDK version >= 22.9.17, thermal logging enhancements will not be available without updated NDK >= 22.9.17. Thus, coupling with NDK >=22.9.17 is preferred and recommended. Why I did it To address thermal logging deficiencies. Work item tracking Microsoft ADO (number only): 26365734 How I did it The following changes are included: Threshold configuration values are provided in the associated device data .json files. There is also a change included to better handle the condition where an SFP module read fails. Modify the module.py reboot to support reboot linecard from Supervisor - Modify reboot to call _reboot_imm for single IMM card reboot - Add log to the ndk_cmd to log the operation of "reboot-linecard" and "shutdown/satrtup the sfm" Add new nokia_cmd set command and modify show ndk-status output - Add a new function reboot_imm() to nokia_common.py to support reboot a single IMM slot from CPM - Added new command: nokia_cmd set reboot-linecard <slot> [forece] for CPM - Append a new column "RebootStatus" at the end of output of "nokia_cmd show ndk-status" - Provide ability for IMM to disable all transceiver module TX at reboot time - Remove defunct xcvr-resync service commit 2f8630c Author: Marty Y. Lok <76118573+mlok-nokia@users.noreply.github.com> Date: Mon Jan 8 14:39:30 2024 -0500 [Nokia-IXR7250E] Modify the platform_reboot on the IXR7250E for PMON API reboot and Disable all SFPs (sonic-net#17483) Why I did it When Supervisor card is rebooted by using PMON API, it takes about 90 seconds to trigger the shutdown in down path. At this time linecards have been up. This delays linecards database initialization which is trying to PING/PONG the database-chassis. To address this issue, we modified the NDK to use the system call with "sudo reboot" when the request is from PMON API on Supervisor case. The NDK version is 22.9.20 and greater. This new NDK requires this modifcaiton of platform_reboot to work with. Work item tracking Microsoft ADO (number only): 26365734 How I did it Modify the platform_reboot In Supervisor not to reboot all IMMs since it has been done in the function reboot() in module.py. Also handle the reboot-cause.txt for on the Supervisor when the reboot is request from PMON API. Modify the Nokia platform specific platform_reboot in linecard to disable all SPFs. This PR works with NDK version 22.9.20 and above Signed-off-by: mlok <marty.lok@nokia.com> commit 6926171 Author: Liu Shilong <shilongliu@microsoft.com> Date: Mon Jan 15 14:59:21 2024 +0800 [build] Fix a bash script some times called by sh issue. (sonic-net#17761) Why I did it Fix a bug that sometimes the script runs in sh not bash. Work item tracking Microsoft ADO (number only): 26297955 How I did it commit a262306 Author: vdahiya12 <67608553+vdahiya12@users.noreply.github.com> Date: Tue Jan 16 11:34:19 2024 -0800 [Arista] Update config.bcm of 7060_cx32s for handling 40g optics with unreliable los settings (sonic-net#17768) For 40G optics there is SAI handling of T0 facing ports to be set with SR4 type and unreliable los set for a fixed set of ports. For this property to be invoked the requirement is set phy_unlos_msft=1 in config.bcm. This change is to meet the requirement and once this property is set, the los/interface type settings is applied by SAI on the required ports. Why I did it For Arista-7060CX-32S-Q32 T1, 40G ports RX_ERR minimalization during connected device reboot can be achieved by turning on Unreliable LOS and SR4 media_type for all ports which are connected to T0. The property phy_unlos_msft=1 is to exclusively enable this property. Microsoft ADO: 25941176 How I did it Changes in SAI and turning on property How to verify it Ran the changes on a testbed and verified configurations are as intended. with property admin@sonic2:~$ bcmcmd "phy diag xe8 dsc config" | grep -C 2 "LOS" Brdfe_on = 0 Media Type = 2 Unreliable LOS = 1 Scrambling Disable = 0 Lane Config from PCS = 0 without property admin@sonic:~$ bcmcmd "phy diag xe8 dsc config" | grep -C 2 "LOS" Brdfe_on = 0 Media Type = 0 Unreliable LOS = 0 Scrambling Disable = 0 Lane Config from PCS = 0 Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com> commit 245f337 Author: Feng-msft <fenpan@microsoft.com> Date: Fri Jan 12 10:51:48 2024 +0800 Fix dialout build flag issue. (sonic-net#17715) Fix ENABLE_DIALOUT flag issue. - Microsoft ADO **(number only)**: 21326000 Update Makefile.work and add debug string. ![image](https://github.com/sonic-net/sonic-buildimage/assets/97083744/960d75d1-618c-4734-acb5-7a32a28c262b) commit b53a890 Author: Liping Xu <108326363+lipxu@users.noreply.github.com> Date: Fri Jan 12 15:26:06 2024 +0800 disable restapi for leafRouter in slim image (sonic-net#17713) Why I did it For some devices with small memory, after upgrading to the latest image, the available memory is not enough. Work item tracking Microsoft ADO (number only): 26324242 How I did it Disable restapi feature for LeafRouter which with slim image. How to verify it verified on 7050qx T1 (slim image), restapi disabled verified on 7050qx T0 (slim image), restapi enabled verified on 7260 T1 (normal image), restapi enabled commit 8561fa6 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 12 16:34:35 2024 +0800 [submodule] Update submodule sonic-utilities to the latest HEAD automatically (sonic-net#17757) src/sonic-utilities ``` * 651a80b1 - (HEAD -> 202305, origin/202305) Modify teamd retry count script to base BGP status on default BGP status (sonic-net#3069) (22 hours ago) [Saikrishna Arcot] ``` commit 9f66a7d Author: Lawrence Lee <lawlee@microsoft.com> Date: Wed Jan 10 14:40:15 2024 -0800 add timeout to ping6 command (sonic-net#17729) Signed-off-by: Lawrence Lee <lawlee@microsoft.com> commit 13aa19a Author: Nazarii Hnydyn <nazariig@nvidia.com> Date: Wed Jan 10 15:15:55 2024 +0200 [swss/syncd]: Remove dependency on interfaces-config.service (sonic-net#17649) Signed-off-by: Nazarii Hnydyn nazariig@nvidia.com This improvement does not bring any warm-reboot degradation, since the database availability (tcp/ip access over the loopback interface) was fixed by these PRs: Re-add 127.0.0.1/8 when bringing down the interfaces sonic-net#15080 Fix potentially not having any loopback address on lo interface sonic-net#16490 Why I did it Removed dependency on interfaces-config.service to speed up the boot, because interfaces-config.service takes a lot of time on init Work item tracking N/A How I did it Changed service files for swss/syncd How to verify it Boot and check swss/syncd start time comparing to interfaces-config commit f4c15b8 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Wed Jan 10 16:34:10 2024 +0800 [submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#17731) src/linkmgrd ``` * 2f5971f - (HEAD -> 202305, origin/202305) [warmboot] use config_db connector to update mux mode config instead of CLI (sonic-net#223) (4 hours ago) [Jing Zhang] ``` commit a3b5ea9 Author: Nazarii Hnydyn <nazariig@nvidia.com> Date: Wed Jan 10 02:56:20 2024 +0200 [sonic-cfggen]: Optimize template rendering and database access. (sonic-net#17650) Signed-off-by: Nazarii Hnydyn nazariig@nvidia.com Why I did it Improved switch init time Work item tracking N/A How I did it Replaced: sonic-cfggen -> sonic-db-cli Aggregated template list for sonic-cfggen How to verify it Run warm-reboot commit 44bc291 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Wed Jan 10 04:32:40 2024 +0800 [submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#17721) src/linkmgrd ``` * 2089ab6 - (HEAD -> 202305, origin/202305) Exclude DbInterface in PR coverage check (sonic-net#224) (3 hours ago) [Jing Zhang] ``` commit 1337597 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Wed Jan 10 02:32:19 2024 +0800 [submodule] Update submodule sonic-snmpagent to the latest HEAD automatically (sonic-net#17722) src/sonic-snmpagent ``` * e5fd192 - (HEAD -> 202305, origin/202305) Fix SNMP dropping some of the queue counter when create_only_config_db_buffers is set to true (sonic-net#303) (9 hours ago) [DavidZagury] ``` commit bb23f7b Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 6 16:42:00 2024 +0800 [submodule] Update submodule sonic-gnmi to the latest HEAD automatically (sonic-net#17696) commit 7ccef97 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 6 03:37:17 2024 +0800 [YANG] Enable Yang model for BGP_BBR config entry (sonic-net#17622) (sonic-net#17692) commit 8defdfe Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 6 01:15:01 2024 +0800 [submodule] Update submodule sonic-sairedis to the latest HEAD automatically (sonic-net#17691) commit b549962 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 6 01:00:55 2024 +0800 [submodule] Update submodule sonic-gnmi to the latest HEAD automatically (sonic-net#17690) commit 02dc49a Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 15:14:43 2024 +0800 [submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#17687) commit 0d31ee8 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 02:39:03 2024 +0800 Update TELEMETRY_CLIENT YANG model (sonic-net#16861) (sonic-net#17679) commit df22ca9 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 01:04:39 2024 +0800 [Arista] Remove aggregate port config files for multi-asic devices (sonic-net#16923) (sonic-net#17678) commit ca2695f Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 00:44:19 2024 +0800 password-hardening: Add support to disable expiration date like in Linux (PAM) (sonic-net#17426) (sonic-net#17674) commit 388457a Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 00:35:07 2024 +0800 [arp_update]: Flush neighbors with incorrect MAC info (sonic-net#17238) (sonic-net#17677) commit 38c5e68 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 00:32:38 2024 +0800 Fix can't access IPV6 address via management interface because 'default' route table does not add to route lookup issue. (sonic-net#17281) (sonic-net#17676) commit 76d8ff0 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Thu Jan 4 23:10:28 2024 +0800 Update backend_acl.py to specify ACL table name (sonic-net#17553) (sonic-net#17673) commit b72a740 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Thu Jan 4 22:37:26 2024 +0800 [docker_image_ctl.j2]: swss docker initialization improvements (sonic-net#17628) (sonic-net#17672) commit 609b3a7 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Thu Jan 4 22:29:00 2024 +0800 [image_config]: Update DHCP rate-limit for mgmt TOR devices (sonic-net#17630) (sonic-net#17671) commit 8362c09 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Tue Jan 2 15:13:53 2024 +0800 [submodule] Update submodule sonic-swss to the latest HEAD automatically (sonic-net#17642) commit 3cb6343 Author: Stepan Blyshchak <38952541+stepanblyschak@users.noreply.github.com> Date: Tue Jan 2 02:59:17 2024 +0200 [202305] Revert bgp suppress fib pending (sonic-net#17578) DEPENDS ON: sonic-net/sonic-swss#2997 sonic-net/sonic-utilities#3093 What I did Revert the feature. Why I did it Revert bgp suppress FIB functionality due to found FRR memory consumption issues and bugs. How I verified it Basic sanity check on t1-lag, regression in progress. commit 64ed3d5 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Mon Jan 1 10:31:33 2024 +0800 Fix system-health hardware_checker to consume fan tolerance details (sonic-net#16689) (sonic-net#17640) commit 98ad3b0 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sun Dec 31 17:01:53 2023 +0800 [submodule] Update submodule sonic-utilities to the latest HEAD automatically (sonic-net#17643) commit 1398daa Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sun Dec 31 15:20:25 2023 +0800 [submodule] Update submodule sonic-platform-daemons to the latest HEAD automatically (sonic-net#17641) commit fb83d4d Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Dec 29 01:07:45 2023 +0800 [Mellanox] wait until hw-management watchdog files ready (sonic-net#17618) (sonic-net#17633) commit a8ad19d Author: Junchao-Mellanox <57339448+Junchao-Mellanox@users.noreply.github.com> Date: Thu Dec 28 20:53:49 2023 +0800 [202305] Optimize syslog rate limit feature for fast and warm boot (sonic-net#17478) Backport PR sonic-net#17458 due to conflict. Why I did it Optimize syslog rate limit feature for fast and warm boot Work item tracking Microsoft ADO (number only): How I did it Optimize redis start time Don't render rsyslog.conf in container startup script Disable containercfgd by default. There is a new CLI to enable it (in another PR) How to verify it Manual test Regression test

Squashed commit of the following: commit 335ebaa Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Wed Jan 24 16:35:00 2024 +0800 [submodule] Update submodule sonic-platform-daemons to the latest HEAD automatically (sonic-net#17891) #### Why I did it src/sonic-platform-daemons ``` * 824c20a - (HEAD -> 202305, origin/202305) Support 800G ifname in xcvrd (sonic-net#420) (20 hours ago) [Anoop Kamath] ``` #### How I did it #### How to verify it #### Description for the changelog commit 78e211c Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sun Jan 21 16:32:35 2024 +0800 [submodule] Update submodule sonic-utilities to the latest HEAD automatically (sonic-net#17868) #### Why I did it src/sonic-utilities ``` * 83a548de - (HEAD -> 202305, origin/202305) Disable Key Validation feature during sonic-installation for Cisco Platforms (sonic-net#3115) (22 hours ago) [selvipal] ``` #### How I did it #### How to verify it #### Description for the changelog commit 5d30151 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 20 16:32:45 2024 +0800 [submodule] Update submodule sonic-snmpagent to the latest HEAD automatically (sonic-net#17863) #### Why I did it src/sonic-snmpagent ``` * 6f59d29 - (HEAD -> 202305, origin/202305) Fix SNMP dropping some of the queue counter when create_only_config_db_buffers is set to true (sonic-net#303) (sonic-net#309) (33 minutes ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog commit 208c170 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 20 04:32:37 2024 +0800 [submodule] Update submodule sonic-snmpagent to the latest HEAD automatically (sonic-net#17859) #### Why I did it src/sonic-snmpagent ``` * 2efaf2e - (HEAD -> 202305, origin/202305) Revert "[action] [PR:303] Fix SNMP dropping some of the queue counter when create_only_config_db_buffers is set to true (sonic-net#303)" (sonic-net#308) (4 minutes ago) [StormLiangMS] ``` #### How I did it #### How to verify it #### Description for the changelog commit 306175b Author: Saikrishna Arcot <sarcot@microsoft.com> Date: Fri Jan 19 03:16:04 2024 -0800 dhcrelay: Don't look up the ifindex for the fallback interface (sonic-net#17797) (sonic-net#17840) Currently, whenever isc-dhcp-relay forwards a packet upstream, internally, it will try to send it on a "fallback" interface. My understanding is that this isn't meant to be a real interface, but instead is basically saying to use Linux's regular routing stack to route the packet appropriately (rather than having isc-dhcp-relay specify specifically which interface to use). The problem is that on systems with a weak CPU, a large number of interfaces, and many upstream servers specified, this can introduce a noticeable delay in packets getting sent. The delay comes from trying to get the ifindex of the fallback interface. In one test case, it got to the point that only 2 packets could be processed per second. Because of this, dhcrelay will easily get backlogged and likely get to a point where packets get dropped in the kernel. Fix this by adding a check saying if we're using the fallback interface, then don't try to get the ifindex of this interface. We're never going to have an interface named this in SONiC. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> commit fc7a1ac Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 19 18:36:00 2024 +0800 [submodule] Update submodule sonic-snmpagent to the latest HEAD automatically (sonic-net#17853) #### Why I did it src/sonic-snmpagent ``` * b0a4bcc - (HEAD -> 202305, origin/202305) Set the execute bit on sysDescr_pass.py (sonic-net#306) (22 hours ago) [Andre Kostur] ``` #### How I did it #### How to verify it #### Description for the changelog commit 30b1f05 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 19 16:34:55 2024 +0800 [submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#17851) #### Why I did it src/linkmgrd ``` * f5e9b54 - (HEAD -> 202305, origin/202305) [CodeQL] fix unmet build dependency (sonic-net#222) (10 hours ago) [Jing Zhang] * 2282cc5 - [active-standby] Probe the link in suspend timeout (sonic-net#235) (22 hours ago) [Longxiang Lyu] ``` #### How I did it #### How to verify it #### Description for the changelog commit 66ce739 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 19 16:34:46 2024 +0800 [submodule] Update submodule sonic-utilities to the latest HEAD automatically (sonic-net#17855) #### Why I did it src/sonic-utilities ``` * 93c42272 - (HEAD -> 202305, origin/202305) [chassis]: Support show ip bgp summary to display without error when no external neighbors are configured on chassis LC (sonic-net#3099) (22 hours ago) [Arvindsrinivasan Lakshmi Narasimhan] ``` #### How I did it #### How to verify it #### Description for the changelog commit 076b6c3 Author: zitingguo-ms <zitingguo@microsoft.com> Date: Fri Jan 19 14:56:01 2024 +0800 upgrade xgs SAI to 8.4.39.2 (sonic-net#17842) Why I did it Upgrade the xgs SAI version to 8.4.39.2 to include the following fix: 8.4.36.0: [submodule upgrade] [SAI_BRANCH rel_ocp_sai_8_4] SID: SDK-381039 Cosq control dynamic type changes 8.4.37.0: SID: MMU cosq control configuration with Dynamic Type Check 8.4.38.0: [sbumodule upgrade] [CSP 0001232212][SAI_BRANCH rel_ocp_sai_8_4]back-porting SONIC-82415 to SAI 8.4 8.4.39.0: [CSP CS00012320979] Port SONIC-81867 sai spec compliance for get SAI_SWITCH_ATTR_SWITCH_HARDWARE_INFO 8.4.39.1: changes for phy-re-init of 40G ports for TH platforms CS00012327470 8.4.39.2: fix capability for Hostif queue by change SET operation of SAI_HOSTIF_ATTR_QUEUE to be true Work item tracking Microsoft ADO (number only): 26491005 How I did it Upgrade xgs SAI version in sai.mk file. How to verify it Run basic SONiC test using SAI release pipeline, all cases passed. https://dev.azure.com/mssonic/internal/_build/results?buildId=457869&view=results commit 6d767e5 Author: abdosi <58047199+abdosi@users.noreply.github.com> Date: Thu Jan 18 20:53:26 2024 -0800 [chassis] Support advertisement of Loopback0 of all LC's across all e-BGP peers in TSA mode (sonic-net#16714) (sonic-net#17837) What I did: In Chassis TSA mode Loopback0 Ip's of each LC's should be advertise through e-BGP peers of each remote LC's How I did: - Route-map policy to Advertise own/self Loopback IP to other internal iBGP peers with a community internal_community as define in constants.yml - Route-map policy to match on above internal_community when route is received from internal iBGP peers and set a internal tag as define in constants.yml and also delete the internal_community so we don't send to any of e-BGP peers - In TSA new route-map match on above internal tag and permit the route (Loopback0 IP's of remote LC's) and set the community to traffic_shift_community. - In TSB delete the above new route-map. How I verify: Manual Verification UT updated. sonic-mgmt PR: sonic-net/sonic-mgmt#10239 Signed-off-by: Abhishek Dosi <abdosi@microsoft.com> commit 898f126 Author: Baorong Liu <baorliu@cisco.com> Date: Thu Jan 18 04:08:29 2024 -0800 [staticroutebfd]double commit PR-16450, change bfd to singlehop (sonic-net#17549) Why I did it double commit PR-16450 because of cherry pick conflict for PR#202305 Work item tracking Microsoft ADO (number only): How I did it How to verify it commit d81780b Author: ganglv <88995770+ganglyu@users.noreply.github.com> Date: Thu Jan 18 20:07:40 2024 +0800 Fix host service for 202305 branch (sonic-net#17781) Why I did it When we disable telemetry.service, sonic-hostservice will not start. And root cause is sonic-hostservice is only wanted by telemetry.service. Work item tracking Microsoft ADO (number only): How I did it Add dependency for gnmi.service. How to verify it Disable telemetry.service and build new image, and then check sonic-hostservice with new image. commit b99c46e Author: Liu Shilong <shilongliu@microsoft.com> Date: Thu Jan 18 20:05:04 2024 +0800 [build] Add gpg keys for sonic-slave-bullseye in arm64 cross build on amd64. (sonic-net#17182) (sonic-net#17828) Fix sonic-net#16204 Microsoft ADO (number only): 25746782 How I did it multiarch/debian-debootstrap:arm64-bullseye is too old. It needs to add some gpg keys before 'apt-get update' commit f460347 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Thu Jan 18 16:34:00 2024 +0800 [submodule] Update submodule sonic-swss to the latest HEAD automatically (sonic-net#17821) #### Why I did it src/sonic-swss ``` * ac94f0b7 - (HEAD -> 202305, origin/202305) [202305][routeorch] Fixing bug with multiple routes pointing to nhg (sonic-net#3002) (2 hours ago) [Nikola Dancejic] ``` #### How I did it #### How to verify it #### Description for the changelog commit ed71c12 Author: abdosi <58047199+abdosi@users.noreply.github.com> Date: Fri Jul 7 11:10:35 2023 -0700 Enable BFD for Static Route for chassis-packet. (sonic-net#15383) *What I did: Enable BFD for Static Route for chassis-packet. This will trigger the use of the feature as defined in here: sonic-net#13789 Signed-off-by: Abhishek Dosi <abdosi@microsoft.com> commit aa01630 Author: abdosi <58047199+abdosi@users.noreply.github.com> Date: Tue Aug 29 13:41:01 2023 -0700 [build]: Added flag in sonic_version.yml to see if image is secured or non-secured (sonic-net#16191) What I did: Added flag in sonic_version.yml to see if compiled image is secured or non-secured. This is done using build/compile time environmental variable SECURE_UPGRADE_MODE as define in HLD: https://github.com/sonic-net/SONiC/blob/master/doc/secure_boot/hld_secure_boot.md This flag does not provide the runtime status of whether the image has booted securely or not. It's possible that compile time signed image (secured image) can boot on non secure platform. Why I did: Flag can be used for manual check or by the test case. ADO: 24319390 How I verify: Manual Verification --- build_version: 'master-16191.346262-cdc5e72a3' debian_version: '11.7' kernel_version: '5.10.0-18-2-amd64' asic_type: broadcom asic_subtype: 'broadcom' commit_id: 'cdc5e72a3' branch: 'master-16191' release: 'none' build_date: Fri Aug 25 03:15:45 UTC 2023 build_number: 346262 built_by: AzDevOps@vmss-soni001UR5 libswsscommon: 1.0.0 sonic_utilities: 1.2 sonic_os_version: 11 secure_boot_image: 'no' Signed-off-by: Abhishek Dosi <abdosi@microsoft.com> commit 9f81d9d Author: snider-nokia <76123698+snider-nokia@users.noreply.github.com> Date: Mon Jan 8 14:38:46 2024 -0500 [Nokia][sonic-platform] Update Nokia sonic-platform submodule and device data (sonic-net#17378) These changes, in conjunction with NDK version >= 22.9.17 address the thermal logging issues discussed at Nokia-ION/ndk#27. While the changes contained at this PR do not require coupling to NDK version >= 22.9.17, thermal logging enhancements will not be available without updated NDK >= 22.9.17. Thus, coupling with NDK >=22.9.17 is preferred and recommended. Why I did it To address thermal logging deficiencies. Work item tracking Microsoft ADO (number only): 26365734 How I did it The following changes are included: Threshold configuration values are provided in the associated device data .json files. There is also a change included to better handle the condition where an SFP module read fails. Modify the module.py reboot to support reboot linecard from Supervisor - Modify reboot to call _reboot_imm for single IMM card reboot - Add log to the ndk_cmd to log the operation of "reboot-linecard" and "shutdown/satrtup the sfm" Add new nokia_cmd set command and modify show ndk-status output - Add a new function reboot_imm() to nokia_common.py to support reboot a single IMM slot from CPM - Added new command: nokia_cmd set reboot-linecard <slot> [forece] for CPM - Append a new column "RebootStatus" at the end of output of "nokia_cmd show ndk-status" - Provide ability for IMM to disable all transceiver module TX at reboot time - Remove defunct xcvr-resync service commit 2f8630c Author: Marty Y. Lok <76118573+mlok-nokia@users.noreply.github.com> Date: Mon Jan 8 14:39:30 2024 -0500 [Nokia-IXR7250E] Modify the platform_reboot on the IXR7250E for PMON API reboot and Disable all SFPs (sonic-net#17483) Why I did it When Supervisor card is rebooted by using PMON API, it takes about 90 seconds to trigger the shutdown in down path. At this time linecards have been up. This delays linecards database initialization which is trying to PING/PONG the database-chassis. To address this issue, we modified the NDK to use the system call with "sudo reboot" when the request is from PMON API on Supervisor case. The NDK version is 22.9.20 and greater. This new NDK requires this modifcaiton of platform_reboot to work with. Work item tracking Microsoft ADO (number only): 26365734 How I did it Modify the platform_reboot In Supervisor not to reboot all IMMs since it has been done in the function reboot() in module.py. Also handle the reboot-cause.txt for on the Supervisor when the reboot is request from PMON API. Modify the Nokia platform specific platform_reboot in linecard to disable all SPFs. This PR works with NDK version 22.9.20 and above Signed-off-by: mlok <marty.lok@nokia.com> commit 6926171 Author: Liu Shilong <shilongliu@microsoft.com> Date: Mon Jan 15 14:59:21 2024 +0800 [build] Fix a bash script some times called by sh issue. (sonic-net#17761) Why I did it Fix a bug that sometimes the script runs in sh not bash. Work item tracking Microsoft ADO (number only): 26297955 How I did it commit a262306 Author: vdahiya12 <67608553+vdahiya12@users.noreply.github.com> Date: Tue Jan 16 11:34:19 2024 -0800 [Arista] Update config.bcm of 7060_cx32s for handling 40g optics with unreliable los settings (sonic-net#17768) For 40G optics there is SAI handling of T0 facing ports to be set with SR4 type and unreliable los set for a fixed set of ports. For this property to be invoked the requirement is set phy_unlos_msft=1 in config.bcm. This change is to meet the requirement and once this property is set, the los/interface type settings is applied by SAI on the required ports. Why I did it For Arista-7060CX-32S-Q32 T1, 40G ports RX_ERR minimalization during connected device reboot can be achieved by turning on Unreliable LOS and SR4 media_type for all ports which are connected to T0. The property phy_unlos_msft=1 is to exclusively enable this property. Microsoft ADO: 25941176 How I did it Changes in SAI and turning on property How to verify it Ran the changes on a testbed and verified configurations are as intended. with property admin@sonic2:~$ bcmcmd "phy diag xe8 dsc config" | grep -C 2 "LOS" Brdfe_on = 0 Media Type = 2 Unreliable LOS = 1 Scrambling Disable = 0 Lane Config from PCS = 0 without property admin@sonic:~$ bcmcmd "phy diag xe8 dsc config" | grep -C 2 "LOS" Brdfe_on = 0 Media Type = 0 Unreliable LOS = 0 Scrambling Disable = 0 Lane Config from PCS = 0 Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com> commit 245f337 Author: Feng-msft <fenpan@microsoft.com> Date: Fri Jan 12 10:51:48 2024 +0800 Fix dialout build flag issue. (sonic-net#17715) ### Why I did it Fix ENABLE_DIALOUT flag issue. ##### Work item tracking - Microsoft ADO **(number only)**: 21326000 #### How I did it Update Makefile.work and add debug string. #### How to verify it ![image](https://github.com/sonic-net/sonic-buildimage/assets/97083744/960d75d1-618c-4734-acb5-7a32a28c262b) commit b53a890 Author: Liping Xu <108326363+lipxu@users.noreply.github.com> Date: Fri Jan 12 15:26:06 2024 +0800 disable restapi for leafRouter in slim image (sonic-net#17713) Why I did it For some devices with small memory, after upgrading to the latest image, the available memory is not enough. Work item tracking Microsoft ADO (number only): 26324242 How I did it Disable restapi feature for LeafRouter which with slim image. How to verify it verified on 7050qx T1 (slim image), restapi disabled verified on 7050qx T0 (slim image), restapi enabled verified on 7260 T1 (normal image), restapi enabled commit 8561fa6 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 12 16:34:35 2024 +0800 [submodule] Update submodule sonic-utilities to the latest HEAD automatically (sonic-net#17757) #### Why I did it src/sonic-utilities ``` * 651a80b1 - (HEAD -> 202305, origin/202305) Modify teamd retry count script to base BGP status on default BGP status (sonic-net#3069) (22 hours ago) [Saikrishna Arcot] ``` #### How I did it #### How to verify it #### Description for the changelog commit 9f66a7d Author: Lawrence Lee <lawlee@microsoft.com> Date: Wed Jan 10 14:40:15 2024 -0800 add timeout to ping6 command (sonic-net#17729) Signed-off-by: Lawrence Lee <lawlee@microsoft.com> commit 13aa19a Author: Nazarii Hnydyn <nazariig@nvidia.com> Date: Wed Jan 10 15:15:55 2024 +0200 [swss/syncd]: Remove dependency on interfaces-config.service (sonic-net#17649) Signed-off-by: Nazarii Hnydyn nazariig@nvidia.com This improvement does not bring any warm-reboot degradation, since the database availability (tcp/ip access over the loopback interface) was fixed by these PRs: Re-add 127.0.0.1/8 when bringing down the interfaces sonic-net#15080 Fix potentially not having any loopback address on lo interface sonic-net#16490 Why I did it Removed dependency on interfaces-config.service to speed up the boot, because interfaces-config.service takes a lot of time on init Work item tracking N/A How I did it Changed service files for swss/syncd How to verify it Boot and check swss/syncd start time comparing to interfaces-config commit f4c15b8 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Wed Jan 10 16:34:10 2024 +0800 [submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#17731) #### Why I did it src/linkmgrd ``` * 2f5971f - (HEAD -> 202305, origin/202305) [warmboot] use config_db connector to update mux mode config instead of CLI (sonic-net#223) (4 hours ago) [Jing Zhang] ``` #### How I did it #### How to verify it #### Description for the changelog commit a3b5ea9 Author: Nazarii Hnydyn <nazariig@nvidia.com> Date: Wed Jan 10 02:56:20 2024 +0200 [sonic-cfggen]: Optimize template rendering and database access. (sonic-net#17650) Signed-off-by: Nazarii Hnydyn nazariig@nvidia.com Why I did it Improved switch init time Work item tracking N/A How I did it Replaced: sonic-cfggen -> sonic-db-cli Aggregated template list for sonic-cfggen How to verify it Run warm-reboot commit 44bc291 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Wed Jan 10 04:32:40 2024 +0800 [submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#17721) #### Why I did it src/linkmgrd ``` * 2089ab6 - (HEAD -> 202305, origin/202305) Exclude DbInterface in PR coverage check (sonic-net#224) (3 hours ago) [Jing Zhang] ``` #### How I did it #### How to verify it #### Description for the changelog commit 1337597 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Wed Jan 10 02:32:19 2024 +0800 [submodule] Update submodule sonic-snmpagent to the latest HEAD automatically (sonic-net#17722) #### Why I did it src/sonic-snmpagent ``` * e5fd192 - (HEAD -> 202305, origin/202305) Fix SNMP dropping some of the queue counter when create_only_config_db_buffers is set to true (sonic-net#303) (9 hours ago) [DavidZagury] ``` #### How I did it #### How to verify it #### Description for the changelog commit bb23f7b Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 6 16:42:00 2024 +0800 [submodule] Update submodule sonic-gnmi to the latest HEAD automatically (sonic-net#17696) commit 7ccef97 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 6 03:37:17 2024 +0800 [YANG] Enable Yang model for BGP_BBR config entry (sonic-net#17622) (sonic-net#17692) commit 8defdfe Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 6 01:15:01 2024 +0800 [submodule] Update submodule sonic-sairedis to the latest HEAD automatically (sonic-net#17691) commit b549962 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sat Jan 6 01:00:55 2024 +0800 [submodule] Update submodule sonic-gnmi to the latest HEAD automatically (sonic-net#17690) commit 02dc49a Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 15:14:43 2024 +0800 [submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#17687) commit 0d31ee8 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 02:39:03 2024 +0800 Update TELEMETRY_CLIENT YANG model (sonic-net#16861) (sonic-net#17679) commit df22ca9 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 01:04:39 2024 +0800 [Arista] Remove aggregate port config files for multi-asic devices (sonic-net#16923) (sonic-net#17678) commit ca2695f Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 00:44:19 2024 +0800 password-hardening: Add support to disable expiration date like in Linux (PAM) (sonic-net#17426) (sonic-net#17674) commit 388457a Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 00:35:07 2024 +0800 [arp_update]: Flush neighbors with incorrect MAC info (sonic-net#17238) (sonic-net#17677) commit 38c5e68 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Jan 5 00:32:38 2024 +0800 Fix can't access IPV6 address via management interface because 'default' route table does not add to route lookup issue. (sonic-net#17281) (sonic-net#17676) commit 76d8ff0 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Thu Jan 4 23:10:28 2024 +0800 Update backend_acl.py to specify ACL table name (sonic-net#17553) (sonic-net#17673) commit b72a740 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Thu Jan 4 22:37:26 2024 +0800 [docker_image_ctl.j2]: swss docker initialization improvements (sonic-net#17628) (sonic-net#17672) commit 609b3a7 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Thu Jan 4 22:29:00 2024 +0800 [image_config]: Update DHCP rate-limit for mgmt TOR devices (sonic-net#17630) (sonic-net#17671) commit 8362c09 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Tue Jan 2 15:13:53 2024 +0800 [submodule] Update submodule sonic-swss to the latest HEAD automatically (sonic-net#17642) commit 3cb6343 Author: Stepan Blyshchak <38952541+stepanblyschak@users.noreply.github.com> Date: Tue Jan 2 02:59:17 2024 +0200 [202305] Revert bgp suppress fib pending (sonic-net#17578) DEPENDS ON: sonic-net/sonic-swss#2997 sonic-net/sonic-utilities#3093 What I did Revert the feature. Why I did it Revert bgp suppress FIB functionality due to found FRR memory consumption issues and bugs. How I verified it Basic sanity check on t1-lag, regression in progress. commit 64ed3d5 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Mon Jan 1 10:31:33 2024 +0800 Fix system-health hardware_checker to consume fan tolerance details (sonic-net#16689) (sonic-net#17640) commit 98ad3b0 Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sun Dec 31 17:01:53 2023 +0800 [submodule] Update submodule sonic-utilities to the latest HEAD automatically (sonic-net#17643) commit 1398daa Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Sun Dec 31 15:20:25 2023 +0800 [submodule] Update submodule sonic-platform-daemons to the latest HEAD automatically (sonic-net#17641) commit fb83d4d Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com> Date: Fri Dec 29 01:07:45 2023 +0800 [Mellanox] wait until hw-management watchdog files ready (sonic-net#17618) (sonic-net#17633) commit a8ad19d Author: Junchao-Mellanox <57339448+Junchao-Mellanox@users.noreply.github.com> Date: Thu Dec 28 20:53:49 2023 +0800 [202305] Optimize syslog rate limit feature for fast and warm boot (sonic-net#17478) Backport PR sonic-net#17458 due to conflict. Why I did it Optimize syslog rate limit feature for fast and warm boot Work item tracking Microsoft ADO (number only): How I did it Optimize redis start time Don't render rsyslog.conf in container startup script Disable containercfgd by default. There is a new CLI to enable it (in another PR) How to verify it Manual test Regression test

vmittal-msft added the MARVELL label Aug 30, 2023

vmittal-msft added the Triaged this issue has been triaged label Aug 30, 2023

liushilongbuaa mentioned this issue Nov 15, 2023

[build] Add gpg keys for sonic-slave-bullseye in arm64 cross build on amd64. #17182

Merged

11 tasks

liushilongbuaa added the MSFT label Nov 15, 2023

lguohan closed this as completed in 27219fb Nov 16, 2023

Build Error in SONiC 202211 branch - Marvell ARM64 #16204

Build Error in SONiC 202211 branch - Marvell ARM64 #16204

Comments

thovikeerthi commented Aug 18, 2023 • edited Loading

Error Snippet: " => ERROR [internal] load metadata for docker.io/library/sonic-slave-buster-march-arm64:1d6f93e8d09 1.1s

Dockerfile.cleanup:9

7 | 8 | # Clean up the cache data 9 | >>> FROM sonic-slave-buster-march-arm64:1d6f93e8d09 as final 10 | RUN rm /cache.tgz 11 |

thovikeerthi commented Aug 22, 2023 • edited Loading

thovikeerthi commented Aug 28, 2023

vmittal-msft commented Aug 30, 2023

kishoreatreya commented Aug 30, 2023

liushilongbuaa commented Sep 14, 2023

thovikeerthi commented Sep 15, 2023

thovikeerthi commented Sep 15, 2023 • edited Loading

radha-danda commented Sep 20, 2023

liushilongbuaa commented Sep 20, 2023 • edited Loading

radha-danda commented Sep 20, 2023

thovikeerthi commented Sep 20, 2023 • edited Loading

thovikeerthi commented Sep 20, 2023

radha-danda commented Sep 21, 2023 • edited Loading

liushilongbuaa commented Sep 21, 2023

liushilongbuaa commented Sep 21, 2023

thovikeerthi commented Sep 25, 2023 • edited Loading

thovikeerthi commented Oct 3, 2023

liushilongbuaa commented Oct 7, 2023 • edited Loading

shanshri commented Oct 11, 2023

thovikeerthi commented Oct 12, 2023 • edited Loading

liushilongbuaa commented Oct 17, 2023

thovikeerthi commented Oct 19, 2023

radha-danda commented Oct 19, 2023

thovikeerthi commented Oct 19, 2023

liushilongbuaa commented Oct 20, 2023

thovikeerthi commented Oct 24, 2023

liushilongbuaa commented Oct 29, 2023

thovikeerthi commented Nov 2, 2023

liushilongbuaa commented Nov 3, 2023

thovikeerthi commented Nov 8, 2023

liushilongbuaa commented Nov 8, 2023 • edited Loading

thovikeerthi commented Nov 15, 2023 • edited Loading

liushilongbuaa commented Nov 15, 2023

liushilongbuaa commented Nov 15, 2023

thovikeerthi commented Nov 15, 2023

thovikeerthi commented Nov 15, 2023

liushilongbuaa commented Nov 15, 2023 • edited Loading

liushilongbuaa commented Nov 15, 2023

thovikeerthi commented Nov 16, 2023 • edited Loading

liushilongbuaa commented Nov 16, 2023

thovikeerthi commented Nov 23, 2023

SudharshanSuresh commented Jan 24, 2024

thovikeerthi commented Jan 24, 2024

thovikeerthi commented Aug 18, 2023 •

edited

Loading

Error Snippet:
"
=> ERROR [internal] load metadata for docker.io/library/sonic-slave-buster-march-arm64:1d6f93e8d09 1.1s

7 |
8 | # Clean up the cache data
9 | >>> FROM sonic-slave-buster-march-arm64:1d6f93e8d09 as final
10 | RUN rm /cache.tgz
11 |

thovikeerthi commented Aug 22, 2023 •

edited

Loading

thovikeerthi commented Sep 15, 2023 •

edited

Loading

liushilongbuaa commented Sep 20, 2023 •

edited

Loading

thovikeerthi commented Sep 20, 2023 •

edited

Loading

radha-danda commented Sep 21, 2023 •

edited

Loading

thovikeerthi commented Sep 25, 2023 •

edited

Loading

liushilongbuaa commented Oct 7, 2023 •

edited

Loading

thovikeerthi commented Oct 12, 2023 •

edited

Loading

liushilongbuaa commented Nov 8, 2023 •

edited

Loading

thovikeerthi commented Nov 15, 2023 •

edited

Loading

liushilongbuaa commented Nov 15, 2023 •

edited

Loading

thovikeerthi commented Nov 16, 2023 •

edited

Loading