coordination #9466
closed
coordination #15108: [sle][functional][u][epic] Modules (Installation + migration)
[sle][functional][epic][medium][u]Modules - Containers: Test the SLE module for containers
Added by RBrownSUSE over 8 years ago.
Updated over 3 years ago.
Description
Motivation¶
We require proper modules testing
This should be done as part of Validation if possible
Acceptance criteria¶
- AC1: The existing test module "console/docker" is passed (or blocked and labeled with proper valid bug) for SLE15
- AC2: Same as above for SLE12SP4
Tasks¶
- Make sure the docker package is available to an installation in SLE15, i.e. the system has to be registered and the container module activated -> see #9466#note-13
- Apply the equivalent way for SLE12 where we commonly call the testsuite extra_tests_in_textmode based on an unregistered system
- Verify for both versions of SLE
- Checklist item changed from to [ ] SLE
- Target version deleted (
156)
- Parent task set to #15108
- Related to action #17042: [sles][functional][modules] Modules installation added
- Related to deleted (action #17042: [sles][functional][modules] Modules installation)
gnome-asmm-proxySCC test suite was added to SLES Function job group.
First step is to have ASMM installed onppc64le, s390x(zkvm) and x86_64.
Second step is to test the steps in the description of the task.
- Subject changed from Modules - Containers to [sle]Modules - Containers
- Target version set to Milestone 12
- Subject changed from [sle]Modules - Containers to [sle][functional]Modules - Containers
- Assignee set to maritawerner
Start date: 11/11/2015
Interesting.
@maritawerner: am I correct that we have a requirement to do some testing like that for SLE15? Or I am wrong?
Same for SLE15 as for SLE12. The containers module is mentioned in the PRD and should be tested by QA SLE accordingly. IMHO the original ticket description still applies, e.g. reg. the mandatory steps. I assume the same applies for SLE12SP4 as well.
The Testing Document says that we do installation tests. So, yes that still applies for SLE15 and SLE 12 SP4. Perform some basic tests is optional.
- Assignee deleted (
maritawerner)
- Subject changed from [sle][functional]Modules - Containers to [sle][functional][medium]Modules - Containers: Test the SLE module for containers
- Description updated (diff)
- Due date set to 2018-04-10
- Status changed from New to Workable
- Target version changed from Milestone 12 to Milestone 15
TW works -> https://openqa.opensuse.org/tests/588945#step/docker/72
but for SLE we need to enable the container module in when we want to install docker -> see how #28854 resolved that with the use of
# preparation for crash test
if (is_sle && sle_version_at_least('15')) {
add_suseconnect_product('sle-module-desktop-applications');
add_suseconnect_product('sle-module-development-tools');
}
- Subject changed from [sle][functional][medium]Modules - Containers: Test the SLE module for containers to [sle][functional][epic][medium][u]Modules - Containers: Test the SLE module for containers
- Status changed from Workable to In Progress
- Assignee set to oorlov
- Assignee deleted (
oorlov)
- Status changed from In Progress to Workable
please set the ticket back to workable if unassigning
we don't want to have tickets in "in progress" without assignee
- Status changed from Workable to Blocked
- Assignee set to okurz
- Due date changed from 2018-04-10 to 2018-04-22
due to changes in a related task
- Due date changed from 2018-04-22 to 2018-03-13
due to changes in a related task
- Status changed from Blocked to Resolved
- Start date set to 2015-06-12
due to changes in a related task
- Related to action #33184: [sle][functional][12sp4][u]test fails in docker - needs to add container module / how do we want to execute extra tests that rely on a registered image for SLE12? added
- Tracker changed from action to coordination
- Difficulty deleted (
medium)
Also available in: Atom
PDF