Project

General

Profile

Actions
Copy link

action #90392

closed

[qe-core][qem][sporadic] test fails in yast2_apparmor

Added by dzedro about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
dzedro
Category:
Bugs in existing tests
Target version:
QA - QE-Core: Ready
Start date:
2021-03-22
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-Server-DVD-Updates-x86_64-mau-extratests-yast2ui-textmode@64bit fails in
yast2_apparmor

Test suite description

Run console tests against aggregated test repo

Reproducible

Fails since (at least) Build 20210322-1

Expected result

Last good: 20210321-1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by mgrifalconi about 3 years ago

  • Subject changed from [qe-core][qem] test fails in yast2_apparmor to [qe-core][qem][sporadic] test fails in yast2_apparmor auto_review:"no candidate needle with tag(s) 'yast2_apparmor_profile_mode_configuration_toggle'"
Actions
Copy link
 #2

Updated by tjyrinki_suse about 3 years ago

  • Status changed from New to Workable
Actions
Copy link
 #3

Updated by openqa_review almost 3 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: mau-extratests-yast2ui-textmode
https://openqa.suse.de/tests/6036093

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #4

Updated by dzedro almost 3 years ago

  • Subject changed from [qe-core][qem][sporadic] test fails in yast2_apparmor auto_review:"no candidate needle with tag(s) 'yast2_apparmor_profile_mode_configuration_toggle'" to [qe-core][qem][sporadic] test fails in yast2_apparmor
  • Status changed from Workable to Blocked
  • % Done changed from 0 to 90

I have prepared change to fix the occasional failures, but there is also workaround for bug. [1]
I will probably open PR when update [1] is released.

[1] https://bugzilla.suse.com/show_bug.cgi?id=1186330
[2] https://smelt.suse.de/incident/19871/

Actions
Copy link
 #5

Updated by dzedro almost 3 years ago

  • Status changed from Blocked to In Progress
Actions
Copy link
 #6

Updated by dzedro almost 3 years ago

And it happened again https://openqa.suse.de/tests/6397023
When I watch the video the profile changes from enforce -> complain -> enforce
Change mode (alt-c) is pressed once, but before that is alt-c pressed to enter configuration
This can be pressed while the button is not active and I guess here is possibility
that somehow it enters the configuration and also toggles profile mode.
I made some changes, unfortunately still can't say it will solve occasional failures ...

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12867

Actions
Copy link
 #7

Updated by dzedro over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Didn't see apparmor failure quite some time.

Actions
Copy link
 #8

Updated by szarate over 2 years ago

  • Target version set to QE-Core: Ready
Actions
Copy link

Also available in: Atom PDF