coordination #151822: [epic] Soft-fails mitigation
Added by JERiveraMoya 7 months ago. Updated 5 months ago.
0%
Description
See parent epic.
https://openqa.suse.de/tests/12837013#step/release_notes_from_url/7 -> bsc#1190711
AC1: Revisit soft-failure bsc#1190711
Now we need wait developer's reply in https://bugzilla.suse.com/show_bug.cgi?id=1190711#c9 for 'when should be expected this release notes via URL for the scenario to succeed', then we can decide how to do for this soft-failure.
leli wrote in #note-3:
Now we need wait developer's reply in https://bugzilla.suse.com/show_bug.cgi?id=1190711#c9 for 'when should be expected this release notes via URL for the scenario to succeed', then we can decide how to do for this soft-failure.
Developer didn't respond since Feb, please, read again the epic, the goal is to take some actions not to wait, you need to chase the problem or understand the problem and justify why give up in the worst case.
Please refer to https://suse.slack.com/archives/C02CLB2LB7Z/p1704179087246679 for suggestions and info for this ticket.
Currently I will continue contact Rado for Stefan's suggestion in https://bugzilla.suse.com/show_bug.cgi?id=1190711#c3 which will update the release note for the product string even in early stage, test code won't need change and test will pass consistently, but need wait...
Another thing is to detect somehow the develpment phase we are, so before RC the test passes with RPM and after RC it fails (no soft-failure).
we will do check always, just rpm from RC and url after, so we can create a more urgent bug that will not be neglected.
After discussing, we figured out that we can use the build title to provide information whether the build is RC and BETA variable to check if it's GMC.
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18441
Module passes successfully by only recording an error: https://openqa.suse.de/tests/13332712#step/release_notes_from_url/9