Description
On a multi-asic DUT, after we issue a sonic-installer install command, all SONIC commands produces a backtrace and exits w/out executing the command after a long time.
A 'sudo reboot' command does reboot the DUT, but only after the exception is thrown after a long time.
Steps to reproduce the issue:
- Run a show command like 'show feature status'
- Run sonic-install install to install an new image that doesn't exit on the DUT.
- Run the show command again.
Describe the results you received:
admin@sonic:~$ show feature status
Feature State AutoRestart SetOwner
-------------- --------------- -------------- ----------
bgp enabled enabled
database always_enabled always_enabled
dhcp_relay enabled enabled local
lldp enabled enabled
macsec disabled enabled
mgmt-framework enabled enabled
mux always_disabled enabled
nat disabled enabled
pmon enabled enabled
radv enabled enabled
sflow disabled enabled
snmp enabled enabled
swss enabled enabled
syncd enabled enabled
teamd enabled enabled
telemetry enabled enabled
admin@sonic:~$
admin@sonic:~$ sudo sonic-installer install /tmp/sonic-broadcom-dnx.bin -y
Installing image SONiC-OS-HEAD.230935-dirty-20220301.182109 and setting it as default...
Command: bash /tmp/sonic_image
Verifying image checksum ... OK.
Preparing image archive ... OK.
Installing SONiC in SONiC
ONIE Installer: platform: x86_64-broadcom-dnx-r0
onie_platform: x86_64-nokia_ixr7250e_sup-r0
Removing old SONiC installation /host/image-HEAD.231265-dirty-20220302.011117
Installing SONiC to /host/image-HEAD.230935-dirty-20220301.182109
.
.
.
admin@sonic:~$ show feature status
Traceback (most recent call last):
File "/usr/local/bin/show", line 5, in <module>
from show.main import cli
File "/usr/local/lib/python3.9/dist-packages/show/main.py", line 8, in <module>
import utilities_common.cli as clicommon
File "/usr/local/lib/python3.9/dist-packages/utilities_common/cli.py", line 189, in <module>
iface_alias_converter = InterfaceAliasConverter()
File "/usr/local/lib/python3.9/dist-packages/utilities_common/cli.py", line 126, in __init__
self.port_dict = multi_asic.get_port_table()
File "/usr/local/lib/python3.9/dist-packages/sonic_py_common/multi_asic.py", line 295, in get_port_table
ports = get_port_table_for_asic(ns)
File "/usr/local/lib/python3.9/dist-packages/sonic_py_common/multi_asic.py", line 309, in get_port_table_for_asic
config_db = connect_config_db_for_ns(namespace)
File "/usr/local/lib/python3.9/dist-packages/sonic_py_common/multi_asic.py", line 43, in connect_config_db_for_ns
config_db.connect()
File "/usr/lib/python3/dist-packages/swsscommon/swsscommon.py", line 1829, in connect
return _swsscommon.ConfigDBConnector_Native_connect(self, wait_for_init, retry_on)
RuntimeError: Unable to connect to redis: Cannot assign requested address
admin@sonic:~$
Describe the results you expected:
Don't expect to see the backtrace and commands should execute.
Output of show version:
Output of show techsupport:
(paste your output here or download and attach the file here )
Additional information you deem important (e.g. issue happens only occasionally):
Description
On a multi-asic DUT, after we issue a sonic-installer install command, all SONIC commands produces a backtrace and exits w/out executing the command after a long time.
A 'sudo reboot' command does reboot the DUT, but only after the exception is thrown after a long time.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Don't expect to see the backtrace and commands should execute.
Output of
show version:Output of
show techsupport:Additional information you deem important (e.g. issue happens only occasionally):