Project

General

Profile

Actions
Copy link

action #98853

closed

[sle][security][sle15sp4] test fails in settings_disable_enable_apparmor: needle with tag(s) 'root-console-x11' matched

Added by llzhao over 2 years ago. Updated about 2 years ago.

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

100%

Estimated time:
4.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP4-Online-aarch64-yast2_apparmor@aarch64 fails in
settings_disable_enable_apparmor

Test suite description

Maintainer: llzhao@suse.com
Test "yast2 apparmor" with an existing disk image.

Reproducible

Fails since (at least) Build 31.2

Expected result

Last good: 29.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by openqa_review over 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: yast2_apparmor
https://openqa.suse.de/tests/7261505

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
Actions
Copy link
 #2

Updated by openqa_review over 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: yast2_apparmor
https://openqa.suse.de/tests/7429502

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
Actions
Copy link
 #3

Updated by openqa_review over 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: yast2_apparmor
https://openqa.suse.de/tests/7555973

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

Updated by llzhao over 2 years ago

  • Priority changed from Normal to Low

Filed a bug to track: bsc#1192197 - [Build 55.1] openQA test fails in settings_disable_enable_apparmor: "# systemctl status apparmor" outputs lots of warnings

Test case can use this bug to mark test case as a "softfailure".

Actions
Copy link
 #5

Updated by openqa_review over 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: yast2_apparmor
https://openqa.suse.de/tests/7715572

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
Actions
Copy link
 #6

Updated by openqa_review over 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: yast2_apparmor
https://openqa.suse.de/tests/7804852

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
Actions
Copy link
 #7

Updated by openqa_review over 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: yast2_apparmor
https://openqa.suse.de/tests/7897897

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
Actions
Copy link
 #8

Updated by llzhao over 2 years ago

It is random and seems only found on aarch64 arch.

Actions
Copy link
 #9

Updated by llzhao over 2 years ago

  • % Done changed from 0 to 90
Actions
Copy link
 #10

Updated by llzhao over 2 years ago

  • Status changed from New to Feedback

There are still random fails.

Actions
Copy link
 #11

Updated by openqa_review about 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: yast2_apparmor
https://openqa.suse.de/tests/8158462

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
Actions
Copy link
 #12

Updated by llzhao about 2 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 90 to 100

It is a random failure but not very frequent so resolved it ATM.

Actions
Copy link

Also available in: Atom PDF