Use CHASSIS_FABRIC_ASIC_TABLE instead of CHASSIS_ASIC_TABLE#7090
Merged
SuvarnaMeenakshi merged 1 commit intosonic-net:masterfrom Feb 21, 2023
Merged
Use CHASSIS_FABRIC_ASIC_TABLE instead of CHASSIS_ASIC_TABLE#7090SuvarnaMeenakshi merged 1 commit intosonic-net:masterfrom
SuvarnaMeenakshi merged 1 commit intosonic-net:masterfrom
Conversation
6 tasks
SuvarnaMeenakshi
approved these changes
Feb 11, 2023
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wangxin
pushed a commit
that referenced
this pull request
Feb 23, 2023
Fixes # (issue) In 'CHASSIS_STATE_DB' the table 'CHASSIS_ASIC_TABLE' has changed to 'CHASSIS_FABRIC_ASIC_TABLE' This was being used to set the critical services based on the fabric asics that were present. W/out this change, the asic level services were not getting added to the critical services list and not being validated in the sanity check. What is the motivation for this PR? In 'CHASSIS_STATE_DB' the table 'CHASSIS_ASIC_TABLE' has changed to 'CHASSIS_FABRIC_ASIC_TABLE' This was being used to set the critical services based on the fabric asics that were present. W/out this change, the asic level services were not getting added to the critical services list and not being validated in the sanity check. How did you do it? Modified 'CHASSIS_ASIC_TABLE' to 'CHASSIS_FABRIC_ASIC_TABLE' in critical_services_tracking_list function.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
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?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation