Fix for PID assertion issue - PSUD and CHASSID platform cases#7781
Fix for PID assertion issue - PSUD and CHASSID platform cases#7781wenyiz2021 merged 2 commits intosonic-net:masterfrom
Conversation
|
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:
|
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
Fix for PID assertion - Typo Error Fixing up other chassisd and psud tests to poll for deamon to restart with bigger pid than before
|
@sanjair-git PR conflicts with 202205 branch |
…net#7781) Fix for PID assertion issue - PSUD and CHASSID platform cases Fixing up other chassisd and psud tests to poll for deamon to restart with bigger pid than before --------- Co-authored-by: sanmalho <sandeep.malhotra@nokia.com>
…#8776) Fix for PID assertion issue - PSUD and CHASSID platform cases Fixing up other chassisd and psud tests to poll for deamon to restart with bigger pid than before --------- Cherry-Pick PR #7781 : For resolving conflicts. Fix for PID assertion issue - PSUD and CHASSID platform cases. Description of PR Fixing up other chassisd and psud platform tests to poll for deamon to restart with bigger pid than before. This is an extension of PR #7150. Summary: Fixes # (issue) Fixes PSUD 'stop & start', 'term & start' and 'kill & start' test cases by making sure the daemon restarted has bigger PID than before. Fixes CHASSID 'stop & start' and 'kill & start' test cases by making sure the daemon restarted has bigger PID than before. Type of change Bug fix Testbed and Framework(new/improvement) Test case(new/improvement) Back port request 201911 202012 202205 Approach What is the motivation for this PR? Currently PSUD and CHASSID platform test cases like 'term & start', 'kill & start' and 'stop & start' don't check if the restarted daemon has bigger pid than the previous one or not. Currently "check_expected_daemon_status" doesn't verify about pre-daemon-pid, just returns TRUE even if the status is RUNNING with old PID. How did you do it? By invoking 'check_if_daemon_restarted' method on the above-mentioned cases and making sure the new pid is bigger than the old pid. How did you verify/test it? Ran the respective platform tests against a multi-asic line card in a T2 chassis. Co-authored-by: sanmalho <sandeep.malhotra@nokia.com>, jianquanye@microsoft.com
…net#7781) Fix for PID assertion issue - PSUD and CHASSID platform cases Fixing up other chassisd and psud tests to poll for deamon to restart with bigger pid than before --------- Co-authored-by: sanmalho <sandeep.malhotra@nokia.com>
…net#7781) Fix for PID assertion issue - PSUD and CHASSID platform cases Fixing up other chassisd and psud tests to poll for deamon to restart with bigger pid than before --------- Co-authored-by: sanmalho <sandeep.malhotra@nokia.com>
Description of PR
Fixing up other chassisd and psud platform tests to poll for deamon to restart with bigger pid than before.
This is an extension of PR #7150.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation