Project

General

Profile

action #116872

[security] test fails sporadically in manually_add_profile

Added by punkioudi 3 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-09-20
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

This tests fails sporadically here:

# Scan systemlog
send_key "alt-s";
assert_screen("AppArmor-Scan-system-log");

It seems that s is not being sent in all the cases properly, so it would be helpful to add a retry here.

Acceptance criteria

  1. Investigate the sporadic failure and check if a workaround can be applied
  2. Run multiple verification runs to make sure that this failure doesn't happen any more

Observation

openQA test in scenario sle-15-SP4-Server-DVD-Updates-x86_64-yast2_apparmor@64bit fails in
manually_add_profile

Test suite description

Testsuite maintained at https://gitlab.suse.de/qe-security/osd-sle15-security.

Reproducible

Fails since (at least) Build 20220919-2 (current job)

Expected result

Last good: 20220919-1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #116764: [security] test fails in manually_add_profileResolved2022-09-19

History

#1 Updated by punkioudi 2 months ago

  • Priority changed from Normal to Urgent

#2 Updated by pstivanin 2 months ago

  • Assignee set to pstivanin

#3 Updated by pstivanin 2 months ago

The test has been really shaky. Looking at its history, it doesn't seem to fail always on the same point though.
This seems to be some slowness related issue. Looking into it.

#5 Updated by pstivanin 2 months ago

  • Related to action #116764: [security] test fails in manually_add_profile added

#6 Updated by pstivanin 2 months ago

  • % Done changed from 0 to 50

#7 Updated by pstivanin 2 months ago

I'm testing some changes. So far the run has been stable.

#8 Updated by pstivanin 2 months ago

  • % Done changed from 50 to 80

Test is running fine so far.

#9 Updated by pstivanin 2 months ago

  • Priority changed from Urgent to High

Lowering prio since the test has been stable.

#10 Updated by pstivanin 2 months ago

  • Status changed from New to In Progress

#11 Updated by pstivanin 2 months ago

The test failed again. What's weird is that the test is very shaky only on 15-SP4, on 15-SP3 it runs stable.

#12 Updated by pstivanin 2 months ago

  • % Done changed from 80 to 50

The same test in the devel space (https://openqa.suse.de/tests/9619790) has been running great so far. Could be some load related issue in prod?
I think the best solution here would be to move from the QT to the Ncurses ui.

#13 Updated by pstivanin 2 months ago

  • % Done changed from 50 to 90

I've rewritten the test. I'll let it run a couple of days in the devel project. After that, we'll move it to secmaint.

#15 Updated by pstivanin 2 months ago

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

Also available in: Atom PDF