Project

General

Profile

Actions

action #10466

closed

s390x: network-device ctc can't establish a connection and so can't find a repo

Added by mgriessmeier about 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2016-01-28
Due date:
% Done:

90%

Estimated time:

Description

Actions #1

Updated by mgriessmeier about 8 years ago

  • % Done changed from 0 to 90

fixed and tested locally - applied fix to S390_NETWORK_PARAMS in openqa machine description
=> waiting for a new build in openqa to see if it works in production

Actions #2

Updated by RBrownSUSE about 8 years ago

Fix did not work in build886

Actions #3

Updated by mgriessmeier about 8 years ago

  • Target version changed from Milestone 1 to Milestone 2

this is still under observation but seems to be a misconfiguration problem in our hardware..
-> carry over to milestone 2

Actions #4

Updated by okurz over 7 years ago

  • Category set to 132
  • Status changed from In Progress to Feedback

workaround of retrying on setup problems on ctc applied with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1572

deleted from test development job group and added to server acceptance group. Let's see how it behaves.

Actions #5

Updated by mgriessmeier over 7 years ago

not a comment about the CTC issue, but apparently we introduced a misleading error message, which triggers on every installation which is not able to load the installation system
see https://openqa.suse.de/tests/489090

Actions #6

Updated by okurz over 7 years ago

  • Assignee changed from mgriessmeier to okurz

message fixed, should work now, maybe not super stable, let's see.

Actions #7

Updated by okurz over 7 years ago

  • Status changed from Feedback to Resolved
Actions #8

Updated by okurz over 7 years ago

  • Status changed from Resolved to In Progress

looking at a more recent job we can see it fails in about one out of 15 runs: https://openqa.suse.de/tests/513687?limit_previous=100#previous

I crosschecked logs when the repo gets actually deleted and it got deleted after the job failed so it's not like it already vanished when the test ran. Maybe we can solve it with retrying even more or waiting a bit in between --> https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1715

Actions #9

Updated by okurz over 7 years ago

  • Status changed from In Progress to Resolved

PR merged, that should really hold for some time. https://openqa.suse.de/tests/521475?limit_previous=50#previous doesn't look too bad.

Actions

Also available in: Atom PDF