openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-01-20T08:58:37ZopenSUSE Project Management Tool
Redmine openQA Tests - action #62339 (Rejected): [kernel][ltp] <syscall> slept too long failures in VMshttps://progress.opensuse.org/issues/623392020-01-20T08:58:37Zrpalethorperichard.palethorpe@suse.com
<p>Sometimes timing tests fail with this, especially on ARM. As we are running the tests in VMs on hosts with lots of contention, this is most likely caused by the environment.</p>
openQA Tests - action #19152 (Resolved): [aarch64] handle_uefi_boot_disk_workaround should use AR...https://progress.opensuse.org/issues/191522017-05-12T12:23:03Zrpalethorperichard.palethorpe@suse.com
<p>tests with aarch64-virtio set as the machine can not boot: <a href="https://openqa.suse.de/tests/932275#" class="external">https://openqa.suse.de/tests/932275#</a></p>
<p>probably because of openqabasetest.pm line ~317.</p>
openQA Tests - action #18674 (Resolved): [ltp][openqa] Remove or replace pidstat stuff in install...https://progress.opensuse.org/issues/186742017-04-20T09:46:41Zrpalethorperichard.palethorpe@suse.com
<p>It broke. So , replace with "script_run('(pidstat -p ALL 1 > ... &)'" and "script_run('kill $(ps -C pidstat -o pid --no-headers)'";</p>
<pre><code> ^
/ \
(0.o)
\____|____/
|
#
/
/ \
/ |
d h
</code></pre> openQA Tests - action #16424 (Rejected): [openqa] main.pm is too oldhttps://progress.opensuse.org/issues/164242017-02-02T16:13:07Zrpalethorperichard.palethorpe@suse.com
<p>If main.pm is not updated then some tests are not scheduled correctly and may fail or run the wrong test.</p>
openQA Tests - action #15700 (Rejected): [LTP][OpenQA] ima,tpm: need TPMhttps://progress.opensuse.org/issues/157002016-12-30T10:26:11Zrpalethorperichard.palethorpe@suse.com
<p>These tests require a Trusted Platform Module which is not currently available inside our SUT's VM. At a cursory glance, there are a few options for solving this, including, but probably not limited to:</p>
<ol>
<li>Pass-through the host's TPM module to the guest.</li>
<li>Emulate the TPM using <a href="https://github.com/PeterHuewe/tpm-emulator" class="external">https://github.com/PeterHuewe/tpm-emulator</a> either on the guest or host.</li>
<li>Wait for QEMU TPM device emulation.</li>
</ol>
<p>In the case of option 1 we need to use the Linux vTPM proxy driver to ensure the guest doesn't take exclusive control of the TPM. This requires reconfiguring the host/worker's kernel to build the vtpmx module.</p>
<p>The second seems quite flexible, although we will need to package the emulator to run it on workers. There also appears to be an emulator built into QEMU in the works which would be easiest to configure.</p>
openQA Tests - action #15678 (Resolved): [LTP][OpenQA] misc: acpi_test_dev_callback failshttps://progress.opensuse.org/issues/156782016-12-29T09:16:53Zrpalethorperichard.palethorpe@suse.com
<p>The ltp_acpi tests fails when running a test inside the ltp_acpi_cmds kernel module called acpi_test_dev_callback.</p>
<p><a href="https://openqa.suse.de/tests/686455#step/run_ltp/45" class="external">https://openqa.suse.de/tests/686455#step/run_ltp/45</a></p>
openQA Tests - action #15668 (Resolved): [kernel][LTP][OpenQA] hyperthreading ht_interrupt won't runhttps://progress.opensuse.org/issues/156682016-12-28T15:53:28Zrpalethorperichard.palethorpe@suse.com
<p>Test fails with TCONF claiming system does not have HT enabled. However the CPU has the HT flag and shows 8 processors configured on a 4 core CPU.</p>
<p>The file <code>/testcases/kernel/sched/hyperthreading/ht_interrupt/ht_utils.c</code> (AFAICT) checks the <code>/proc/cpuinfo</code> file for the number of logical processors vs the number sockets/cores/threads and also looks for a line starting with <code>cpu_package</code>. If it finds <code>cpu_package</code> then it assumes that this is a Hyperthreading kernel. No such line is present on my system.</p>
<p>The other tests in the HT runfile, smt_smp_enable and smt_smp_affinity, run and pass, they have their own copies of <code>ht_utils.c</code> which are different.</p>
openQA Tests - action #15652 (Closed): [LTP][OpenQA] commands: mkfs.ntfs missinghttps://progress.opensuse.org/issues/156522016-12-27T11:26:45Zrpalethorperichard.palethorpe@suse.com
<p>The ntfsprogs package appears to be missing in SLES 12 onwards. It exists in OpenSUSE, so we could at least run the tests there, but then we start on the path of installing different sets of packages in SLES and OpenSUSE. Furthermore I am not sure that we care about NTFS support.</p>
openQA Tests - action #15626 (Resolved): [LTP][OpenQA] commands: du -a test failshttps://progress.opensuse.org/issues/156262016-12-22T12:46:21Zrpalethorperichard.palethorpe@suse.com
<p><a href="https://openqa.suse.de/tests/686450#step/run_ltp/111" class="external">https://openqa.suse.de/tests/686450#step/run_ltp/111</a></p>
openQA Tests - action #15624 (Resolved): [LTP][OpenQA] sssd: sss_* commands not foundhttps://progress.opensuse.org/issues/156242016-12-22T12:42:05Zrpalethorperichard.palethorpe@suse.com
<p>It seems that SUSE does not have commands (they are not in sssd-tools) such as sss_useradd. We probably just use regular <code>useradd</code> with the correct PAM modules configured.</p>
openQA Tests - action #15622 (Resolved): [LTP][OpenQA] commands: mail test claims mail fail is no...https://progress.opensuse.org/issues/156222016-12-22T12:36:35Zrpalethorperichard.palethorpe@suse.com
<p><a href="https://openqa.suse.de/tests/686450#step/run_ltp/56" class="external">https://openqa.suse.de/tests/686450#step/run_ltp/56</a></p>
<p><a href="https://openqa.suse.de/tests/latest?flavor=Server-DVD&distri=sle&machine=64bit&test=ltp_commands&version=12-SP3&arch=x86_64" class="external">latest</a></p>
openQA Tests - action #15620 (Rejected): [LTP][OpenQA] Crontab activity not foundhttps://progress.opensuse.org/issues/156202016-12-22T12:17:18Zrpalethorperichard.palethorpe@suse.com
<p>cron_tests.sh checks /var/log/messages and /var/log/cron for crontab activity, but neither file exists on newer systems. The test should probably try using <code>journalctl</code> as well.</p>
openQA Tests - action #15592 (Resolved): [LTP][OpenQA][kernel] LTP Native test runner minor issueshttps://progress.opensuse.org/issues/155922016-12-20T16:06:45Zrpalethorperichard.palethorpe@suse.com
<p>This is an unsorted and unverified list of issues I have identified from running most of the LTP tests on openqa.suse.de</p>
<ul>
<li>[ ] aiodio no junkfile</li>
<li>[ ] cap bounds; fail to exec check_pe</li>
<li>[ ] commands; no crontab activity</li>
<li>[ ] commands; no fail mail</li>
<li>[ ] commands: sssd-lib.sh missing</li>
<li>[ ] commands: du -a failed</li>
<li>[ ] commands; ntfs not found</li>
<li>[ ] controllers; cgroup fail</li>
<li>[ ] controllers; mem+swap not enabled</li>
<li>[ ] controllers; memcg fail</li>
<li>[ ] controllers; subsystem debug not supported</li>
<li>[ ] controllers; 'controllers' test broken</li>
<li>[ ] cpuhotplug support</li>
<li>[ ] random timeouts where serial terminal I/O appears to cease with no error</li>
<li>[ ] ext4, readonly; need big block device</li>
<li>[ ] hyperthreading; supported?</li>
<li>[ ] ima; broken?</li>
<li>[ ] misc; need kernel modules</li>
<li>[ ] misc; acpi broken?</li>
<li>[ ] lvm; unable to make ~/test/growfiles/msdos~ directory</li>
<li>[ ] mm; need more swap space</li>
<li>[ ] numa; broken test?</li>
<li>[ ] rpc; broken tests?</li>
<li>[ ] smack; needs ~/smack~</li>
<li>[ ] syscalls; movepages needs NUMA</li>
<li>[ ] syscalls_ipc; duplicates syscalls?</li>
<li>[ ] msgctl10; fork failed (too ambitious?)</li>
<li>[ ] tirpc; tests broken?</li>
<li>[ ] tpm_tools; commands are missing</li>
<li>[ ] tpm_tools; virtual or physical TPM required</li>
<li>[ ] ensure all non-duplicate, non-networking runtest files are being used</li>
<li>[ ] transfer test configurations to openSUSE</li>
</ul>
<p>Some issues are probably upstream problems and others may be large or hard enough to deserve their own issue entry and proper scrutiny. I will try to fix the easiest ones first and get a better idea of what is required.</p>
openQA Tests - action #15492 (Resolved): Upgrade ppc64le workers to QEMU 2.6.*, i.e. current Leap...https://progress.opensuse.org/issues/154922016-12-14T11:06:38Zrpalethorperichard.palethorpe@suse.com
<a name="observation"></a>
<h2 >observation<a href="#observation" class="wiki-anchor">¶</a></h2>
<p>This job (<a href="https://openqa.suse.de/tests/668033/file/autoinst-log.txt" class="external">https://openqa.suse.de/tests/668033/file/autoinst-log.txt</a>) fails because the logfile parameter is not available in the installed version of QEMU on the worker.</p>
<a name="problem"></a>
<h2 >problem<a href="#problem" class="wiki-anchor">¶</a></h2>
<p>Upgrading the QEMU version on the worker will fix this. But for this we would need to update e.g. malbec.arch from SLES 12 SP1 to a more recent version which no one did, maybe for good reasons.</p>
<a name="workaround"></a>
<h2 >workaround<a href="#workaround" class="wiki-anchor">¶</a></h2>
<p>The virtio-console is optional in os-autoinst and is only enabled if the job states 'VIRTIO_CONSOLE=1'. As a workaround disable this setting.</p>
openQA Tests - action #13140 (Resolved): Job template organizationhttps://progress.opensuse.org/issues/131402016-08-10T13:59:43Zrpalethorperichard.palethorpe@suse.com
<p>I find the products/opensuse/templates file to big and painful to deal with. Perhaps a templates sub-directory should be created, which we then insert template files into just containing test suits, machines, job groups etc. which are tightly related.</p>
<p>That way someone can view all the information relating to these tests on one or two pages and import the tests without worrying if anything unexpected is going to be added. If someone needs to add all the templates at once then they can write something like ./load_templates templates/*.</p>
<p>Templates provide a way of recording how a machine or test suit should be used, in a transportable and human readable format, but one huge monolithic file is only useful for automated export-import. I used this template during my local installation by following the instructions, but the number of tests it has added was counter productive when trying to learn the system. If new users want to see a complex setup they can look no further than openqa.suse.de.</p>