-
Notifications
You must be signed in to change notification settings - Fork 750
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
Fix portstat case #6148
Fix portstat case #6148
Conversation
Becuase desigin change for "portstat -c -t filename", so change portstat test 1. Orignal design: After running “portstat -c -t filename”, status file will be created on the folder of /tmp/portstat-{uid}/{uid}-{filename} 2. New design: After running “portstat -c -t filename”, status file will be created on the folder of /tmp/cache/portstat/{uid}-{filename} Change-Id: Ia122a08b9a55a26fe6a299d74d2df1f1949c7ca3
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/azp run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Can we add backwards compatibility to this function? For example:
|
The bug fixes: sonic-net/sonic-buildimage#11244, sonic-net/sonic-utilities#2232, which should be backported to branch 202205. |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
Thank you for clarification. In case of fix being backported, OS version check is not needed. |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
Becuase desigin change for "portstat -c -t filename", so change portstat test 1. Orignal design: After running “portstat -c -t filename”, status file will be created on the folder of /tmp/portstat-{uid}/{uid}-{filename} 2. New design: After running “portstat -c -t filename”, status file will be created on the folder of /tmp/cache/portstat/{uid}-{filename} Change-Id: Ia122a08b9a55a26fe6a299d74d2df1f1949c7ca3
Becuase desigin change for "portstat -c -t filename", so change portstat test 1. Orignal design: After running “portstat -c -t filename”, status file will be created on the folder of /tmp/portstat-{uid}/{uid}-{filename} 2. New design: After running “portstat -c -t filename”, status file will be created on the folder of /tmp/cache/portstat/{uid}-{filename} Change-Id: Ia122a08b9a55a26fe6a299d74d2df1f1949c7ca3
Becuase desigin change for "portstat -c -t filename", so change portstat test 1. Orignal design: After running “portstat -c -t filename”, status file will be created on the folder of /tmp/portstat-{uid}/{uid}-{filename} 2. New design: After running “portstat -c -t filename”, status file will be created on the folder of /tmp/cache/portstat/{uid}-{filename} Change-Id: Ia122a08b9a55a26fe6a299d74d2df1f1949c7ca3
There is a bug fix for "portstat -c -t filename" which changes the path of portstat status file, so we need to update the relevant portstat test:
sonic-net/sonic-utilities#2232
sonic-net/sonic-buildimage#11244
Change-Id: Ia122a08b9a55a26fe6a299d74d2df1f1949c7ca3
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Fix test issue, because there is a relevant bug fix for the product.
How did you do it?
Change the test as the new desgin.
How did you verify/test it?
Run the tests on the image with bug fix
Any platform specific information?
Any
Supported testbed topology if it's a new test case?
Any
Documentation