action #31453
closed[sle][functional][easy] test fails in docker - Add containers module
0%
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-x86_64-extra_tests_in_textmode@svirt-xen-pv fails in
docker
Container module is already available: https://fate.suse.com/323788
And enabled on allmodules tests:
Acceptance criteria¶
- AC1: The test suite extra_tests_in_textmode has the container module enabled.
- AC2: The test module docker is able to install the docker package.
Reproducible¶
Fails since (at least) Build 346.1
Expected result¶
Leap 15.0. I do not think this was ever working for SLE as docker was added by panos (shortname too hard for me to remember) and never working for SLE validation.
Suggestions¶
Further details¶
Always latest result in this scenario: latest
Updated by SLindoMansilla about 6 years ago
- Subject changed from [sle][functional] test fails in docker - Add containers module to [sle][functional][easy] test fails in docker - Add containers module
- Description updated (diff)
I think that changing the qcow2 image is going to make us loosing coverage of standard sle+gnome installation.
I would set a milestone before docker and enable the container module in the same docker module to test docker, and then, after all container tests, rollback to milestone, so we don't pollute following tests.
Or putting container tests at the end of the list.
Updated by okurz about 6 years ago
SLindoMansilla wrote:
I would set a milestone before docker and enable the container module in the same docker module to test docker, and then, after all container tests, rollback to milestone, so we don't pollute following tests.
I would not rely on the qcow snapshot rollback feature in any tests except for failure recovery as we do not have that available on all backends. Moving the test modules is an option, another is to just cleanup in the post_run_hook which I think we already do in some other tests (@riafarov)
Updated by okurz about 6 years ago
- Description updated (diff)
- Due date set to 2018-03-27
- Status changed from New to In Progress
- Assignee set to okurz
- Priority changed from Normal to High
@jrivera What mnowak mentioned in https://bugzilla.suse.com/show_bug.cgi?id=1064683#c4 is not that we need to use a different qcow image but make sure the container module is enabled in the corresponding test. We have already done this in other cases, e.g. development-tools module, etc.
Trying this with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4459
Updated by okurz about 6 years ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4471 as a replacement
Updated by okurz about 6 years ago
https://openqa.suse.de/tests/1495203 should show if that worked