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>
openQA Project - coordination #58166 (Resolved): EPIC: Continue tests after failures on !qemuhttps://progress.opensuse.org/issues/581662019-10-15T06:06:43Zxlaixlai@suse.com
<p>Our jobs run on ipmi workers. When many tests chained, to get high test efficiency, we need the feature that the following tests can continue when earlier tests fail.</p>
<p>We were suggested to set fatal flag to 0 to these tests. However from the tried example, it did not work.</p>
<p>Failure job link: <br>
<a href="http://10.67.18.220/tests/38#" class="external">http://10.67.18.220/tests/38#</a>.</p>
<p>Can any expert on this help to confirm whether we use it the correct way? </p>
<p>Job details:</p>
<pre><code>Test order:
login_console -> fail_moduleA -> fail_moduleB
fail_moduleA main code:
sub run {
type_string("echo start fail_moduleA.pm\n");
die "die on purpose to check if test continue to next module";
}
sub post_fail_hook {
#force_soft_failure("let test continue...");
type_string("post_fail_hook DONE");
save_screenshot;
}
sub test_flags {
return {fatal => 0};
But B was not started after A fail.
</code></pre> 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 Infrastructure - action #55757 (Resolved): OSD ftp service has problem: NFS mount on qanet...https://progress.opensuse.org/issues/557572019-08-20T10:21:33Zxlaixlai@suse.com
<p>From around 4 hours ago, pxe installation on osd always fail at boot_from_pxe with error "Could not find kernel image xxx", <a href="https://openqa.suse.de/tests/3270212#step/boot_from_pxe/6" class="external">https://openqa.suse.de/tests/3270212#step/boot_from_pxe/6</a>.</p>
<p>We tested ftp service, it is not accessible for images, but http works well.</p>
<p>Please help recover. It blocks virtualization test for beta4 candidate.</p>
<a name="Log"></a>
<h1 >Log:<a href="#Log" class="wiki-anchor">¶</a></h1>
<p>FTP STATUS:<br>
'wget <a href="ftp://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux" class="external">ftp://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux</a><br>
--2019-08-20 06:15:32-- <a href="ftp://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux" class="external">ftp://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux</a><br>
=> ‘linux.1’<br>
Resolving openqa.suse.de (openqa.suse.de)... 10.160.0.207, 2620:113:80c0:8080:10:160:0:207 <br>
Connecting to openqa.suse.de (openqa.suse.de)|10.160.0.207|:21... connected. <br>
Logging in as anonymous ... Logged in!<br>
==> SYST ... done. ==> PWD ... done.<br>
==> TYPE I ... done. ==> CWD (1) /assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader ...<br>
No such directory ‘assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader’. <br>
'<br>
HTTP:<br>
'wget <a href="http://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux" class="external">http://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux</a><br>
--2019-08-20 06:16:35-- <a href="http://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux" class="external">http://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux</a><br>
Resolving openqa.suse.de (openqa.suse.de)... 10.160.0.207, 2620:113:80c0:8080:10:160:0:207 <br>
Connecting to openqa.suse.de (openqa.suse.de)|10.160.0.207|:80... connected. <br>
HTTP request sent, awaiting response... 200 OK<br>
Length: 6856480 (6.5M)<br>
Saving to: ‘linux.1’</p>
<p>100%[===============================================================>] 6,856,480 --.-K/s in 0.08s </p>
<p>2019-08-20 06:16:35 (80.0 MB/s) - ‘linux.1’ saved [6856480/6856480]<br>
'</p>
<p>'# curl <a href="ftp://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux" class="external">ftp://openqa.suse.de/assets/repo/fixed/SLE-12-SP4-Server-DVD-x86_64-GM-DVD1/boot/x86_64/loader/linux</a><br>
curl: (9) Server denied you to change to the given directory<br>
'</p>
openQA Infrastructure - action #54263 (Resolved): Please help to setup ipmi on openqaw5-xen.qa.su...https://progress.opensuse.org/issues/542632019-07-15T10:09:58Zxlaixlai@suse.com
<p>Hello,</p>
<p>This machine is for virtualization QA test in openqa. Please help to setup ipmi connection on it for remote control from beijing. Detailed info in <a href="https://racktables.nue.suse.com/index.php?page=object&tab=default&object_id=3468" class="external">https://racktables.nue.suse.com/index.php?page=object&tab=default&object_id=3468</a>.</p>
<p>Thank you in advance!</p>
openQA Infrastructure - action #44228 (Resolved): Need to deploy SLE12SP4 GM x86_64 repo to http:...https://progress.opensuse.org/issues/442282018-11-22T08:17:03Zxlaixlai@suse.com
<p>In SLE15SP1 test plan, virtualization will cover tests on sle12sp4 GM host. So like before, can anyone help to make it under <a href="http://openqa.suse.de/assets/repo/fixed/" class="external">http://openqa.suse.de/assets/repo/fixed/</a>, like other sle12sp3 or sle15 GM setup?</p>
openQA Infrastructure - action #43874 (Resolved): HDD in kermit.qa.suse.de has problems in combin...https://progress.opensuse.org/issues/438742018-11-16T08:12:55Zxlaixlai@suse.com
<p>OpenQA worker openqaworker2:23 relevant SUT, configuration:<br>
"IPMI_HOSTNAME" : "sp.kermit.qa.suse.de",<br>
"IPMI_PASSWORD" : "ADMIN",<br>
"IPMI_USER" : "ADMIN",</p>
<p>mkfs and fdisk operations on this disk fails (on sle12sp3 /15sp1 system), showing error of writing superblocks.</p>
<p>Please help to 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 Project - action #38522 (Resolved): Updating Job Group default priority does not have effe...https://progress.opensuse.org/issues/385222018-07-18T10:11:19Zxlaixlai@suse.com
<p>In virtualization-acceptance job group in sle12sp4, change the default priority from 50 to 30, but the tests still show priority as 50, and also after I retrigger the job via "client isos post", the priority of job is still 50.</p>
<p>I tried to readd the tests after setting default priority of that group to 30 suggested by sergio(this way worked for him), but the added test still shows old priority 50.</p>
<p>BTW, we need to evaluate the run time for this job group during beta1 with priority 30, can anyone help to change the priority if you can by anyway?</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 #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 #19744 (Resolved): Guest installation on sles12sp3 kvm fails due to not get...https://progress.opensuse.org/issues/197442017-06-12T05:17:21Zxlaixlai@suse.com
<p>Job link <a href="https://openqa.suse.de/tests/991716" class="external">https://openqa.suse.de/tests/991716</a>, key error screen <a href="https://openqa.suse.de/tests/991716#step/update_package/12" class="external">https://openqa.suse.de/tests/991716#step/update_package/12</a></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 #13914 (New): [qe-core][functional][ipmi] wait_serial does not get expected...https://progress.opensuse.org/issues/139142016-09-27T01:36:22Zxlaixlai@suse.com
<p>Test failed due to wait_serial does not get output. From serial0.txt, the ipmi session was already closed due to "excess errors received"</p>
<p>Failure step:<br>
<a href="https://openqa.suse.de/tests/587781#step/install_package/4" class="external">https://openqa.suse.de/tests/587781#step/install_package/4</a></p>
<p>Build link:<br>
<a href="https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2141&groupid=46" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=2141&groupid=46</a></p>
<p>Serial output link:<br>
<a href="https://openqa.suse.de/tests/587781/file/serial0.txt" class="external">https://openqa.suse.de/tests/587781/file/serial0.txt</a></p>
<p>Key serial output errors:</p>
<pre><code>[�[0;32m OK �[0m] Started Serial Getty on ttyS1.
[�[0;32m OK �[0m] Started Serial Getty on hvc0.
Starting X Display Manager...
[�[0;32m OK �[0m] Started Getty on tty1.
[�[0;32m OK �[0m] Reached target Login Prompts.
[�[0;32m OK �[0m] Started /etc/init.d/after.local Compatibility.
[�[0;32m OK �[0m] Started Load dom0 backend drivers.
Starting The Xen xenstore...
[SOL established]
[error received]: excess errors received
[closing the connection]
</code></pre>