Add sai call to isolate/unisolate a fabric port #3141
Conversation
orchagent/fabricportsorch.cpp
Outdated
| } | ||
| else | ||
| { | ||
| SWSS_LOG_NOTICE( "JFJF same isolation status for %d", lane); |
There was a problem hiding this comment.
nit: fix this logs message?
There was a problem hiding this comment.
nit: fix this logs message?
good catch. fixed. thank you !
|
tests failed with some " 'Invalid response from docker daemon: key "ApiVersion"' ' is missing.' . Not related to this chagne, will restart the tests pipeline |
|
/azpw run Azure.sonic-swss |
|
/AzurePipelines run Azure.sonic-swss |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
test_chassis_system_lag_id_allocator_table_full failed (1 runs remaining out of 2). not related to this chagne |
|
/azpw run Azure.sonic-swss |
|
/AzurePipelines run Azure.sonic-swss |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
test_chassis_system_lag_id_allocator_table_full failed (1 runs remaining out of 2). not related to this chagne |
@jfeng-arista , looking into it |
thank you ! this failure seems affecting almost all PRs in swss . |
|
@prsunny can you help merge this PR |
|
we can, just that it will not be protected under than toggle. |
|
the failure not related to this change, it is synced down . |
|
/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). |
|
test failures are from upstream, not related to this change. |
Add sai call for isolate/unisolate the fabric links.
Please merge this up after #3132
What I did
Why I did it
How I verified it
Details if related