Ensure correct value from/to SERIALCONSOLE#24927
Ensure correct value from/to SERIALCONSOLE#24927waynechen55 wants to merge 1 commit intoos-autoinst:masterfrom
Conversation
4b90217 to
c4e6187
Compare
|
Welcome your review @alice-suse @guoxuguang @Julie-CAO @RoyCai7 @nanzhg @tbaev @martinsmarcelo Please help have a look if you are interested and leave a message. |
|
If it has been ensured for my 2 comments, and all validation is ok, I think it will be good enough. |
I want to further clarify that this pull request is just to ensure serial console gets reset to default value |
Thanks for the explanation. Now I understand your motivation better. To me, the code logic has changed a little bit and updates the (best-practice or necessary) requirements when setting ipmi workers. Maybe others are not that deep into the code as you about the relevant parts. Would you point out explicitly what's the change/new requirement now to configure ipmi workers? Will it additionally require CORRECT SETTINGs for SERIALDEV and SERIALCONSOLE for any ipmi worker? Let's also involve other ipmi worker users for awareness, @czerw @rfan1 @Dawei-Pang @JoyceNa . |
Basically no requirements from others. I think they can just bear in mind that But this does not exclude use of I want to reiterate that this pull request is just to reset default value of |
c4e6187 to
5c2654d
Compare
|
LGTM |
|
Commit message is missing important information, why we actually want such a change. What is broken? |
|
LGTM since no change to SERIALDEV |
ca691bd to
efdaaab
Compare
Already updated. @czerw |
efdaaab to
fd57e09
Compare
1.For OSD workers, some machines use ttyS0 and some others use ttyS1 or even ttyS2 which is assigned to setting SERIALDEV. But SERIALDEV is not safe enough to be used everywhere, because it becomes sshserial during test run, here is an example: https://openqa.suse.de/tests/21287146/file/vars.json. 2.Merge request https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/1225 introduces setting SERIALCONSOLE which is already being widely used in automation code. This can avoid incorrect SERIALCONSOLE leading to test run failure, for exmaple: https://openqa.suse.de/tests/21287262#step/prepare_transactional_server/74. 3.Current subroutine save_serial_console resets SERIALCONSOLE, if it has no value, to default value obtained from SERIALDEV which may become sshserial. So it is necessary to check and assign more meaningful default value ttyS1 to SERIALCONSOLE. And ttyS1 is also the most widely used serial console.
fd57e09 to
55c6d15
Compare
|
|
|
I finished the last verification with added |
For OSD workers, some machines use
ttyS0and some others usettyS1or eventtyS2which is assigned to settingSERIALDEV. ButSERIALDEVis not safe enough to be used everywhere, because it becomessshserialduring test run, here is an example.Merge request introduces setting
SERIALCONSOLEwhich is already being widely used in automation code. This can avoid incorrectSERIALCONSOLEleading to test run failure, for exmaple, this one.Current subroutine
save_serial_consoleresetSERIALCONSOLE, if it has no value, todefault value obtained from
SERIALDEVwhich may becomesshserial. So it is necessary to check and assign more meaningful default valuettyS1toSERIALCONSOLE. AndttyS1is also the most widely used serial console.Please also refer to update console for more details.
Verification Runs: