Project

General

Profile

Actions

action #70132

closed

[functional][u] test fails in machinery - detect missing capability in zypper and report the corrresponding error

Added by szarate over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Refactor/Code Improvements
Target version:
SUSE QA - Milestone 30
Start date:
2020-08-17
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Description

openQA test in scenario sle-15-SP3-Online-x86_64-extra_tests_textmode_phub@64bit fails in
machinery

When looking at the zypper log, one can clearly see the following trace, which means that a package, pattern or capability was not found, similar to #70129 to save time during review, knowing which of those packages are missing from the test results instead of looking at logs, would save some minutes.

Suggestions

Implement a regex search for every occurence of: SolverRequester.cc(install):325 .* cap:machinery not found and report them in a single record_info box that is triggered when zypper's return code is 104 which resolves to ZYPPER_EXIT_INF_CAP_NOT_FOUND, also see #70129

2020-08-14 05:32:41 <1> susetest(2351) [zypper] basecommand.cc(defaultSystemSetup):199 -------------- Calling SAT Solver to establish the PPP status -------------------
2020-08-14 05:32:41 <1> susetest(2351) [zypper++] PackageArgs.cc(preprocess):84 args received: machinery 
2020-08-14 05:32:41 <1> susetest(2351) [zypper++] PackageArgs.cc(preprocess):88 args compiled: machinery 
2020-08-14 05:32:41 <1> susetest(2351) [zypper] PackageArgs.cc(argsToCaps):223 got wanted 'machinery'; repo ''
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 query: kinds: package 
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 repos: ALL
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 version: ANY 
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 status: ALL
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 string match flags: GLOB|SKIP_KIND
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 strings: 
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 attributes: 
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 * solvable:name: machinery 
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 predicated: 
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 last attribute matcher compiled: 
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 not yet compiled
2020-08-14 05:32:41 <1> susetest(2351) [zypper:req++] SolverRequester.cc(pkg_spec_to_poolquery):76 
2020-08-14 05:32:41 <2> susetest(2351) [zypper:req] SolverRequester.cc(install):325 machinery cap:machinery not found
2020-08-14 05:32:41 <1> susetest(2351) [zypper++] PackageArgs.cc(preprocess):84 args received: 
2020-08-14 05:32:41 <1> susetest(2351) [zypper++] PackageArgs.cc(preprocess):88 args compiled: 
2020-08-14 05:32:41 <2> susetest(2351) [zypper] Zypper.h(setExitCode):164 setExitCode 104
2020-08-14 05:32:41 <5> susetest(2351) [zypp] Exception.cc(log):166 installremove.cc(handleFeedback):41 THROW:    name or capability not found
2020-08-14 05:32:41 <5> susetest(2351) [zypp] Exception.cc(log):166 basecommand.cc(run):274 CAUGHT:   name or capability not found
2020-08-14 05:32:41 <2> susetest(2351) [zypper] basecommand.cc(run):275 Caught exit request: exitCode 104
2020-08-14 05:32:41 <2> susetest(2351) [zypper] Zypper.h(setExitCode):164 setExitCode 104
2020-08-14 05:32:41 <1> susetest(2351) [zypper] Zypper.cc(doCommand):685 Done 
2020-08-14 05:32:41 <1> susetest(2351) [zypper] Zypper.cc(cleanup):737 START

Suggestions

Reproducible

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

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 2 (0 open2 closed)

Related to openQA Tests - action #70129: [functional][u] test fails in pam - Detect invalid repositories and report them as suchResolveddheidler2020-08-17

Actions
Related to openQA Tests - action #70528: [functional][u] test fails in machinery - detect "Valid metadata not found at specified URL" and record the errorResolveddheidler2020-08-26

Actions
Actions #1

Updated by szarate over 3 years ago

  • Category changed from Bugs in existing tests to Refactor/Code Improvements
Actions #2

Updated by SLindoMansilla over 3 years ago

  • Status changed from New to Workable
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h
Actions #3

Updated by dheidler over 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to dheidler
Actions #4

Updated by dheidler over 3 years ago

  • Status changed from In Progress to Feedback
Actions #5

Updated by szarate over 3 years ago

  • Related to action #70129: [functional][u] test fails in pam - Detect invalid repositories and report them as such added
Actions #6

Updated by szarate over 3 years ago

  • Related to action #70528: [functional][u] test fails in machinery - detect "Valid metadata not found at specified URL" and record the error added
Actions #7

Updated by dheidler over 3 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF