-
Notifications
You must be signed in to change notification settings - Fork 708
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 flaky test_reload_configuration_checks when all processes are not… #14218
Fix flaky test_reload_configuration_checks when all processes are not… #14218
Conversation
@tudupa please fix the build errors |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
@tudupa Can you please help comment |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
… up during swss stop job
4a9fc7e
to
4aaa76c
Compare
@bingwang-ms @yxieca Can you please help add approval tag for backport 202405/202311, thank you! |
… up during swss stop job (sonic-net#14218) What is the motivation for this PR? The testcase test_reload_configuration_checks fails sometimes when swss is stopped after a config reload and some of the critical processes are still coming up. The stop job of swss in the queue is cancelled due to other critical processes still coming up and trying to bring up swss. Hence, we get the error - "Job for swss.service cancelled" How did you do it? This PR enhanced the testcase to wait until all the critical processes are up after a config reload and then execute a stop job for swss. How did you verify/test it? Ran the testcase 15-20 times to see if it fails.
Cherry-pick PR to 202405: #14298 |
… up during swss stop job (sonic-net#14218) What is the motivation for this PR? The testcase test_reload_configuration_checks fails sometimes when swss is stopped after a config reload and some of the critical processes are still coming up. The stop job of swss in the queue is cancelled due to other critical processes still coming up and trying to bring up swss. Hence, we get the error - "Job for swss.service cancelled" How did you do it? This PR enhanced the testcase to wait until all the critical processes are up after a config reload and then execute a stop job for swss. How did you verify/test it? Ran the testcase 15-20 times to see if it fails.
Cherry-pick PR to 202311: #14302 |
… up during swss stop job (#14218) What is the motivation for this PR? The testcase test_reload_configuration_checks fails sometimes when swss is stopped after a config reload and some of the critical processes are still coming up. The stop job of swss in the queue is cancelled due to other critical processes still coming up and trying to bring up swss. Hence, we get the error - "Job for swss.service cancelled" How did you do it? This PR enhanced the testcase to wait until all the critical processes are up after a config reload and then execute a stop job for swss. How did you verify/test it? Ran the testcase 15-20 times to see if it fails.
… up during swss stop job (#14218) What is the motivation for this PR? The testcase test_reload_configuration_checks fails sometimes when swss is stopped after a config reload and some of the critical processes are still coming up. The stop job of swss in the queue is cancelled due to other critical processes still coming up and trying to bring up swss. Hence, we get the error - "Job for swss.service cancelled" How did you do it? This PR enhanced the testcase to wait until all the critical processes are up after a config reload and then execute a stop job for swss. How did you verify/test it? Ran the testcase 15-20 times to see if it fails.
… up during swss stop job (sonic-net#14218) What is the motivation for this PR? The testcase test_reload_configuration_checks fails sometimes when swss is stopped after a config reload and some of the critical processes are still coming up. The stop job of swss in the queue is cancelled due to other critical processes still coming up and trying to bring up swss. Hence, we get the error - "Job for swss.service cancelled" How did you do it? This PR enhanced the testcase to wait until all the critical processes are up after a config reload and then execute a stop job for swss. How did you verify/test it? Ran the testcase 15-20 times to see if it fails.
… up during swss stop job (sonic-net#14218) What is the motivation for this PR? The testcase test_reload_configuration_checks fails sometimes when swss is stopped after a config reload and some of the critical processes are still coming up. The stop job of swss in the queue is cancelled due to other critical processes still coming up and trying to bring up swss. Hence, we get the error - "Job for swss.service cancelled" How did you do it? This PR enhanced the testcase to wait until all the critical processes are up after a config reload and then execute a stop job for swss. How did you verify/test it? Ran the testcase 15-20 times to see if it fails.
… up during swss stop job
Type of change
Back port request
Approach
What is the motivation for this PR?
The testcase test_reload_configuration_checks fails sometimes when swss is stopped after a config reload and some of the critical processes are still coming up. The stop job of swss in the queue is cancelled due to other critical processes still coming up and trying to bring up swss. Hence, we get the error - "Job for swss.service cancelled"
How did you do it?
This PR enhanced the testcase to wait until all the critical processes are up after a config reload and then execute a stop job for swss.
How did you verify/test it?
Ran the testcase 15-20 times to see if it fails.
Any platform specific information?
NA
Supported testbed topology if it's a new test case?
NA