You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the test test voq/test_fabric_cli_and_db.py::test_fabric_cli_isolate_supervisor on t2 topo with voq chassis.
This was tested with t2 topo and Nokia chassis running 202405 based image.
I see that after the test completes it does not restore the port to its initial isolate state if initial state was False.
After analyzing the logs I found unisolate is never called the reason being 'originalIsolateStatus' is being overwritten after changing the fabric port isolate state incorrectly.
Results you see
I see after the test completes the the isolate state of fabric port is not false it is still true. See below output the manual isolate is true and port is still isolated
asic4
Local Link Auto Isolated Manual Isolated Isolated
Issue Description
Run the test test voq/test_fabric_cli_and_db.py::test_fabric_cli_isolate_supervisor on t2 topo with voq chassis.
This was tested with t2 topo and Nokia chassis running 202405 based image.
I see that after the test completes it does not restore the port to its initial isolate state if initial state was False.
After analyzing the logs I found unisolate is never called the reason being 'originalIsolateStatus' is being overwritten after changing the fabric port isolate state incorrectly.
Results you see
I see after the test completes the the isolate state of fabric port is not false it is still true. See below output the manual isolate is true and port is still isolated
asic4
Local Link Auto Isolated Manual Isolated Isolated
From log the original state was False
DEBUG tests.common.devices.base:base.py:71 /data/tests/common/devices/multi_asic.py::_run_on_asics#135: [ixre-cpm-chassis19] AnsibleModule::shell, args=["sonic-db-cli -n asic4 CONFIG_DB hget 'FABRIC_PORT|Fabric32' isolateStatus"], kwargs={"module_ignore_errors": true}
DEBUG tests.common.devices.base:base.py:108 /data/tests/common/devices/multi_asic.py::_run_on_asics#135: [ixre-cpm-chassis19] AnsibleModule::shell Result => {"changed": true, "stdout": "False", "stderr": "", "rc": 0, "cmd": "sonic-db-cli -n asic4 CONFIG_DB hget 'FABRIC_PORT|Fabric32' isolateStatus", "start": "2024-12-12 23:07:24.491393", "end": "2024-12-12 23:07:24.511762", "delta": "0:00:00.020369", "msg": "", "invocation": {"module_args": {"_raw_params": "sonic-db-cli -n asic4 CONFIG_DB hget 'FABRIC_PORT|Fabric32' isolateStatus", "_uses_shell": true, "warn": false, "stdin_add_newline": true, "strip_empty_ends": true, "argv": null, "chdir": null, "executable": null, "creates": null, "removes": null, "stdin": null}}, "stdout_lines": ["False"], "stderr_lines": [], "_ansible_no_log": null, "failed": false}
DEBUG tests.voq.test_fabric_cli_and_db:test_fabric_cli_and_db.py:214 originalIsolateStatus: False
Results you expected to see
The test should rever fabric port from isolate to unisolate if original state was unisolated
Is it platform specific
generic
Relevant log output
No response
Output of
show version
No response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered: