action #68696: xterm always start then exit immediately during continuously test run - openQA Tests - openSUSE Project Management Tool

Actions

Copy link

action #68696

closed

xterm always start then exit immediately during continuously test run

Added by dawei_pang almost 4 years ago. Updated almost 4 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

dawei_pang

Category:

Target version:

Start date:

2020-07-07

Due date:

% Done:

Estimated time:

Difficulty:

Description

Initially observed xterm always start then exit immediately during continuously test run, for example: http://10.67.19.72/tests/15

[2020-07-03T01:45:05.482 CST] [debug] <<< testapi::select_console(testapi_console="sol", await_console=0)
/usr/lib/os-autoinst/consoles/vnc_base.pm:62:{
"ikvm" => 0,
"port" => 36829,
"hostname" => "localhost"
}
[2020-07-03T01:45:05.525 CST] [debug] Connected to Xvnc - PID 20497
icewm PID is 20504
xterm PID is 20506
[2020-07-03T01:45:06.587 CST] [debug] led state 0 0 0 -261
[2020-07-03T01:45:06.596 CST] [debug] activate_console, console: sol, type:
[2020-07-03T01:45:06.596 CST] [debug] activate_console called with generic type, no action
[2020-07-03T01:45:06.596 CST] [debug] tests/virt_autotest/login_console.pm:168 called login_console::login_to_console -> tests/virt_autotest/login_console.pm:46 called testapi::send_key_until_needlematch
... ...
[2020-07-03T01:45:06.669 CST] [debug] Driver backend collected unknown process with pid 20506 and exit status: 0

package version:
openQA-local-db-4.6.1589882993.dd2749ac3-lp152.1.15.noarch
openQA-client-4.6.1593790150.a010576f0-lp152.2947.1.noarch
openQA-4.6.1593790150.a010576f0-lp152.2947.1.noarch
openQA-worker-4.6.1593790150.a010576f0-lp152.2947.1.noarch
openQA-common-4.6.1593790150.a010576f0-lp152.2947.1.noarch
openQAtest:~ # rpm -qa | grep os-autoin
os-autoinst-4.6.1593790773.2f943dc7-lp152.468.1.x86_64

Actions

Copy link

Updated by dawei_pang almost 4 years ago

After some debugging in consoles::sshXtermIPMI, xterm is launched by "/usr/bin/xterm-console" with parameter like "ipmitool -H HOSTNAME -U USERNAME -P PASSWORD -I lanplus sol activate", at that time executing "ipmitool ... sol activate" is failure, because the SOL is not deactivate in previous test run.

Base on the above investigation, adding disable() function in consoles::sshXtermIPMI to 1) deactivate IPMI SOL 2) call parent disable(), so as to complete SOL deactivate during BACKEND SHUTDOWN.

Actions

Copy link