action #45938

Updated by okurz over 5 years ago

## Observation 
 Since 09th Jan the disk_boot test on Kubic is failing, but only during it's textmode scenario 

 This test should be rebooting the SUT, but that reboot does not appear to occur 

 Other Kubic scenarios that call the disk_boot test but do not use Textmode are ok 

 The product has been confirmed manually that it boots perfectly fine, even when using textmode during the installation. 

 This is strongly suspected to be an openQA issue because tests with earlier TW builds that passed before 0109 (eg ) now fail when run after the deploy that occurred on 0109 (eg 

 I honestly have NO idea how the deploy can cause this symptoms, but in the absence of any recent commit that affects the use codepath ( I think the changes introduced in the deploy to o3 are the most likely cause. 

 ## Problem 
 * **H1** *REJECT* The product has changed 
  * **H1.1** *REJECT* Specified assets have changed -> see #45938#note-1, failure reproduced with the ISO from "last good" 
  * **H1.2** *REJECT* Downloaded, dynamic content is differing and impacting the test 

 * **H2** *ACCEPT* Fails because of changes in test setup 
  * **H2.1** *REJECT* Our test hardware equipment behaves different 
  * **H2.2** *REJECT* The network behaves different 
  * **H2.3** *ACCEPT* The worker has an influence 

 * **H3** *REJECT* Fails because of changes in test infrastructure software, e.g. os-autoinst, openQA 
 * **H4** *REJECT* Fails because of changes in test management configuration, e.g. openQA database settings 
 * **H5** *REJECT* Fails because of changes in the test software itself (the test plan in source code as well as needles) -> **E2.3-1** 
 * **H6** *ACCEPT* Sporadic issue, i.e. the root problem is already hidden in the system for a long time but does not show symptoms every time 
  * **H6.1** *ACCEPT* The test code is not resilient enough to slow reboots because of the 30s timeout waiting for the grub screen in `kubic/`