action #36127

[functional][u] test fails in zypper_up with no network - debugging and logging should be improved

Added by okurz almost 2 years ago. Updated over 1 year ago.

Status:NewStart date:14/05/2018
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Bugs in existing tests
Target version:QA - future
Difficulty:
Duration:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-NET-ppc64-minimalx@ppc64 fails in
zypper_up
with problems to connect to the network. This is also why e.g. zypper.log can not be uploaded (no network).

Reproducible

Fails since (at least) Build 20180427

Expected result

Last good: 20180425 (or more recent)

Debugging and logging should be improved in this case, e.g. by outputting the according information to the serial dev. @asmorodskyi also did some "network recovery" in https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/1382f2745925a0a0b4edac14896818f8f91a63c1 which could be used in cases like these as well. This might be especially important for zypper_up as it is one of the first modules to be executed but should be applied in a generic way.

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Project - action #45086: Idea: way to get logs out of os-autoinst without network ... Rejected 12/12/2018

History

#1 Updated by okurz over 1 year ago

  • Target version changed from Milestone 18 to Milestone 18

#2 Updated by okurz over 1 year ago

  • Target version changed from Milestone 18 to future

#3 Updated by okurz over 1 year ago

  • Status changed from Workable to New

Bulk action to set status back to "New" for older tickets which are in "future". They would need to be revisited in time when we come up with a defined plan and assign to a milestone.

#4 Updated by okurz about 1 year ago

  • Related to action #45086: Idea: way to get logs out of os-autoinst without network connection added

Also available in: Atom PDF