sonic-swss
sonic-swss copied to clipboard
[202111] [PFC_WD] Avoid applying ZeroBuffer Profiles to ingress PG when a PFC storm is detected
What I did Avoid dropping traffic that is ingressing the port/pg that is in storm. The code changes in this PR avoid creating the ingress zero pool and profile and does not attach any zero profile to the ingress pg when pfcwd is triggered
Revert changes related to #1480 where the retry mechanism was added to BufferOrch which caches the task retries and while the PG is locked by PfcWdZeroBufferHandler.
Revert changes related to #2164 in PfcWdZeroBufferHandler & ZeroBufferProfile & BufferOrch.
Updated UT's accordingly
Signed-off-by: Vivek Reddy Karri [email protected]
What I did
Why I did it
How I verified it
Details if related
/azpw run Azure.sonic-swss
/AzurePipelines run Azure.sonic-swss
Azure Pipelines successfully started running 1 pipeline(s).
@neethajohn Please signoff.
/azpw run Azure.sonic-swss
/AzurePipelines run Azure.sonic-swss
Azure Pipelines successfully started running 1 pipeline(s).
/azp run Azure.sonic-swss
Azure Pipelines successfully started running 1 pipeline(s).
/azpw run Azure.sonic-swss
/AzurePipelines run Azure.sonic-swss
Azure Pipelines successfully started running 1 pipeline(s).
/azpw run Azure.sonic-swss
/AzurePipelines run Azure.sonic-swss
Azure Pipelines successfully started running 1 pipeline(s).
/azpw run Azure.sonic-swss
/AzurePipelines run Azure.sonic-swss
Azure Pipelines successfully started running 1 pipeline(s).
/azp run Azure.sonic-swss
/easycla
Azure Pipelines successfully started running 1 pipeline(s).
/azpw run Azure.sonic-swss
/azpw run Azure.sonic-swss
/AzurePipelines run Azure.sonic-swss
Azure Pipelines successfully started running 1 pipeline(s).
/azpw run Azure.sonic-swss
@judyjoseph Looks like the build job (Azure.sonic-swss (Build amd64)) is itself failing now
Closing this PR. A label is added to https://github.com/sonic-net/sonic-swss/pull/2304 which is cherry-pickable.