-
Notifications
You must be signed in to change notification settings - Fork 537
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 the issue when persistent DVS is used to run pytest which has number of front-panel ports < 32 #1373
Conversation
and ports are created dynamically (ref pr: sonic-net/sonic-buildimage#4499). There were two issues: a) since number of dynamic front port can be < 32 test case fails as it expect always 32. Make sure to udpate persitent DVS to always have 32 ports/server link as part of test run and save the current config db b) after test is done persistent DVS need to be moved to original state. Make dure to remove extra port/server link and restore back config db Signed-off-by: Abhishek Dosi <[email protected]>
Which tests are always expecting 32 ports? I am OK with this change as a short-term fix, but I think the real issue here is that the tests are hard-coded for 32 ports instead of checking in the Config DB. We should open an issue and track this. |
Signed-off-by: Abhishek Dosi <[email protected]>
@daall . Many test case are using hard-coded server indexing For eg: test_fdb_update.py we use dvs.servers[17].runcmd |
ack, I will open an issue to track this. Thanks for pointing this out! |
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.
lgtm, please wait for @lguohan's review
retest this please |
2 similar comments
retest this please |
retest this please |
retest this please |
1 similar comment
retest this please |
@lguohan can you review this. |
retest this please |
1 similar comment
retest this please |
maybe we can just check if persistent dvs has 32 ports, if not, then we just abort and say persistent dvs has to be 32 ports instead of reconfiguration here? |
@lguohan i think it is better to keep using existing persistent dvs and we can run pytest on top of that |
Updated Readme Signed-off-by: Abhishek Dosi <[email protected]>
This pull request introduces 1 alert and fixes 12 when merging d821218 into 879f45b - view on LGTM.com new alerts:
fixed alerts:
|
Signed-off-by: Abhishek Dosi <[email protected]>
This pull request introduces 1 alert and fixes 12 when merging 6629b67 into 879f45b - view on LGTM.com new alerts:
fixed alerts:
|
Signed-off-by: Abhishek Dosi <[email protected]>
Co-authored-by: Danny Allen <[email protected]>
retest vs please |
Why/What I did
Fix the issue where persistent DVS is used to run pytest
and ports are created dynamically (ref pr#
sonic-net/sonic-buildimage#4499). There were two
issues:
How I verified it
a) Verified Persistent DVS < 32 ports without forcedvs option then abort else DVS restarted with 32 ports.
b) Manually Verified VS Docker has correct interface config/port.ini/ip link after test is completed and restored original config db
c) Verified on host ip netns list has expected server link only after is completed