action #70129
closed[functional][u] test fails in pam - Detect invalid repositories and report them as such
0%
Description
Description¶
openQA test in scenario sle-15-SP3-Online-x86_64-extra_tests_textmode@svirt-xen-pv fails in
pam
To ease investigation during review, would be helpful to have a result box that reports when a repository is broken in the referenced test, we're able to see the problem, because the normal root console is being used, however, if serial-terminal is being used, we end up in a different scenario, where logs have to be analyzed.
Suggestions¶
Ideally, one more elsif
block before detection of package conflicts with a search for THROW:.*
if the command was ar
for instance
2020-08-14 08:33:59 <5> 1c196(10433) [zypp] Exception.cc(log):166 RepoManager.cc(refreshMetadata):1223 THROW: [qa-head-repo|http://download.suse.de/ibs/QA:/Head/SLE-15-SP3] Valid metadata not found at specified URL
2020-08-14 08:33:59 <5> 1c196(10433) [zypp] Exception.cc(log):166 History:
2020-08-14 08:33:59 <5> 1c196(10433) [zypp] Exception.cc(log):166 - [qa-head-repo|http://download.suse.de/ibs/QA:/Head/SLE-15-SP3] Repository type can't be determined.
2020-08-14 08:33:59 <5> 1c196(10433) [zypp] Exception.cc(log):166
2020-08-14 08:33:59 <5> 1c196(10433) [zypp] Exception.cc(log):166 repos.cc(refresh_raw_metadata):383 CAUGHT: [qa-head-repo|http://download.suse.de/ibs/QA:/Head/SLE-15-SP3] Valid metadata not found at specified URL
2020-08-14 08:33:59 <5> 1c196(10433) [zypp] Exception.cc(log):166 History:
2020-08-14 08:33:59 <5> 1c196(10433) [zypp] Exception.cc(log):166 - [qa-head-repo|http://download.suse.de/ibs/QA:/Head/SLE-15-SP3] Repository type can't be determined.
2020-08-14 08:33:59 <5> 1c196(10433) [zypp] Exception.cc(log):166
2020-08-14 08:33:59 <3> 1c196(10433) [zypper] refresh.cc(refreshRepositories):263 Skipping repository 'qa-head-repo' because of the above error.
Reproducible¶
Fails since (at least) Build 14.2 (current job)
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by szarate over 4 years ago
- Category changed from Bugs in existing tests to Refactor/Code Improvements
Updated by SLindoMansilla over 4 years ago
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
Updated by dheidler over 4 years ago
- Status changed from Workable to In Progress
- Assignee set to dheidler
Updated by szarate over 4 years ago
- Related to action #70132: [functional][u] test fails in machinery - detect missing capability in zypper and report the corrresponding error added
Updated by dheidler over 4 years ago
- Status changed from In Progress to Feedback
Updated by dheidler over 4 years ago
- Status changed from Feedback to Resolved
Repo was fixed in the meantime so no way to have a fast verification on osd.
Updated by szarate about 3 years ago
- Related to action #106916: [qe-core] test fails in rmt_feature - detect failing post-install scripts during zypper_calls added