-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[multi-asic]: remove load_sonic_global_db_config calls #8173
Conversation
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <arlakshm@microsoft.com>
The vstest failure is relating this PR
|
if is_multi_asic(): | ||
swsscommon.SonicDBConfig.load_sonic_global_db_config() | ||
else: | ||
swsscommon.SonicDBConfig.initialize() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocking issue. You may use load_sonic_db_config
which is available in both swsscommon and swsssdk. #Closed
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <arlakshm@microsoft.com>
Hi Qi,
To prevent this error, added a new function |
/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). |
/Azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
#### Why I did it Remove the call to `SonicDBConfig.load_sonic_global_db_config()` in the multi asic functions. The expection is the client calling this function will call `SonicDBConfig.load_sonic_global_db_config()` This PR is dependent on the PR sonic-net/sonic-utilities#1712 #### How to verify it compile sonic-utilities
What I did Recent change was done to remove call to load database global_db which expects the clients to load global_db. [sonic-net/sonic-buildimage#8173] The load global_db was missing in multi_asic.py which was causing "show interfaces cli" to fail. While testing on multi-asic VS image: How I did it load global_db config in multi_asic.py. How to verify it Load multi-asic VS image with the fix. Signed-off-by: Suvarna Meenakshi <sumeenak@microsoft.com>
What I did Recent change was done to remove call to load database global_db which expects the clients to load global_db. [sonic-net/sonic-buildimage#8173] The load global_db was missing in multi_asic.py which was causing "show interfaces cli" to fail. While testing on multi-asic VS image: How I did it load global_db config in multi_asic.py. How to verify it Load multi-asic VS image with the fix. Signed-off-by: Suvarna Meenakshi <sumeenak@microsoft.com>
What is the motivation for this PR? With the changes in sonic-net/sonic-buildimage#8173, the applications that connect to namespace dbs have to load global database configuration. Due to this change, the sonic-py-common.multi_asic functions that connect to database will fail if database configuration is not loaded in ansible library functions. How did you do it? Add a new module_utility library function to load the right db configuration based on single or multi-asic platform. Invoke this function in port_util and lag_facts where mutli_asic library function is invoked which connects to db. How did you verify/test it? Bring up a multi-asic VS testbed. ./testbed-cli.sh -t vtestbed.csv -m veos_vtb -k ceos add-topo vms-kvm-four-asic-t1-lag password.txt Before adding this change, failure seen while running test_bgp_fact.py
#### Why I did it Remove the call to `SonicDBConfig.load_sonic_global_db_config()` in the multi asic functions. The expection is the client calling this function will call `SonicDBConfig.load_sonic_global_db_config()` This PR is dependent on the PR sonic-net/sonic-utilities#1712 #### How to verify it compile sonic-utilities
What is the motivation for this PR? With the changes in sonic-net/sonic-buildimage#8173, the applications that connect to namespace dbs have to load global database configuration. Due to this change, the sonic-py-common.multi_asic functions that connect to database will fail if database configuration is not loaded in ansible library functions. How did you do it? Add a new module_utility library function to load the right db configuration based on single or multi-asic platform. Invoke this function in port_util and lag_facts where mutli_asic library function is invoked which connects to db. How did you verify/test it? Bring up a multi-asic VS testbed. ./testbed-cli.sh -t vtestbed.csv -m veos_vtb -k ceos add-topo vms-kvm-four-asic-t1-lag password.txt Before adding this change, failure seen while running test_bgp_fact.py
What I did Recent change was done to remove call to load database global_db which expects the clients to load global_db. [sonic-net/sonic-buildimage#8173] The load global_db was missing in multi_asic.py which was causing "show interfaces cli" to fail. While testing on multi-asic VS image: How I did it load global_db config in multi_asic.py. How to verify it Load multi-asic VS image with the fix. Signed-off-by: Suvarna Meenakshi <sumeenak@microsoft.com>
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan arlakshm@microsoft.com
Why I did it
Remove the call to
SonicDBConfig.load_sonic_global_db_config()
in the multi asic functions.The expection is the client calling this function will call
SonicDBConfig.load_sonic_global_db_config()
This PR is dependent on the PR sonic-net/sonic-utilities#1712
How to verify it
compile sonic-utilities
Which release branch to backport (provide reason below if selected)
Description for the changelog
A picture of a cute animal (not mandatory but encouraged)