action #97316
Updated by JERiveraMoya over 2 years ago
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 origin. ## Observation openQA test in scenario sle-15-SP4-Full-aarch64-releasenotes_origin+unregistered@aarch64 fails in [releasenotes_origin](https://openqa.suse.de/tests/6886738/modules/releasenotes_origin/steps/5) ## 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](https://openqa.suse.de/tests/6860553) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Full&machine=aarch64&test=releasenotes_origin%2Bunregistered&version=15-SP4)