action #110071
closed[sle][security][CC][backlog]Investigate: The system will become no-response when running './dfuzzer -v -n org.freedesktop.login1'
Added by Xiaojing_liu about 2 years ago. Updated over 1 year ago.
100%
Description
Story¶
When integrating test case 'DBus fuzzer' into openQA, testing 'org.freedesktop.login1' by running './dfuzzer -v -n org.freedesktop.login1', the system will stack in somewhere and needs to be rebooted.
We need to investigate which method causes this and if skip this testing make sense.
Updated by Xiaojing_liu about 2 years ago
- Copied from action #109978: [sle][security][sle15sp4][CC]automation: Integrate test case 'DBus fuzzer' into openQA added
Updated by openqa_review almost 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_atsec
https://openqa.suse.de/tests/8677108
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 Xiaojing_liu almost 2 years ago
- Subject changed from [sle][security][sle15sp4][CC]Investigate: The system will become no-response when running './dfuzzer -v -n org.freedesktop.login1' to [sle][security][CC][backlog]Investigate: The system will become no-response when running './dfuzzer -v -n org.freedesktop.login1'
- Target version set to future
Updated by openqa_review almost 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_atsec
https://openqa.suse.de/tests/8751964
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 openqa_review almost 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_atsec
https://openqa.suse.de/tests/8897594
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 56 days if nothing changes in this ticket.
Updated by rfan1 almost 2 years ago
- Assignee changed from Xiaojing_liu to pstivanin
Updated by pstivanin almost 2 years ago
- Category changed from Spike/Research to Bugs in existing tests
- Status changed from New to In Progress
- Target version deleted (
future) - Start date deleted (
2022-04-11) - Estimated time changed from 8.00 h to 16.00 h
Updated by pstivanin almost 2 years ago
The method that causes the test to get stuck is 'FlushDevices'.
A workaround could be adding "FlushDevices destructive" to dfuzzer.conf.
Updated by pstivanin almost 2 years ago
- % Done changed from 60 to 100
Updated by pstivanin over 1 year ago
- Status changed from In Progress to Resolved
job has also been added to 15-sp4 secmaint.
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_atsec
https://openqa.suse.de/tests/8897594
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.