action #106822
closed
New security settings for AppArmor/SELinux in SLE 15 SP4
Added by suntorytimed about 2 years ago.
Updated about 2 years ago.
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-Y-Staging-x86_64-minimal+base@64bit fails in
start_install
Test suite description¶
Maintainers: QE Core
Select a minimal textmode installation by starting with the default and unselecting all patterns except for "base" and "minimal". Not to be confused with the new system role "minimal" introduced with SLE15.
Reproducible¶
Fails since (at least) Build Y.75.3
Expected result¶
Last good: Y.74.1 (or more recent)
Further details¶
We have changed the way on how to setup a system with and without AppArmor/SELinux by introducing a configuration option in the installation summary (in Security -> Major Linux Security Module). If you want to not install AppArmor you now need to adjust this in the Security settings and unselecting the pattern shouldn't be required after that anymore. If you unselect the pattern though, you also have to deactivate the security setting in the installation overview.
Always latest result in this scenario: latest
- Tags set to qe-yast-refinement
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
- Assignee set to JERiveraMoya
- Target version set to Current
- Tags deleted (
qe-yast-refinement)
- Status changed from New to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to Closed
- Status changed from Closed to Workable
When AppArmor is active, it should also install AppArmor. In that case unselecting AppArmor from the package installation is not a valid use case and will result in the error shown in the UI. The customer has now the chance to either add AppArmor back to the package proposal or deactivate AppArmor in the Security settings.
- Status changed from Workable to In Progress
- Assignee changed from JERiveraMoya to szarate
Assigning to Santi as agreed with him.
For the future we are working together in bring AutoYaST for create_hdd_ test suites, so we don't have to do double work.
ybonatakis wrote:
@santi are you ok to close this. i have restarted only one job[0] and start_install
passes but i dont think it is destructed any further
[0] https://openqa.suse.de/tests/8301124#next_previous
All looks good, no further changes needed (other than reneedling for s390)
- Status changed from In Progress to Feedback
- Status changed from Feedback to Closed
Also available in: Atom
PDF