[Smartswitch][nvidia-bluefield]Add watchdog device mount for pmon#24746
Merged
liat-grozovik merged 3 commits intosonic-net:masterfrom Jan 12, 2026
Merged
[Smartswitch][nvidia-bluefield]Add watchdog device mount for pmon#24746liat-grozovik merged 3 commits intosonic-net:masterfrom
liat-grozovik merged 3 commits intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
oleksandrivantsiv
approved these changes
Dec 4, 2025
vvolam
approved these changes
Dec 11, 2025
Signed-off-by: gpunathilell <[email protected]>
ef1de80 to
dbdee09
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run Azure.sonic-buildimage |
Collaborator
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
liat-grozovik
approved these changes
Jan 12, 2026
Collaborator
|
Cherry-pick PR to 202511: #25059 |
Collaborator
|
@gpunathilell cherry pick PR didn't pass PR checker. Please check!!! |
SahilChaudhari
pushed a commit
to SahilChaudhari/sonic-buildimage-sonic-net
that referenced
this pull request
Jan 21, 2026
…nic-net#24746) - Why I did it The watchdog arm/disarm will fail in the pmon container with the following error: root@sonic:/# mlxbf-bootctl /dev/mmcblk0: No such file or directory root@sonic:/# Because the container hardening feature required explicit device mounting. This is fixed by mounting the dpu watchdog device for the pmon container, since we have platform apis in the containers which are called during sonci-mgmt tests - How I did it Mount the DPU watchdog relevant device. - How to verify it Arm/check the watchdog status in the pmon container, with the watchdog platform api object. Signed-off-by: gpunathilell <[email protected]> Co-authored-by: Sudharsan Dhamal Gopalarathnam <[email protected]>
jasonbridges
pushed a commit
to jasonbridges/sonic-buildimage
that referenced
this pull request
Jan 22, 2026
…nic-net#24746) - Why I did it The watchdog arm/disarm will fail in the pmon container with the following error: root@sonic:/# mlxbf-bootctl /dev/mmcblk0: No such file or directory root@sonic:/# Because the container hardening feature required explicit device mounting. This is fixed by mounting the dpu watchdog device for the pmon container, since we have platform apis in the containers which are called during sonci-mgmt tests - How I did it Mount the DPU watchdog relevant device. - How to verify it Arm/check the watchdog status in the pmon container, with the watchdog platform api object. Signed-off-by: gpunathilell <[email protected]> Co-authored-by: Sudharsan Dhamal Gopalarathnam <[email protected]>
spandan-nexthop
pushed a commit
to spandan-nexthop/sonic-buildimage
that referenced
this pull request
Feb 15, 2026
…nic-net#24746) - Why I did it The watchdog arm/disarm will fail in the pmon container with the following error: root@sonic:/# mlxbf-bootctl /dev/mmcblk0: No such file or directory root@sonic:/# Because the container hardening feature required explicit device mounting. This is fixed by mounting the dpu watchdog device for the pmon container, since we have platform apis in the containers which are called during sonci-mgmt tests - How I did it Mount the DPU watchdog relevant device. - How to verify it Arm/check the watchdog status in the pmon container, with the watchdog platform api object. Signed-off-by: gpunathilell <[email protected]> Co-authored-by: Sudharsan Dhamal Gopalarathnam <[email protected]>
baorliu
pushed a commit
to baorliu/sonic-buildimage
that referenced
this pull request
Feb 24, 2026
…nic-net#24746) - Why I did it The watchdog arm/disarm will fail in the pmon container with the following error: root@sonic:/# mlxbf-bootctl /dev/mmcblk0: No such file or directory root@sonic:/# Because the container hardening feature required explicit device mounting. This is fixed by mounting the dpu watchdog device for the pmon container, since we have platform apis in the containers which are called during sonci-mgmt tests - How I did it Mount the DPU watchdog relevant device. - How to verify it Arm/check the watchdog status in the pmon container, with the watchdog platform api object. Signed-off-by: gpunathilell <[email protected]> Co-authored-by: Sudharsan Dhamal Gopalarathnam <[email protected]>
FengPan-Frank
pushed a commit
to FengPan-Frank/sonic-buildimage
that referenced
this pull request
Mar 6, 2026
…nic-net#24746) - Why I did it The watchdog arm/disarm will fail in the pmon container with the following error: root@sonic:/# mlxbf-bootctl /dev/mmcblk0: No such file or directory root@sonic:/# Because the container hardening feature required explicit device mounting. This is fixed by mounting the dpu watchdog device for the pmon container, since we have platform apis in the containers which are called during sonci-mgmt tests - How I did it Mount the DPU watchdog relevant device. - How to verify it Arm/check the watchdog status in the pmon container, with the watchdog platform api object. Signed-off-by: gpunathilell <[email protected]> Co-authored-by: Sudharsan Dhamal Gopalarathnam <[email protected]> Signed-off-by: Feng Pan <[email protected]>
kalash-nexthop
pushed a commit
to kalash-nexthop/sonic-buildimage
that referenced
this pull request
Mar 13, 2026
…nic-net#24746) - Why I did it The watchdog arm/disarm will fail in the pmon container with the following error: root@sonic:/# mlxbf-bootctl /dev/mmcblk0: No such file or directory root@sonic:/# Because the container hardening feature required explicit device mounting. This is fixed by mounting the dpu watchdog device for the pmon container, since we have platform apis in the containers which are called during sonci-mgmt tests - How I did it Mount the DPU watchdog relevant device. - How to verify it Arm/check the watchdog status in the pmon container, with the watchdog platform api object. Signed-off-by: gpunathilell <[email protected]> Co-authored-by: Sudharsan Dhamal Gopalarathnam <[email protected]> Signed-off-by: Kalash Nainwal <[email protected]>
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
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.
Why I did it
The watchdog arm/disarm will fail in the pmon container with the following error:
Because the container hardening feature required explicit device mounting. This is fixed by mounting the dpu watchdog device for the pmon container, since we have platform apis in the containers which are called during sonci-mgmt tests
Work item tracking
How I did it
Mount the DPU watchdog relevant device.
How to verify it
Arm/check the watchdog status in the pmon container, with the watchdog platform api object.
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)