action #97316
closedtest fails in releasenotes_origin
100%
Description
After contacting the yast team to clear up what is expected, the system gets release notes mostly from URL as they are more up to day, unless there is no availability (offline installation, not released notes yet, etc) so it gets it from RPM. The particular failure occurs because the release notes for SP4 are not yet available via URL. We can add a workaround for releasenotes_origin.pm line:24, so it doesn't fail for now. Also, we could schedule the module to offline installation test suite, where we would always expect RPM as release notes origin: https://openqa.suse.de/tests/6887000
Observation¶
openQA test in scenario sle-15-SP4-Full-aarch64-releasenotes_origin+unregistered@aarch64 fails in
releasenotes_origin
Test suite description¶
Test fate#323273 - Check the origin (rpm or url) of the showed release notes.
Reproducible¶
Fails since (at least) Build 18.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by syrianidou_sofia over 3 years ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
Updated by JERiveraMoya about 3 years ago
- Tags deleted (
qe-yast-refinement) - Description updated (diff)
- Status changed from New to Workable
Updated by rainerkoenig about 3 years ago
- Status changed from Workable to In Progress
Updated by rainerkoenig about 3 years ago
PR merged.
VRs from production:
- release_notes_from_rpm: https://openqa.suse.de/tests/7200206
- release_notes_from_url: https://openqa.suse.de/tests/7200205
Updated by rainerkoenig about 3 years ago
- Due date set to 2021-09-23
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Updated by rainerkoenig about 3 years ago
- Status changed from Feedback to Resolved