[GCU] Adding t2 support in gcu lo test case#17293
[GCU] Adding t2 support in gcu lo test case#17293judyjoseph merged 4 commits intosonic-net:masterfrom
Conversation
|
/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). |
|
Hello, This test case fails if it gonna be enabled for multi-asic. The test case is suppossed to change the Loopback interface under /localhost namespace. After that change running database has these values: As you can see there is an incosistency for Loopback0 between /localhost and asic namespaces. The test verifies based on Which means the cli command "show ip int" fetches values based on namespaces cfg? I am not sure what is the expected here. We can modify the patch to apply change in localhost as well as in all asic namespaces in case of multiasci duthost and that will pass the case, Thanks, |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@okaravasi there is a predependency check which is failing can you check |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: opcoder0 <[email protected]>
Signed-off-by: Guy Shemesh <[email protected]>
Signed-off-by: Aharon Malkin <[email protected]>
Signed-off-by: Guy Shemesh <[email protected]>
Signed-off-by: Guy Shemesh <[email protected]>
Signed-off-by: Yael Tzur <[email protected]>
Description of PR
The original change was included in https://github.com/sonic-net/sonic-mgmt/pull/15236/files.
However, the code changes were handled in a different PR. This PR only adds support for T2.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Ran in kvm-t0, t2 chassis.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation