Project

General

Profile

Actions

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 almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
16.00 h
Difficulty:

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.


Related issues 1 (0 open1 closed)

Copied from openQA Tests - action #109978: [sle][security][sle15sp4][CC]automation: Integrate test case 'DBus fuzzer' into openQAResolvedXiaojing_liu2022-04-11

Actions
Actions #1

Updated by Xiaojing_liu almost 2 years ago

  • Copied from action #109978: [sle][security][sle15sp4][CC]automation: Integrate test case 'DBus fuzzer' into openQA added
Actions #2

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #3

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
Actions #4

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #5

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #6

Updated by rfan1 over 1 year ago

  • Assignee changed from Xiaojing_liu to pstivanin
Actions #7

Updated by pstivanin over 1 year ago

  • Assignee deleted (pstivanin)
Actions #8

Updated by pstivanin over 1 year 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
Actions #9

Updated by pstivanin over 1 year ago

  • Assignee set to pstivanin
Actions #10

Updated by pstivanin over 1 year ago

The method that causes the test to get stuck is 'FlushDevices'.
A workaround could be adding "FlushDevices destructive" to dfuzzer.conf.

Actions #11

Updated by pstivanin over 1 year ago

  • % Done changed from 0 to 40
Actions #12

Updated by pstivanin over 1 year ago

  • % Done changed from 40 to 60
Actions #14

Updated by pstivanin over 1 year ago

  • Status changed from In Progress to Resolved

job has also been added to 15-sp4 secmaint.

Actions #15

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions

Also available in: Atom PDF