action #168682
Updated by ph03nix 25 days ago
In Tumbleweed currently the container iso test runs only run with AppArmor. However SELinux enabled by default, see context: https://bugzilla.suse.com/show_bug.cgi?id=1230118 showed us that also see: https://progress.opensuse.org/issues/166613 i think the we need to also run container-selinux installed for the container test runs with SELinux enabled. case to work This ticket is about establishing ## Observation openQA test scenarios for `podman` and for `docker` using SELinux and AppArmor, where AppArmor should be used right now for the test runs. in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_bats_testsuite@64bit fails in [runc-root_tap](https://openqa.opensuse.org/tests/4548777/modules/runc-root_tap/steps/213) The ## Test suite description Maintainer: qe-c@suse.de https://confluence.suse.com/display/qasle/podman+upstream+tests ## Reproducible Fails since (at least) Build [20241008](https://openqa.opensuse.org/tests/4545681) ## Expected result should be dedicated scenarios for each security framework, e.g. `containers_host_podman_SELinux` and `containers_host_podman_AppArmor`. Last good: (unknown) (or more recent) ## Acceptance criteria Further details * **AC1** Tumbleweed test runs for the `podman` engine are being tested with SELinux and with AppArmor Always latest result in separate test scenarios this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=containers_host_bats_testsuite&version=Tumbleweed) * **AC2** Tumbleweed test runs for the `docker` engine are being tested with SELinux and with AppArmor in separate test scenarios