Actions
action #47423
closed[functional][u] test fails in zypper_ref - ZYPPER_EXIT_NO_REPOS
Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Start date:
2019-02-12
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
openQA test in scenario skip_registration+all-packages-iso fails in
zypper_ref
Reproducible¶
Fails since (at least) Build 162.2 (current job)
Expected result¶
Last good: 161.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Zypper returns ZYPPER_EXIT_NO_REPOS because there are no ENABLED repos.
Updated by okurz about 5 years ago
- Subject changed from [functional][i] test fails in zypper_ref - ZYPPER_EXIT_NO_REPOS to [functional][u] test fails in zypper_ref - ZYPPER_EXIT_NO_REPOS
I guess you meant [u]? Please add the scenario name
Updated by okurz about 5 years ago
- Status changed from New to Workable
- Priority changed from Normal to High
Also, for issues linked to current test failures we should use "High" and set to workable when it's a clear regression with last good known.
Updated by dheidler about 5 years ago
- Status changed from Workable to In Progress
- Assignee set to dheidler
Updated by dheidler about 5 years ago
- Status changed from In Progress to Resolved
Having a 2nd look it actually looks like a product bug.
Actions