-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Start fabric mgr daemon in swss container. #17473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start fabric mgr daemon in swss container. #17473
Conversation
/Azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
the failure seems not related to the change /Azpw run Azure.sonic-buildimage |
/Azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/Azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
2023-12-13T21:09:29.8376752Z Test plan id: 657a0283cfacd86e78e3e907, status: EXECUTING, progress: 91.67%, elapsed: 5169 seconds failed as abvoe, not sure if this could related to my change as it is in t0. I will retirgger the pipline tomorrow |
/Azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
…mands. (#10994) Summary: Add mgmt test for testing fabric link isolation cli commands. This change adds a test for the fabric link isolation command. The test iterates over the fabric links on a linecard. It isolates and unisolates fabric links. Each time the state of the link is changed the state is checked in both CONFIG_DB and APPL_DB. The values in CONFIG_DB are updated by the fabric CLI commands and the values in APPL_DB are updated by the fabric manager daemon. The test check if the 2 major part work as expected. need to wait sonic-net/sonic-buildimage#17473 Signed-off-by: Jie Feng <[email protected]>
@lguohan, can you help merge this PR |
The fabricmgr daemon started in vs environment for testing from sonic-net#16791, we now start the daemon in product code.
The fabricmgr daemon started in vs environment for testing from sonic-net#16791, we now start the daemon in product code.
Why I did it
The fabricmgr daemon started in vs environment for testing from #16791, we now start the daemon in product code.
Work item tracking
How I did it
Start fabric mgr daemon in swss container .
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)