[voq][chassis] Use system port name for BUFFER_QUEUE_TABLE in a voq chassis.#7823
Conversation
PR# 14173 (sonic-net/sonic-buildimage#14173) updates to set buffer_queue_config on system ports on a VoQ chassis. This broke the QoS tests in _getBufferProfile for BUFFER_QUEUE_TABLE Fix was to use system port name (derived from hostname and asic instance) when dealing with voq chassis and BUFFER_QUEUE_TABLE
|
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
PR# 14173 (sonic-net/sonic-buildimage#14173) updates to set buffer_queue_config on system ports on a VoQ chassis. This broke the QoS tests in _getBufferProfile for BUFFER_QUEUE_TABLE Fix was to use system port name (derived from hostname and asic instance) when dealing with voq chassis and BUFFER_QUEUE_TABLE
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
PR# 14173 (sonic-net/sonic-buildimage#14173) updates to set buffer_queue_config on system ports on a VoQ chassis.
This broke the QoS tests in _getBufferProfile for BUFFER_QUEUE_TABLE
How did you do it?
Fix was to use system port name (derived from hostname and asic instance) when dealing with voq chassis and BUFFER_QUEUE_TABLE
How did you verify/test it?
Ran QoS tests against latest 202205 based image
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation