Project

General

Profile

Actions
Copy link

action #64977

closed

[opensuse] test fails in zypper_ref - test runs before repo synced

Added by okurz about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
andriinikitin
Category:
Regressions/Crashes
Target version:
Current Sprint
Start date:
2020-03-30
Due date:
% Done:

100%

Estimated time:

Description

Observation

openQA test in scenario microos-Tumbleweed-DVD-x86_64-microos@64bit fails in
zypper_ref
fails to update in https://openqa.opensuse.org/tests/1218281#step/zypper_ref/24 and many other test scenarios. Any idea what's wrong with the network to access o3 repos?
in general network works, e.g. able to access o3 itself in https://openqa.opensuse.org/tests/1218281#step/networking/5 and o3:/var/lib/openqa/share/factory/repo/openSUSE-Tumbleweed-oss-i586-x86_64-Snapshot20200329 also exists and looks ok to me. perform code: 22 [ HTTP response code said error ] whatever that means... but locally the files can be downloaded fine.

Reproducible

Fails since this Build 20200329 in multiple scenarios.

Expected result

Last good: 20200327 (or more recent)

Workaround

Retrigger tests after OBSsync is finished, most likely at the time of looking at failed jobs

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by okurz about 4 years ago

  • Status changed from New to In Progress
  • Assignee set to favogt

@favogt you wanted to look into this with investigating live openQA sessions.

Actions
Copy link
 #2

Updated by favogt about 4 years ago

  • Subject changed from [opensuse] test fails in zypper_ref - fails to update from repos on o3 but repos exists and network works to [opensuse] test fails in zypper_ref - test runs before repo synced
  • Assignee changed from favogt to andriinikitin

https://openqa.opensuse.org/minion/jobs?id=136521: "finished" => "2020-03-30T06:42:21.69718Z",
The test tried to download at 2020-03-30 06:32:13 localhost(1856) [zypp] MediaCurl.cc(doGetDoesFileExist):903 perform code: 22 [ HTTP response code said error ]

So assuming the clocks are not more than 10 minutes out of sync, the test was started before the repos were available.

Actions
Copy link
 #3

Updated by okurz about 4 years ago

  • Project changed from openQA Tests to openQA Project
  • Description updated (diff)
  • Category changed from Bugs in existing tests to Regressions/Crashes
  • Status changed from In Progress to Workable
Actions
Copy link
 #4

Updated by andriinikitin about 4 years ago

  • Status changed from Workable to In Progress

I must admit it is sync problem

Actions
Copy link
 #5

Updated by okurz about 4 years ago

  • Priority changed from Urgent to High

With the workaround in place I think we can treat this now with "High" priority, one down from "Urgent".

Actions
Copy link
 #6

Updated by livdywan about 4 years ago

  • Target version set to Current Sprint
Actions
Copy link
 #7

Updated by andriinikitin about 4 years ago

  • Status changed from In Progress to Resolved

Should be solved by reverting split of appliances into separate run and stick with previous implementation when Factory appliances repo is never checked for success
https://github.com/andrii-suse/openqa-trigger-from-obs/pull/68

Actions
Copy link
 #8

Updated by andriinikitin about 4 years ago

  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF