action #117100
Updated by JERiveraMoya 4 months ago
### Observation
With **Build 24.1** we get a systematic failure in bootloader_start on S390x (kvm and zvm): S390x:
Example: https://openqa.suse.de/tests/9563755#step/bootloader_start/37
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.
### Scope
YaST validation tests.
### Acceptance criteria
**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)
### Additional info
YaST team told us, that the YaST startup message intentionally changed because of this commit:
https://github.com/yast/yast-installation/commit/462733aca602bb2cf9eb8f309b9c58620b7f2938
[wait_serial](http://open.qa/api/testapi/#_wait_serial) takes regex as parameter, favor that solution over if/else statements in code.
With **Build 24.1** we get a systematic failure in bootloader_start on S390x (kvm and zvm): S390x:
Example: https://openqa.suse.de/tests/9563755#step/bootloader_start/37
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.
### Scope
YaST validation tests.
### Acceptance criteria
**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)
### Additional info
YaST team told us, that the YaST startup message intentionally changed because of this commit:
https://github.com/yast/yast-installation/commit/462733aca602bb2cf9eb8f309b9c58620b7f2938
[wait_serial](http://open.qa/api/testapi/#_wait_serial) takes regex as parameter, favor that solution over if/else statements in code.