Skip to content

[202511] Continue CMIS state even if Decommission fails#859

Merged
vmittal-msft merged 1 commit into
sonic-net:202511from
prgeor:decom
Jul 22, 2026
Merged

[202511] Continue CMIS state even if Decommission fails#859
vmittal-msft merged 1 commit into
sonic-net:202511from
prgeor:decom

Conversation

@prgeor

@prgeor prgeor commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Description

[202511] Cherry pick of #842

Motivation and Context

This PR moved the DP decommission to normal DP activation flow. Previously when there was a failure (some module DONT'T accept appl=0 even for DP decommission), the state machine used to proceed with the retry because on retry, the appl got set to the desired. This PR ignores the failure and continues the datapath initialization with the selected application anways (restoring the status quo for these modules)

How Has This Been Tested?

Validated this on the buggy module which was failing DP decommission.

Additional Information (Optional)

Signed-off-by: Prince George <prgeor@microsoft.com>
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

@vmittal-msft
vmittal-msft merged commit bf691af into sonic-net:202511 Jul 22, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants