openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-09-01T03:20:18ZopenSUSE Project Management Tool
Redmine openQA Tests - action #134969 (New): [qe-core] Require latest released quarterly update images fo...https://progress.opensuse.org/issues/1349692023-09-01T03:20:18Zxlaixlai@suse.com
<p>We recently get a suggestion and agreed in discussions with Heiko Rommel, Jan Stehlik, and Antoine Ginies, that when testing released products, it is better to use <code>latest QU image + scc updates</code>.</p>
<p>For detailed requirements,</p>
<ul>
<li>all supported products' latest QU image are needed,
<ul>
<li>sle12sp3~sle12sp5 (12sp3 has teradata tests after LTSS ends, 12sp4 seems ending but not final confirmed yet)</li>
<li>sle15sp2-sle15sp5 (and sle15sp6/7 when they are released)</li>
</ul></li>
<li>available in three locations' mirror server and pxe server so that local openqa servers' jobs can access them-- DE NUE2 lab(OSD), PRG1 lab (<a href="http://openqa.qam.suse.cz/" class="external">http://openqa.qam.suse.cz/</a> resides in) and BeiJing lab (<a href="http://openqa.qa2.suse.asia/" class="external">http://openqa.qa2.suse.asia/</a> resides in)
<ul>
<li>the QU images can be accessible via http(s) in repository way (unpacked from iso), and are put with FIXED names like SLExxSPx-QU-LATEST </li>
<li>the latest QU for all products are added in pxe server</li>
</ul></li>
</ul>
<p>I am not sure if this ticket's scope can be fully covered by openqa infrastructure (some should). It will help a lot, if anyone familiar with it can help point out which parts should go to which team. We will then split the ticket properly. Thanks in advance!</p>
QA - action #78444 (Closed): [virtualization] alice to deletehttps://progress.opensuse.org/issues/784442020-11-20T06:27:34Zxlaixlai@suse.comopenQA 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 #55100 (Resolved): [hyperv] Need to delete ISO with issue when checksum doe...https://progress.opensuse.org/issues/551002019-08-05T07:00:31Zxlaixlai@suse.com
<p>All vmware&hyperv jobs in virtualization job group fail by similar error <a href="https://openqa.suse.de/tests/3204511#step/welcome/10" class="external">https://openqa.suse.de/tests/3204511#step/welcome/10</a>.</p>
<p>Need to find why checksum does not match and fix it.</p>
openQA Tests - action #42899 (Resolved): Compilation failed in require at /usr/bin/isotovideo lin...https://progress.opensuse.org/issues/428992018-10-25T03:55:39Zxlaixlai@suse.com
<p>This makes openqa tests fail a lot in all job groups.</p>
<p>Job link:<br>
<a href="https://openqa.suse.de/tests/2208950/file/autoinst-log.txt" class="external">https://openqa.suse.de/tests/2208950/file/autoinst-log.txt</a></p>
<p>Key failure:<br>
[2018-10-25T00:43:11.0643 CEST] [debug] scheduling welcome tests/installation/welcome.pm<br>
[2018-10-25T00:43:11.0644 CEST] [debug] scheduling keyboard_selection tests/installation/keyboard_selection.pm<br>
[2018-10-25T00:43:11.0645 CEST] [debug] scheduling skip_registration tests/installation/skip_registration.pm<br>
[2018-10-25T00:43:11.0647 CEST] [debug] scheduling addon_products_sle tests/installation/addon_products_sle.pm<br>
Undefined subroutine &version_utils::is_server called at /var/lib/openqa/cache/tests/sle/lib/version_utils.pm line 320.<br>
Compilation failed in require at /usr/bin/isotovideo line 229.<br>
543: EXIT 1<br>
[2018-10-25T00:43:14.0671 CEST] [info] Isotovideo exit status: 1<br>
[2018-10-25T00:43:14.0698 CEST] [info] +++ worker notes +++<br>
[2018-10-25T00:43:14.0699 CEST] [info] end time: 2018-10-24 22:43:14<br>
[2018-10-25T00:43:14.0699 CEST] [info] result: died</p>
openQA Tests - action #37408 (Resolved): [openqa]Please add sle15 GM image to http://openqa.nue.s...https://progress.opensuse.org/issues/374082018-06-15T02:52:33Zxlaixlai@suse.com
<p>In sle12sp4, virtualization job group will includes tests on sle15 hosts, please help to add sle15 GM image to <a href="http://openqa.nue.suse.com/assets/repo/fixed/" class="external">http://openqa.nue.suse.com/assets/repo/fixed/</a>, like sle12sp3/sle11sp4 .</p>
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 #32746 (Resolved): [sle][tools][remote-backends][hard] Incomplete job becau...https://progress.opensuse.org/issues/327462018-03-05T02:53:08Zxlaixlai@suse.com
<p>Failure root cause from autoinst log:</p>
<p>The console isn't responding correctly. Maybe half-open socket? at /usr/lib/os-autoinst/backend/baseclass.pm line 241.</p>
<pre><code>at /usr/lib/os-autoinst/backend/baseclass.pm line 80. backend::baseclass::die_handler('The console isn\'t responding correctly. Maybe half-open sock...') called at /usr/lib/os-autoinst/backend/baseclass.pm line 241 eval {...} called at /usr/lib/os-autoinst/backend/baseclass.pm line 156 backend::baseclass::run_capture_loop('backend::ipmi=HASH(0x6205910)') called at /usr/lib/os-autoinst/backend/baseclass.pm line 129 backend::baseclass::run('backend::ipmi=HASH(0x6205910)', 5, 8) called at /usr/lib/os-autoinst/backend/driver.pm line 85 backend::driver::start('backend::driver=HASH(0x5d76870)') called at /usr/lib/os-autoinst/backend/driver.pm line 48 backend::driver::new('backend::driver', 'ipmi') called at /usr/bin/isotovideo line 211 main::init_backend() called at /usr/bin/isotovideo line 280 [2018-03-02T12:58:49.0368 CET] [debug] IPMI: Chassis Power Control: Down/Off last frame
</code></pre>
<p>Failure job link:<br>
<a href="https://openqa.suse.de/tests/1514142" class="external">https://openqa.suse.de/tests/1514142</a><br>
<a href="https://openqa.suse.de/tests/1516150" class="external">https://openqa.suse.de/tests/1516150</a></p>
openQA Tests - action #25504 (Resolved): Support for changing test variables including needles du...https://progress.opensuse.org/issues/255042017-09-22T02:56:16Zxlaixlai@suse.com
<p>In sle15, many test files of installation uses function sle_version_at_least to do check for product version, so as to differenciate sle15 new behaviors from older products. </p>
<p>However, this may be not correct. </p>
<p>Since sle12sp2, a new var INSTALL_TO_OTHERS was introduced for tests that needed to install system to a different product(mostly former product), for example in sles12sp3 release, virtualization job group in openqa.suse.de already had tests that actually installed system to sle11sp4, sle12sp1, sle12sp2, like <a href="https://openqa.suse.de/tests/1058378" class="external">https://openqa.suse.de/tests/1058378</a>. </p>
<p>So IMHO, sle15 different behavior should be done for ONLY those <em>really</em> install to a product at least 15, that is for those tests with INSTALL_TO_OTHERS, we should check the version that it want to install is at least 15, and for those without INSTALL_TO_OTHERS, just do what sle_version_at_least does. This is my first thing to talk. Do you agree?</p>
<p>Currently in utils, there are two apis, install_to_other_at_least and sle_version_at_least to check versions for both situations. So the sle15 different behavior should be done only for a condition like "((install_this_version() && sle_version_at_least('15')) || install_to_other_at_least('15'))", rather than simple sle_version_at_least('15'). </p>
<p>However the above complex condition writing is absolutely not a good idea. So here comes the second topic. Solution to it. What comes up to me are:<br>
option 1) add a new api to stand the above complex checking for versions, using the apis install_to_other_at_least and sle_version_at_least, and replace all the usages of the api to the new one, and also notify all test writers about it.<br>
option 2) keep the api, but rewrite it to represent the complex checking. Good thing is no need to change various usages. All test writers does not needs to know about the change, and continue to regard the api as the assumed perfect one.</p>
<p>I personally prefer option 2. What's your choice? Or any other solutions you can figure out?</p>
openQA Tests - action #23514 (Resolved): [labs][64bit-ipmi_debug worker] SLE15 shows interface se...https://progress.opensuse.org/issues/235142017-08-22T02:17:44Zxlaixlai@suse.comopenQA Tests - action #23368 (Resolved): ipmi worker openqaw1:4 has issue to connect to the ipmi ...https://progress.opensuse.org/issues/233682017-08-15T02:23:55Zxlaixlai@suse.com
<p>The worker's bounded SUT name can not be translated to IP.</p>
<p>Key log:<br>
DIE ipmitool -I lanplus -H openqa4-sp.qa.suse.de -U admin -P qatesting mc guid: Address lookup for openqa4-sp.qa.suse.de failed<br>
Could not open socket!<br>
Error: Unable to establish IPMI v2 / RMCP+ session at /usr/lib/os-autoinst/backend/ipmi.pm line 62.</p>
<p>Job link:<br>
<a href="https://openqa.suse.de/tests/1108863" class="external">https://openqa.suse.de/tests/1108863</a></p>
openQA Tests - action #19994 (Resolved): Time out when install guest on sles12sp1 xen.https://progress.opensuse.org/issues/199942017-06-22T07:15:37Zxlaixlai@suse.com
<p>Fail job link <a href="https://openqa.suse.de/tests/1002358#step/guest_installation_run/12" class="external">https://openqa.suse.de/tests/1002358#step/guest_installation_run/12</a>.<br>
Failed due to timeout, but it should not. Something unexpected happen. Please fix it.</p>
openQA Tests - action #19992 (Resolved): [sle][virtualization]Guest installation on sle11sp4 both...https://progress.opensuse.org/issues/199922017-06-22T07:12:55Zxlaixlai@suse.com
<p>Refer to <a href="https://openqa.suse.de/tests/1004374" class="external">https://openqa.suse.de/tests/1004374</a> and <a href="https://openqa.suse.de/tests/1004375" class="external">https://openqa.suse.de/tests/1004375</a>, the guest installation is skipped. </p>
<p>Suspect to be automation issue in qa_lib_virtauto, in vm-install.sh script.</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 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>