Project

General

Profile

Actions

action #155413

closed

Ensure apparmor is enforced in openQA-in-openQA tests size:M

Added by okurz 10 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Motivation

In multiple occurrences openQA failed to start up or operate successfully on openqa.opensuse.org due to change of functionality without having according apparmor adaptions prepared. We should have automatic tests that ensure that apparmor profiles are enforced and fail if not covered properly.

Acceptance criteria

  • AC1: At least one openQA-in-openQA test scenario ensures that openQA jobs can still be executed with apparmor profiles enforced

Suggestions

  • Do we have any documentation regarding apparmor? If not then extend our documentation to cover that, should be simple
  • Enable apparmor in openQA-in-openQA tests and just run tests, e.g. like "zypper -n in apparmor && systemctl enable --now apparmor"
  • Ensure to cover both webUI and worker part though can be on the same host
  • Do we need reboot? Probably not, we don't have any kernel parameters or anything on o3

Related issues 3 (0 open3 closed)

Related to openQA Project (public) - action #165408: Unreviewed issue (Group 24 openQA) test-running in openQA failing with error detecting default remote branch size:SResolvedybonatakis2024-09-06

Actions
Related to openQA Project (public) - action #165692: [openQA-in-openQA] test does not fail if state is done but incomplete auto_review:"no candidate needle.*openqa-dashboard.*matched" size:S Resolvedjbaier_cz2024-08-22

Actions
Copied from openQA Project (public) - action #153427: Improve updating cached assets size:MResolvedmkittler2024-01-05

Actions
Actions

Also available in: Atom PDF