Project

General

Profile

Actions
Copy link

action #17374

closed

Used repository does not exist on download.suse.de

Added by mkravec almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
michalnowak
Category:
Infrastructure
Target version:
-
Start date:
2017-02-28
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

There is no "Update/standard" subproject in:
http://download.suse.de/ibs/SUSE:/SLE-12-SP3:/

Observation

openQA test in scenario sle-12-SP3-Server-DVD-x86_64-sles12sp2_autoyast_bug-870820_sles12@64bit fails in
repos

Reproducible

Fails since (at least) Build 0051

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by michalnowak almost 8 years ago

  • Category changed from Bugs in existing tests to Infrastructure
  • Status changed from New to In Progress
  • Assignee set to michalnowak

Some smart kludge in AutoYaST is, seemingly, changing SP2 repo to SP3, if the installed system is SP2, but such a repo does not exist, obviously. Well, adding Updates repo hampers the testing in any case. Will remove the additional defined repo in the XML profile and add it to new SP3 autoyast profile dir in data/.

Actions
Copy link
 #2

Updated by michalnowak almost 8 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #3

Updated by michalnowak almost 8 years ago

  • Status changed from Feedback to Resolved

Well, the repo magic is being done by a script downloaded from FTP. Nothing we can control. This just can't be run on development version reliably. Will remove 'sles12sp2_autoyast_bug-870820_sles12' from SP3 dev autoyast group.

Actions
Copy link
 #4

Updated by okurz over 7 years ago

  1. can't the according repo not always be disabled afterwards in one of the test modules?
  2. if there is no update repo for sp3 we can ask for one to be added. Basically it is one of the tasks that always have to be done on every version switch and this process can be improved.

When you say you remove 'sles12sp2_autoyast_bug-870820_sles12' from SP3 dev autoyast group does that mean you disabled it from the job group or also deleted the test suite or moved it to another group? If the test suite is really useless I recommend to fully delete it. If it is just not currently useful to run for SLE 12 SP3 I recommend to split the autoyast group accordingly and move tests that work into "sles functional" and others in the "did not work for long time" group

Actions
Copy link

Also available in: Atom PDF