openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-08-23T08:20:01ZopenSUSE Project Management Tool
Redmine openQA Infrastructure - action #55868 (Resolved): USB device is removed from gonzo.qa.suse.de.https://progress.opensuse.org/issues/558682019-08-23T08:20:01Zxlaixlai@suse.com
<p>We equipped on some servers some usb device to test virtualization pvusb feature. However today from a failure test <a href="https://openqa.suse.de/tests/3280807">https://openqa.suse.de/tests/3280807</a>, we noticed that the logitech mouse usb device on it was accidentally removed by someone and resulted in test failure.</p>
<p>SUT_IP: gonzo.qa.suse.de<br>
Missing USB device: <br>
Bus 003 Device 002: ID 046d:c001 Logitech, Inc. N48/M-BB48/M-UK96A [FirstMouse Plus]</p>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/24624">@nicksinger</a> Would you please help to find out who moved it and ask him/her to recover it? I know it is not easy since so many people have access to lab. If you can not find it, would you please help to remind people to not move our usb devices? Really appreciate if you can help paste some warning msg on these machines.</p>
<p>SUTs with usb device:<br>
21:<br>
WORKER_CLASS: virt-mm-64bit-ipmi,virt-pvusb-64bit-ipmi,64bit-ipmi<br>
IPMI_HOSTNAME: sp.kermit.qa.suse.de<br>
IPMI_PASSWORD: ADMIN<br>
IPMI_USER: ADMIN<br>
MAX_JOB_TIME: 32000<br>
SUT_IP: kermit.qa.suse.de<br>
PVUSB_DEVICE: Keyboard<br>
22: //missing now<br>
WORKER_CLASS: virt-mm-64bit-ipmi,virt-pvusb-64bit-ipmi,64bit-ipmi<br>
IPMI_HOSTNAME: sp.gonzo.qa.suse.de<br>
IPMI_PASSWORD: ADMIN<br>
IPMI_USER: ADMIN<br>
MAX_JOB_TIME: 32000<br>
SUT_IP: gonzo.qa.suse.de<br>
PVUSB_DEVICE: Logitech<br>
23:<br>
WORKER_CLASS: virt-mm-64bit-ipmi,virt-pvusb-64bit-ipmi,64bit-ipmi<br>
IPMI_HOSTNAME: sp.fozzie.qa.suse.de<br>
IPMI_PASSWORD: ADMIN<br>
IPMI_USER: ADMIN<br>
MAX_JOB_TIME: 32000<br>
SUT_IP: fozzie-1.qa.suse.de<br>
PVUSB_DEVICE: Logitech<br>
24:<br>
WORKER_CLASS: virt-mm-64bit-ipmi,virt-pvusb-64bit-ipmi,64bit-ipmi<br>
IPMI_HOSTNAME: sp.scooter.qa.suse.de<br>
IPMI_PASSWORD: ADMIN<br>
IPMI_USER: ADMIN<br>
MAX_JOB_TIME: 32000<br>
SUT_IP: scooter-1.qa.suse.de</p>
<pre><code> 16:
WORKER_CLASS: virt-pvusb-64bit-ipmi,64bit-ipmi
IPMI_HOSTNAME: 10.162.28.200
IPMI_PASSWORD: qatesting
IPMI_USER: admin
MAX_JOB_TIME: 32000
SUT_IP: 10.162.2.75
PVUSB_DEVICE: Winbond
17: # new worker quinn.qa.suse.de
WORKER_CLASS: virt-pvusb-64bit-ipmi,64bit-ipmi
IPMI_HOSTNAME: 10.162.3.87
IPMI_PASSWORD: ADMIN
IPMI_USER: ADMIN
SUT_IP: 10.162.2.87
MAX_JOB_TIME: 32000
PVUSB_DEVICE: Verbatim
</code></pre> openQA Tests - action #33136 (Resolved): [virtualization][functional][y] XEN/KVM host text mode ...https://progress.opensuse.org/issues/331362018-03-13T10:51:53Zxlaixlai@suse.com
<p>On build 499.1, most virtualization jobs fail at host installation phase, because PR <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4565" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4565</a> does not add needed needles for such installations.</p>
<p>Virtualization tests really depend on and affected by common installation or special change for xen/kvm roles or special change for ipmi backend. Not only test process delayed, but also we need spend quite some effort to debug the root cause.</p>
<p>Suggestion for future openqa PR-- to deliver to openqa PR reviewers:<br>
when there is code change on common installation or special change for xen/kvm roles or special change for ipmi backend, please add verification run on <a href="https://openqa.suse.de/tests/1536711" class="external">https://openqa.suse.de/tests/1536711</a> (kvm) and <a href="https://openqa.suse.de/tests/1534947" class="external">https://openqa.suse.de/tests/1534947</a> (xen) and make sure the host installation part pass , before it gets merged.</p>
openQA Tests - action #19086 (Closed): Fv guest installation failed in Build0367-prj2_host_upgrad...https://progress.opensuse.org/issues/190862017-05-10T09:51:36Zxlaixlai@suse.com
<p>Job link:<br>
<a href="https://openqa.suse.de/tests/917095" class="external">https://openqa.suse.de/tests/917095</a></p>
<a name="further-details"></a>
<h2 >further details<a href="#further-details" class="wiki-anchor">¶</a></h2>
<p>Link to <a href="https://openqa.suse.de/tests/latest?test=prj2_host_upgrade_sles12sp1_to_sles12sp3_kvm&flavor=Server-DVD&arch=x86_64&distri=sle&machine=64bit-ipmi&version=12-SP3" class="external">latest</a></p>
openQA Tests - action #18834 (Rejected): [virtualization] Orthos machine is still not ready to be...https://progress.opensuse.org/issues/188342017-04-27T09:36:31Zxlaixlai@suse.com
<p>We want to use orthos machine for virtualization testing via proxy way. Richard has helped to mount daily builds to the pxe server of the orthos machine. </p>
<p>However when installing via pxe, after typing the commands in the pxe screen(like in boot_from_pxe), the machine just hangs, and does not respond to start installation. The command is confirmed to be supported on that machine(from email reply in OPS team). But we suspect either the pxe server or that machine is not properly set up. But we can not get support.</p>
<p>Who can help to push it? We are blocked here and still can not use orthos machine in testing although it is proper.</p>
openQA Tests - action #17936 (Resolved): [tools]Add jenkins job to automatically trigger ipmi mai...https://progress.opensuse.org/issues/179362017-03-24T03:32:22Zxlaixlai@suse.com
<p>From the virtualization practice using ipmi machine, I find that the ipmi machine's ipmi main board become unstable after using constantly for some time like two weeks or long. It made the test results unreliable. I had to restart ipmi manually and retrigger the job after I found it.</p>
<p>So maybe we can add a new jenkins job to do such a thing. To avoid the restart affecting running jobs, it is better to be done on two constraints, one is to meet the time period check( machine is used for over two weeks or so), second is before a new build trigger starts.</p>
<p>@oliver, do you agree with such a resolution? Can we write a jenkins job to do it?</p>
openQA Tests - action #17866 (Resolved): [tools]Please add sles12sp2 x86_64 GM repo image to http...https://progress.opensuse.org/issues/178662017-03-22T06:45:56Zxlaixlai@suse.com
<p>I just noticed there was no sles12sp2 x86_64 GM repo image in <a href="https://openqa.suse.de/assets/repo/fixed/" class="external">https://openqa.suse.de/assets/repo/fixed/</a>.</p>
<p>Would you please help to add it? Sorry for not giving the request together with sle11 image.</p>
openQA Tests - action #17694 (Resolved): [tools][virtualization]Please add sles11sp3/sles11sp4 GM...https://progress.opensuse.org/issues/176942017-03-14T08:19:31Zxlaixlai@suse.com
<p>We decide to deploy all guest installation tests into openqa and use it for sles12sp3 verification. It contains scenarios on sles11sp3/sp4 host. So we will need these images for host installation via pxe on ipmi machine.</p>
openQA Project - action #16602 (Resolved): Comment with unicode characters do not work because of...https://progress.opensuse.org/issues/166022017-02-09T02:24:15Zxlaixlai@suse.com
<a name="observation"></a>
<h2 >observation<a href="#observation" class="wiki-anchor">¶</a></h2>
<p>An error message is reported when I updated result for a build on virtualization group on openqa.suse.de</p>
<p>What was typed on comment:</p>
<pre><code>**Date:** <2017-02-09>
**Build:** 0234
**Arch:** x86_64
**Status: <font color="red">Red</font>
**New Product bugs:**
* No
**Requirement:**
* one more ipmi machine: poo#15376
**Existing Product bugs:**
* sles12sp3 pv guest installation: bsc#1012005
* pvusb bug on sles12sp3 xen: bsc#1023948
**Existing openqa issues:**
* guest migration job fail/multi-machine: poo#15376
* ipmi ikvm unstable: poo#14338
* ipmi serial console unstable: poo#13914
* ipmi keyboard simulator unstable: poo#12982 poo#16088
</code></pre>
<a name="steps-to-reproduce"></a>
<h2 >steps to reproduce<a href="#steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<ul>
<li>on an openQA instance with enabled rabbitmq plugin</li>
<li>type character '/' in any comment</li>
<li>observe reported error</li>
</ul>
<a name="problem"></a>
<h2 >problem<a href="#problem" class="wiki-anchor">¶</a></h2>
<p>H1. Mojo::RabbitMQ::Client does not handle unicode input correctly<br>
<a href="https://github.com/inway/mojo-rabbitmq-client/commit/c043447d4fa53a1456515c4def1c4d1367cd87b0#commitcomment-20829251" class="external">https://github.com/inway/mojo-rabbitmq-client/commit/c043447d4fa53a1456515c4def1c4d1367cd87b0#commitcomment-20829251</a><br>
H2. <code>lib/OpenQA/WebAPI/Plugin/AMQP.pm</code> does not forward unicode correctly to Mojo::RabbitMQ::Client</p>
<a name="workaround"></a>
<h2 >workaround<a href="#workaround" class="wiki-anchor">¶</a></h2>
<p>only type ascii within comments.</p>
openQA Infrastructure - action #16088 (Rejected): [ipmi] Do not respond to send_key.https://progress.opensuse.org/issues/160882017-01-19T06:02:20Zxlaixlai@suse.com
<p>In job <a href="https://openqa.suse.de/tests/716647#step/reboot_and_wait_up_normal2/3" class="external">https://openqa.suse.de/tests/716647#step/reboot_and_wait_up_normal2/3</a>, we use send_key_until_needle_match api to select xen grub menuentry, however after catching a not matching screen, and a send_key is sent, screen does not change.</p>
openQA Tests - action #15376 (Resolved): Need one more stable ipmi physical machine for virtualiz...https://progress.opensuse.org/issues/153762016-12-08T08:44:37Zxlaixlai@suse.com
<p>Requirement: <br>
Please add one more ipmi machine with stable ipmi.</p>
<p>Background:<br>
Currently, we only get one stable ipmi machine which is pointed to by worker openqaw2:1. As we add more virtualization tests, we have multi machine jobs involving, including guest migration which was added into openqa already. Also we plan to add virt-v2v, post copy migration tests before sle12sp3 milestone starts. They all require 2 ipmi machines.</p>
openQA Tests - action #14338 (Resolved): [ipmi] ikvm does not get timely image backhttps://progress.opensuse.org/issues/143382016-10-20T09:24:20Zxlaixlai@suse.com
<p>Assert_screen does not get any screenshot back, although it fails, so ikvm does not respond any more</p>
<p>Failed test<br>
<a href="https://openqa.suse.de/tests/619762#" class="external">https://openqa.suse.de/tests/619762#</a></p>
openQA Tests - action #13918 (Rejected): ipmi backend: test incomplete due to code not robust eno...https://progress.opensuse.org/issues/139182016-09-27T01:39:46Zxlaixlai@suse.com
<p>Issue:<br>
IPMI backend needs to handle temporary ipmi session establishment problems to make test more robust.</p>
<p>Test link:<br>
<a href="https://openqa.suse.de/tests/586661/file/autoinst-log.txt" class="external">https://openqa.suse.de/tests/586661/file/autoinst-log.txt</a></p>
<p>Job build link:<br>
<a href="https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2140&groupid=46" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2140&groupid=46</a></p>
<p>Key error log:<br>
12:04:38.1385 2809 IPMI: Chassis Power Control: Down/Off<br>
12:04:38.1681 2809 IPMI: Chassis Power is off<br>
12:04:38.1968 2809 IPMI: Chassis Power Control: Up/On<br>
12:04:38.2270 2809 IPMI: Chassis Power is off<br>
12:04:38.2573 2809 IPMI: Chassis Power Control: Up/On<br>
12:04:40.2889 2809 IPMI: Chassis Power is off<br>
12:04:40.3201 2809 IPMI: Chassis Power Control: Up/On<br>
Error: Unable to establish LAN session at /usr/lib/os-autoinst/backend/ipmi.pm line 62.</p>
openQA Tests - action #13916 (Rejected): [ipmi] What should be typed by type_string is not typed ...https://progress.opensuse.org/issues/139162016-09-27T01:38:14Zxlaixlai@suse.com
<p>In build <a href="https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2144&groupid=46" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2144&groupid=46</a>, two tests failed because what should be typed by type_string is not actually typed at all to screen . There is no ipmi connection issue reported from either serial0.txt or autoinst log. But from screenshot, the string required is not typed at all.</p>
<p>Detailed failure:<br>
<a href="https://openqa.suse.de/tests/589661#comments" class="external">https://openqa.suse.de/tests/589661#comments</a><br>
<a href="https://openqa.suse.de/tests/589666#comments" class="external">https://openqa.suse.de/tests/589666#comments</a></p>
openQA Tests - action #12982 (Closed): What are typed by type_string on ipmi physical machine is ...https://progress.opensuse.org/issues/129822016-08-02T09:36:58Zxlaixlai@suse.com
<p>Job link: <a href="https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2016&groupid=46" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2016&groupid=46</a></p>
<p>Testsuites:</p>
<p>*gi-guest_sles12sp2-on-host_sles12sp2-kvm:</p>
<p>Fail stage: host installation<br>
Fail reason: what are typed out by type_string is not complete<br>
At the last step of installation , 'install and reboot', command 'save_y2logs /tmp/y2logs.tar.bz2 ' is typed to 'save_y2lgs /tmp/y2logs.tar.bz2' which results to 'command y2lgs not found' and exit </p>
<p>Also failed for the similar reason in following build tests.</p>
openQA Tests - action #12926 (Resolved): Can not get ipmi serial output correctly.https://progress.opensuse.org/issues/129262016-07-29T07:11:57Zxlaixlai@suse.com
<p>CASE FAILURES:</p>
<p>Job link: <a href="https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2016&groupid=46">https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2016&groupid=46</a></p>
<p>Testsuites:</p>
<p>*gi-guest_sles12sp2-on-host_sles12sp2-kvm:</p>
<p>Fail stage: host installation<br>
Fail reason: what are typed out by type_string is not complete<br>
At the last step of installation , 'install and reboot', command 'save_y2logs /tmp/y2logs.tar.bz2 ' is typed to 'save_y2lgs /tmp/y2logs.tar.bz2' which results to 'command y2lgs not found' and exit </p>
<p>*gi-guest_sles11sp4-on-host_sles12sp2-kvm</p>
<p>Fail stage: run the first script after login on the newly installed system<br>
Fail reason: Seems unstable serial<br>
Did not get the check code on serial for upload logs, but the previous check code of our virt code was got.</p>
<p>Logs:<br>
20:01:14.5759 24169 <<< testapi::type_string(string='(source /usr/share/qa/virtautolib/lib/virtlib;update_virt_rpms off on off 2>&1 | tee /tmp/update_virt_rpms.log ; echo CMD_FINISHED-45346) 2>&1 | tee -a /dev/ttyS1<br>
', max_interval=250)<br>
20:01:26.2177 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/install_package.pm:44 called virt_autotest_base::execute_script_run<br>
20:01:26.2182 24169 <<< testapi::wait_serial(regex='CMD_FINISHED-45346', timeout=7200)<br>
20:02:02.2913 24169 >>> testapi::wait_serial: CMD_FINISHED-45346: ok</p>
<p>20:02:02.4125 24169 <<< testapi::type_string(string='curl --form upload=@/tmp/update_virt_rpms.log --form upname=install_package-update_virt_rpms.log <a href="http://10.162.0.12:20013/JI6Pc6TclLAoD8J5/uploadlog/update_virt_rpms.log">http://10.162.0.12:20013/JI6Pc6TclLAoD8J5/uploadlog/update_virt_rpms.log</a>; echo CUMYV-$?- > /dev/ttyS1', max_interval=250)<br>
20:02:15.7595 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/install_package.pm:47 called testapi::upload_logs<br>
20:02:15.7597 24169 <<< testapi::send_key(key='ret')<br>
20:02:15.9613 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/install_package.pm:47 called testapi::upload_logs<br>
20:02:15.9617 24169 <<< testapi::wait_serial(regex='CUMYV-\d+-', timeout=90)<br>
20:06:46.7188 24169 >>> testapi::wait_serial: CUMYV-\d+-: fail</p>
<p>*gi-guest_sles12sp1-on-host_sles12sp2-kvm</p>
<p>Fail stage: run the first script after login on the newly installed system<br>
Fail reason: seems serial decode problem, the serial output after the first reboot following installation are unknown character like @</p>
<p>Logs:</p>
<p>21:46:58.4681 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/guest_installation_run.pm:14 called testapi::script_output<br>
21:46:58.4683 24846 <<< testapi::script_run(name='curl -f -v <a href="http://10.162.0.12:20013/84p34tmDuUI38f1X/current_script">http://10.162.0.12:20013/84p34tmDuUI38f1X/current_script</a> > /tmp/scriptOdTh6.sh; echo dTNlY-$?- > /dev/ttyS1', wait=0)<br>
21:46:58.4684 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/guest_installation_run.pm:14 called testapi::script_output<br>
21:46:58.4685 24846 <<< testapi::type_string(string='curl -f -v <a href="http://10.162.0.12:20013/84p34tmDuUI38f1X/current_script">http://10.162.0.12:20013/84p34tmDuUI38f1X/current_script</a> > /tmp/scriptOdTh6.sh; echo dTNlY-$?- > /dev/ttyS1', max_interval=250)<br>
21:47:06.8974 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/guest_installation_run.pm:14 called testapi::script_output<br>
21:47:06.8976 24846 <<< testapi::send_key(key='ret')<br>
21:47:07.0989 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/guest_installation_run.pm:14 called testapi::script_output<br>
21:47:07.0992 24846 <<< testapi::wait_serial(regex='dTNlY-\d+-', timeout=90)<br>
21:51:38.4801 24846 >>> testapi::wait_serial: dTNlY-\d+-: fail</p>
<p>*gi-guest_sles12sp2-on-host_sles12sp1-kvm</p>
<p>Fail stage: run the first script after login on the newly installed system<br>
Fail reason: seems serial decode problem, the serial output after the first reboot following installation are unknown character like @</p>
<p>Logs:</p>
<p>00:06:36.8151 26070 <<< testapi::script_run(name='curl -f -v <a href="http://10.162.0.12:20013/vkUq43upmdPkRsHZ/current_script">http://10.162.0.12:20013/vkUq43upmdPkRsHZ/current_script</a> > /tmp/scriptOdTh6.sh; echo FSXE_-$?- > /dev/ttyS1', wait=0)<br>
00:06:36.8151 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/guest_installation_run.pm:14 called testapi::script_output<br>
00:06:36.8153 26070 <<< testapi::type_string(string='curl -f -v <a href="http://10.162.0.12:20013/vkUq43upmdPkRsHZ/current_script">http://10.162.0.12:20013/vkUq43upmdPkRsHZ/current_script</a> > /tmp/scriptOdTh6.sh; echo FSXE_-$?- > /dev/ttyS1', max_interval=250)<br>
00:06:45.2365 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/guest_installation_run.pm:14 called testapi::script_output<br>
00:06:45.2368 26070 <<< testapi::send_key(key='ret')<br>
00:06:45.4379 Debug: /var/lib/openqa/share/tests/sle/tests/virt_autotest/guest_installation_run.pm:14 called testapi::script_output<br>
00:06:45.4381 26070 <<< testapi::wait_serial(regex='FSXE_-\d+-', timeout=90)<br>
00:11:16.9354 26070 >>> testapi::wait_serial: FSXE_-\d+-: fail</p>