coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Adjust bootloader_start on s390x to new YaST start message
With Build 24.1 we get a systematic failure in bootloader_start on S390x (kvm and zvm):
First line in the output says
# wait_serial expected: " Starting YaST2 "
but at the end when YaST starts the message is:
*** Starting YaST ***
Fix should be easy by adjusting the trigger text.
AC1: Trigger text is adjusted, tests no longer fail in bootloader_start
AC2: Adjusted code doesn't break other products (apparently this change is only in SLE-15-SP5)
YaST team told us, that the YaST startup message intentionally changed because of this commit:
wait_serial takes regex as parameter, favor that solution over if/else statements in code.
Updated by JERiveraMoya over 1 year ago
Would we lose much "precision" if we just do a
without checking for any specific version? Those checks always open the door to problems if new versions arrive.
It makes sense, but there are some spaces that perhaps needs to be accounted..." YaST " we'll see.
Updated by shukui over 1 year ago
Updated by openqa_review over 1 year ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: autoyast_zvm_sles_product_reg@s390x-zVM-vswitch-l2
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.