action #137585
closed[ppc64le][kvm]test fails in scc_deregistration, seems 'wait_serial' function fails to catch up the expected return code if some other messages show up in serial console at the same time
0%
Description
Motivation¶
Currently the test module scc_deregistration is run in root-console, however in recent tests, I can find some issues that even the command is executed successfully, wait_serial function fails to catch up the return code if some other messages printing in serial console at the same time.
Then it may lead to test failure.
Take below test as an example:
openQA test in scenario sle-15-SP6-Continuous-Migration-SLE15-SPx-ppc64le-offline_sle12sp5_sles15sp4_sles15sp_latest_scc_all_full_ppc64le_ph0@ppc64le fails in
scc_deregistration
even we can see the return code 2vdJ6-0- finally, seems openQA doesn't catch up it.
[ 1087.204923] systemd[1]: Reloading.
[ 1108.129961] systemd[1]: /usr/lib/systemd/system/rpc-statd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly.
2vdJ6-0-
Acceptance criteria¶
AC1 Maybe we can switch the test to run in serial_terminal rather than root-console
AC2 May be tools team can take a look at this issue and provide some good fixes
Further details¶
Always latest result in this scenario: latest
Updated by openqa_review 7 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: offline_sle12sp5_sles15sp4_sles15sp_latest_scc_all_full_
https://openqa.suse.de/tests/12552760#step/scc_deregistration/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by tinawang123 6 months ago
- Status changed from Workable to In Progress
- Assignee set to tinawang123
Updated by tinawang123 6 months ago
I checked the code, I think use 'witch the test to run in serial_terminal rather than root-console' is not very good
The root problem is because command 'systemctl mask packagekit; systemctl stop packagekit; while pgrep packagekitd; do sleep 1; done' timed out
This packagegit will be used at several test modules.
So updated scc_deregistration test module is not good enough to fix this problem
I try to update sub quit_packagekit function.
WDYT @rfan1
Updated by rfan1 6 months ago
tinawang123 wrote in #note-4:
I checked the code, I think use 'witch the test to run in serial_terminal rather than root-console' is not very good
The root problem is because command 'systemctl mask packagekit; systemctl stop packagekit; while pgrep packagekitd; do sleep 1; done' timed out
This packagegit will be used at several test modules.
So updated scc_deregistration test module is not good enough to fix this problem
I try to update sub quit_packagekit function.
WDYT @rfan1
Good question, I can see the loop command timeout issue as well. but most of the failed cases are caused
by un-expected serial output rather than timeout.
So, we can also enhance the logic for quit-packagegit at the same time.
Anyway, if we switch the test to use serial terminal, we may need to do enough VRs :)