openQA Project (public)

action #153111

Updated by waynechen55 11 months ago

## Observation 
 According to http://open.qa/api/testapi/, reset_consoles can be used to ensure next select_console really activates a console. But it seems that this is not true for sol console: 

 ``` 
 select_console 'sol', await_console => 0; 
 reset_consoles; 
 select_console 'sol', await_console => 0; 
 ``` 
 The sol console can not be activated anymore after operations shown in above code block. Screenshot captured by openQA looks like as below: 
 ![](inactive_ipmi_sol_console.png) 


 

 ## Steps to reproduce 
 * select_console 'sol', await_console => 0;  
 * reset_consoles;  
 * select_console 'sol', await_console => 0; 

 The machine on which this openQA instance run has been given a fresh reinstall. It runs new Leap 15.5 system. And I installed openQA on this machine by using: 

 ``` 
 curl -s https://raw.githubusercontent.com/os-autoinst/openQA/master/script/openqa-bootstrap | bash -x 
 ``` 

 ## Steps to reproduce 
 * select_console 'sol', await_console => 0;  
 * reset_consoles;  
 * select_console 'sol', await_console => 0; 

 ## Impact 
 Can not use reset_consoles with select_console. 

 ## Problem 
 Maybe the sol console is not cleaned up completely by reset_consoles. 

 ## Suggestions 
 * Clarify whether reset_consoles work well with sol console 
 * What reset_consoles does to sol console 

 ## Workaround 
 n/a

Back