Project

General

Profile

action #48707

Only parse logs in detect_yast2_failures instead of conducting full installation for online medium

Added by riafarov over 2 years ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Target version:
Start date:
2019-03-05
Due date:
% Done:

0%

Estimated time:

Description

Motivation

We use RAID0 as a base test and then parse logs. Instead of repeating same installation steps twice, we should simply publish set of logs for RAID0 job and only parse them to detect if there are any new errors.

We can either chain jobs, boot into installed system and parse logs there, or publish logs as an asset and parse them either directly on the worker (might not work), or boot into any image (even support server) and parse logs there using same tools as before.

NOTE: we cannot optimize this scenario for the Full medium, as we do not execute RAID tests there

Acceptance criteria

  1. For online medium logs are parsed without conduction of the full installation

History

#1 Updated by okurz over 2 years ago

hm, is it worth the effort? Is it technically feasible in the scenarios where we run it, e.g. "bare-metal" or s390x z/VM? If it's about saving reviewer times then I suggest to schedule the detect_yast2_failures simply after RAID0 with START_AFTER_TEST

#2 Updated by riafarov about 2 years ago

  • Target version changed from Milestone 26 to future

#3 Updated by riafarov 9 months ago

  • Project changed from openQA Tests to qe-yast
  • Subject changed from [functional][y] Only parse logs in detect_yast2_failures instead of conducting full installation to Only parse logs in detect_yast2_failures instead of conducting full installation
  • Category deleted (Enhancement to existing tests)

#4 Updated by riafarov 6 months ago

  • Subject changed from Only parse logs in detect_yast2_failures instead of conducting full installation to Only parse logs in detect_yast2_failures instead of conducting full installation for online medium

#5 Updated by riafarov 6 months ago

  • Description updated (diff)
  • Status changed from New to Workable

#6 Updated by syrianidou_sofia 6 months ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia

#8 Updated by syrianidou_sofia 6 months ago

  • Status changed from Feedback to Resolved

OSD runs ok

Also available in: Atom PDF