action #26038
closed
coordination #25850: [sle][functional][sle15][epic] new system roles
[sle][functional][sle15] new system role - "minimal"
Added by okurz over 6 years ago.
Updated over 6 years ago.
Description
acceptance criteria¶
- AC1: An installation is conducted with registration and system role "minimal" selected
tasks¶
- review existing use of the test variable "SYSTEM_ROLE" (0.2-2h) -> DONE: so far only used for kvm, xen and in caasp for different roles
- review the existing test suites "textmode" and "minimalx" if it should use that new system role but in a backward compatible way to still support older versions, e.g. maintenance tests and SLE 12 SP4 (1-4h) -> DONE: role "minimal" does not include a lot of packages so probably it does not make sense to test more stuff. We should go with what corresponds to "INSTALLONLY"
- add a scenario using that role, e.g. change the existing installation test suite "textmode" to add a SLE15 specific system role setting which will not impact older versions? (1-4h) -> based on either sle15 && no_registration or if explicitly selected SYSTEM_ROLE=minimal we should implicitly set DESKTOP=textmode and do what INSTALLONLY=1 does in the test plan
- adapt the test modules that can be executed based on that system role (2-8h)
- Description updated (diff)
- Status changed from New to In Progress
- Due date set to 2017-10-25
PO @sebchlad I think this is a good candidate to add to the current sprint considering delayed perl training, higher capacity, etc., agreed?
- Description updated (diff)
- Copied to action #26042: [sle][functional][sle15] new system role - "textmode" added
- Copied to deleted (action #26042: [sle][functional][sle15] new system role - "textmode")
- Blocks action #25866: [sle][functional][easy] test fails in system_role - needle fails due to renamed default system added
- Description updated (diff)
all merged. Now tests can be triggered with an explicit system role. I did that now in one case based on the skip_registration test suite: https://openqa.suse.de/tests/1221255 as soft-failed so good enough for the case of skip_registration where we don't have any other role available. I will update main.pm to set this system role by default.
Additionally we should have one scenario that starts with a registered installation but selects role "minimal" explicitly, called "minimal+role_minimal"
Added "minimal+role_minimal" test suite with only one variable, "SYSTEM_ROLE=minimal". The "INSTALLONLY=1" should be set implicitly within products/sle/main.pm as we can not execute the normal test modules.
- Status changed from In Progress to Resolved
Added the scenarios "minimal+role_minimal" to "Functional" for aarch64, ppc64le, s390x-kvm, 64bit
- Status changed from Resolved to Feedback
Not sure if this is the right ticket to reopen but the recent build shows two more tests with "minimal" in the name that are not prepared for the new system role selection:
- Status changed from Feedback to Resolved
are you sure you are commenting on the right ticket? the jobs in #26038#note-12 are both failing for different reasons, the first is not related to the system role "minimal" but is a "minimal" pattern selection, as we always had since sle12. The second is a test skipping over the addon screen. Either yast failed to show it or "next" was pressed twice. your last comment #26038#note-13 more likely relates to #23650
Also available in: Atom
PDF