action #31453: [sle][functional][easy] test fails in docker - Add containers module - openQA Tests - openSUSE Project Management Tool

Custom queries

All open Feature tests
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QAM
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
SLE15 Migration Open Tickets
SLE15 SP1 Migration Open Tickets
SLE15SP3 Migration open ticket
SLE15SP3 Security open ticket
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #31453

closed

[sle][functional][easy] test fails in docker - Add containers module

Added by JERiveraMoya about 6 years ago. Updated about 6 years ago.

Status:

Resolved

Priority:

High

Assignee:

okurz

Category:

Bugs in existing tests

Target version:

openQA Project - Milestone 15

Start date:

2018-02-07

Due date:

2018-03-27

% Done:

Estimated time:

Difficulty:

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:

allmodules+allpatterns
gnome+proxy_SCC+allmodules

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

History
Notes
Property changes

Actions

Copy link

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.

Actions

Copy link

Updated by okurz about 6 years ago

Target version set to Milestone 15

Actions

Copy link

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)

Actions

Copy link

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

Actions

Copy link