Remove buffer drop counter when port is deleted#1860
Remove buffer drop counter when port is deleted#1860liat-grozovik merged 1 commit intosonic-net:masterfrom
Conversation
|
/azpw run |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 1860 in repo Azure/sonic-swss |
|
i have these failures on the swss checkers:
vs tests: it looks not related to my change and I also saw the same errors on this PR (the PR is not related to our PR): so maybe we need to rerun these tests |
|
@stephenxs could you pls help to review? |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
the errors on the checkers are not related to my change at all, the test is checking number of routes in the system: |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
the checkers were failed due to: this error is not related to code change. please rerun the checkers |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
Commenter does not have sufficient privileges for PR 1860 in repo Azure/sonic-swss |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Just retriggered LGTM analysis: C/C++. |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
failures not related to this change - rerun /azpw run |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: tomeri <[email protected]>
7019a19
0ce6ba4 to
7019a19
Compare
|
@neethajohn and @stephenxs could you please help to review? |
- What I did I added the removal of port buffer drop counter on the deinit port flow. it was added to the deInitPort function. - Why I did it the buffer drop counter was never removed when port was deleted. this flex counter was create on the initPort function but it was removed when the port was deleted - How I verified it removed and created a port and check the FLEX_COUNTER redis table FLEX_COUNTER_TABLE:PORT_BUFFER_DROP_STAT table
Signed-off-by: tomeri [email protected]
What I did
I added the removal of port buffer drop counter on the deinit port flow.
it was added to the deInitPort function.
Why I did it
the buffer drop counter was never removed when port was deleted.
this flex counter was create on the initPort function but it was removed when the port was deleted
How I verified it
removed and created a port and check the FLEX_COUNTER redis table
FLEX_COUNTER_TABLE:PORT_BUFFER_DROP_STAT table
Details if related