action #53969: [sle][y][functional][arm][sporadic] test fails in yast2_clone_system - cloning takes more time than expected - 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 #53969

closed

[sle][y][functional][arm][sporadic] test fails in yast2_clone_system - cloning takes more time than expected

Added by mloviska almost 5 years ago. Updated over 4 years ago.

Status:

Resolved

Priority:

High

Assignee:

oorlov

Category:

Bugs in existing tests

Target version:

SUSE QA - Milestone 26

Start date:

2019-07-08

Due date:

2019-08-13

% Done:

Estimated time:

3.00 h

Difficulty:

Description

Observation¶

We should take a look if there is any reasonable explanation of the delay and bump the timeout to stabilize the test runs.

openQA test in scenario sle-12-SP5-Server-DVD-aarch64-clone_system@aarch64 fails in
yast2_clone_system

Test suite description¶

Maintainer: okurz@suse.de
Clone the system into an autoyast profile to be used by downstream jobs, e.g. to test reinstall from that profile.

Reproducible¶

Fails since (at least) Build 0216 (current job)

Expected result¶

Last good: 0214 (or more recent)

Further details¶

Always latest result in this scenario: latest

History
Notes
Property changes

Actions

Copy link

Updated by riafarov almost 5 years ago

Due date set to 2019-08-13
Target version set to Milestone 26

We have already bumped the timeout, so worth having a closer look. To figure out the root cause.

Actions

Copy link

Updated by riafarov almost 5 years ago

Subject changed from [sle][y][functional][arm] test fails in yast2_clone_system - cloning takes more time than expected to [sle][y][functional][arm][sporadic] test fails in yast2_clone_system - cloning takes more time than expected
Description updated (diff)
Status changed from New to Workable
Estimated time set to 3.00 h

Actions

Copy link

Updated by JRivrain almost 5 years ago

Assignee set to JRivrain

Actions

Copy link

Updated by JRivrain almost 5 years ago

This happened every 2 second run when this one was signaled, but has not happened since then in the past 6 builds. May as well not happen anymore.
In the failed runs, the serial-terminal.txt only contains this:

Welcome to SUSE Linux Enterprise Server 12 SP5 Beta2 (aarch64) - Kernel 4.12.14-100-default (hvc0).
susetest login:

and that's all. However I don't see why this would be related yet, in serial0.txt we have "yast2-clone_system-status-0" even in failed runs, it looks like the message was not intercepted.

Actions

Copy link

Updated by JRivrain almost 5 years ago

Status changed from Workable to In Progress

Actions

Copy link

Updated by JRivrain over 4 years ago

Status changed from In Progress to Blocked

Blocked by https://progress.opensuse.org/issues/54869: it cannot be cloned because parent job fails almost every time.

Actions

Copy link

Updated by JERiveraMoya over 4 years ago

Parent job seems to be running today: https://openqa.suse.de/tests/3203400. ~Let's see if succeeds creating the image.~ far from that unfortunately.

Actions

Copy link

Updated by JRivrain over 4 years ago

Assignee deleted (~~JRivrain~~)

De-assigning myself. could not work on it because of https://bugzilla.suse.com/show_bug.cgi?id=1058375 and https://progress.opensuse.org/issues/54869, and I am leaving for two weeks.

Actions

Copy link

Updated by okurz over 4 years ago

Status changed from Blocked to Workable
Priority changed from Normal to High

Both the mentioned tickets are certainly an impediment but should not be a blocker as the issue is reproducible at least within the OSD based tests, see the latest https://openqa.suse.de/tests/3205919#step/yast2_clone_system/4 . Ok for you to unset blocked status?

Actions

Copy link

#10