Project

General

Profile

Actions
Copy link

action #48707

closed

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

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

Status:
Resolved
Priority:
Normal
Assignee:
syrianidou_sofia
Target version:
QA (public, currently private due to #173521) - future
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
Actions
Copy link
 #1

Updated by okurz over 5 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

Actions
Copy link
 #2

Updated by riafarov over 5 years ago

  • Target version changed from Milestone 26 to future
Actions
Copy link
 #3

Updated by riafarov about 4 years ago

  • Project changed from openQA Tests (public) to qe-yam
  • 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)
Actions
Copy link
 #4

Updated by riafarov almost 4 years 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
Actions
Copy link
 #5

Updated by riafarov almost 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #6

Updated by syrianidou_sofia almost 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia
Actions
Copy link
 #8

Updated by syrianidou_sofia almost 4 years ago

  • Status changed from Feedback to Resolved

OSD runs ok

Actions
Copy link

Also available in: Atom PDF