Project

General

Profile

Actions

action #70528

closed

[functional][u] test fails in machinery - detect "Valid metadata not found at specified URL" and record the error

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

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2020-08-26
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

Often enough we end up having to investigate multiple reasons why a test can fail, but Valid metadata not found at specified URL is common enough, and happens when a repo is not properly created or the url is malformed.

This is what happens when we get a 104 error code

Refreshing service 'Basesystem_Module_15_SP3_ppc64le'.
Refreshing service 'SUSE_Linux_Enterprise_Server_15_SP3_ppc64le'.
Refreshing service 'SUSE_Package_Hub_15_SP3_ppc64le'.
Refreshing service 'Server_Applications_Module_15_SP3_ppc64le'.
Error building the cache:
[SUSE_Package_Hub_15_SP3_ppc64le:SUSE-PackageHub-15-SP3-Backports-Pool|https://updates.suse.com/SUSE/Backports/SLE-15-SP3_ppc64le/standard?bTDqr14xJVQJUz88I2mAkFE0V3i_qZyXqBIsqNaINlKJBy7N0IH7I0unSFtoQGtI80rs5ss-7RYpIug2IQmosbaG_C1RvCukwKRQCYBeIJ1fXsVTeOKD_iLJ6HqewVE_3VAwyntimVyX] Valid metadata not found at specified URL
History:
 - [SUSE_Package_Hub_15_SP3_ppc64le:SUSE-PackageHub-15-SP3-Backports-Pool|https://updates.suse.com/SUSE/Backports/SLE-15-SP3_ppc64le/standard?bTDqr14xJVQJUz88I2mAkFE0V3i_qZyXqBIsqNaINlKJBy7N0IH7I0unSFtoQGtI80rs5ss-7RYpIug2IQmosbaG_C1RvCukwKRQCYBeIJ1fXsVTeOKD_iLJ6HqewVE_3VAwyntimVyX] Repository type can't be determined.

Warning: Skipping repository 'SUSE-PackageHub-15-SP3-Backports-Pool' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'machinery' not found in package names. Trying capabilities.
No provider of 'machinery' found.
IdFND-104-

Suggestions

Solution should be similar to https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10868

Reproducible

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

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #70132: [functional][u] test fails in machinery - detect missing capability in zypper and report the corrresponding error Resolveddheidler2020-08-17

Actions
Actions

Also available in: Atom PDF