Project

General

Profile

action #69088

coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues

coordination #19720: [epic] Simplify investigation of job failures

Present changes between packages on openQA worker machines in "investigation"

Added by okurz 11 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2020-07-17
Due date:
% Done:

0%

Estimated time:
Difficulty:
medium

Description

Motivation

See parent #19720

Acceptance criteria

  • AC1: Any changes in packages installed on worker machines between "last good" and "current" are available in "investigation" UI tab
  • AC2: The solution within openQA is agnostic to the operating system of the openQA worker, e.g. no hardcoded rpm -qa within openQA code

Suggestions

  • see #19720#note-14 and #19720#note-15 for preliminary evaluations
  • 1st step: Collect the data, e.g. if a hook is defined in worker config, call command on worker at end of job, e.g. with suggestion rpm -qa for openSUSE/SLE machines, save data in text file, upload text file (same as other log files)
  • 2nd step: Show the diff in "investigate" route if file(s) exist, same as we do for vars.json

Further details

  • It might be that overall this is producing too much data to handle on worker side

History

#1 Updated by okurz 10 months ago

  • Target version changed from Ready to future

#2 Updated by cdywan 10 months ago

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

I reckon this is PR is meant to fix this ticket:

https://github.com/os-autoinst/openQA/pull/3303

#3 Updated by okurz 9 months ago

https://github.com/os-autoinst/openQA/pull/3303 merged now. you could activate the according config within the o3 infrastructure now or osd first, your choice :)

#4 Updated by cdywan 9 months ago

Discussing with ilausuch what's missing here:

  • Are the code changes complete?
  • Should PACKAGES_CMD be set in the worker.ini to enable the feature?
  • Can we have a post somewhere explaining how this works? Demonstrating configuration as well as results.

#5 Updated by ilausuch 9 months ago

Added a PR to activate the feature in salt configuration
https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/265

#6 Updated by ilausuch 9 months ago

  • Status changed from In Progress to Feedback

#7 Updated by okurz 9 months ago

  • Due date set to 2020-10-06
  • Target version changed from future to Ready

cdywan wrote:

  • Should PACKAGES_CMD be set in the worker.ini to enable the feature?
  • Can we have a post somewhere explaining how this works? Demonstrating configuration as well as results.

You are right. IMHO PACKAGES_CMD should be within etc/openqa/workers.ini as an example.

I am adding this ticket back to our backlog as we work on it and I think we should better track it in "Ready". Also setting a due date.

I recommend to do three things now:

  • Enable in o3 workers
  • Enable in osd workers
  • Add as example in PACKAGES_CMD

#9 Updated by ilausuch 8 months ago

  • Assignee deleted (ilausuch)

I made the changes for the documentation. About activate in production, I will be some days off, I release this ticket to de completed as soon as possible

#10 Updated by okurz 8 months ago

  • Due date deleted (2020-10-06)
  • Status changed from Feedback to Workable

alright, setting back to Low and removing due date then.

#11 Updated by okurz 8 months ago

  • Status changed from Workable to Resolved
  • Assignee set to ilausuch

I am stumbling over this ticket again. As the main feature is properly done with good test coverage I would regard this as "Resolved" as I don't see us having the capacity to enable and test in o3+osd infrastructure and also not urgent. Let's see what the next opportunity will be where we would benefit from that :)

Also available in: Atom PDF