openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-08-29T09:20:02ZopenSUSE Project Management Tool
Redmine openQA Tests - action #40397 (Resolved): [qam][caasp] needle for velum UI changehttps://progress.opensuse.org/issues/403972018-08-29T09:20:02Zpgeorgiadispgeorgiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario caasp-3.0-CaaSP-DVD-Incidents-x86_64-QAM-CaaSP3-controller@qam-caasp_x86_64 fails in<br>
<a href="https://openqa.suse.de/tests/2008717/modules/stack_update/steps/25" class="external">stack_update</a></p>
<p>This update includes the new image for velum. In this image, there is a significant change in the user interface. This conflicts with one of our needles, thus our needle needs to be update. However, the previous needle should not be removed because we keep maintaining v2 and v3. This change is only for v3.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/2007881" class="external">:8493:velum.1535465206</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/2007873" class="external">:8402:qemu.1535462638</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?machine=qam-caasp_x86_64&version=3.0&distri=caasp&flavor=CaaSP-DVD-Incidents&arch=x86_64&test=QAM-CaaSP3-controller" class="external">latest</a></p>
openQA Tests - action #38021 (Resolved): [qam][caasp] Write test for new packagehttps://progress.opensuse.org/issues/380212018-06-29T08:33:00Zpgeorgiadispgeorgiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario caasp-2.0-CaaSP-DVD-Incidents-x86_64-QAM-CaaSP-controller@qam-caasp_x86_64 fails in<br>
<a href="https://openqa.suse.de/tests/1793182/modules/stack_update/steps/13" class="external">stack_update</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/1793182" class="external">:7858:caasp-tools.1530190287</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/1793174" class="external">:7588:biosdevname.1530189763</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?test=QAM-CaaSP-controller&distri=caasp&flavor=CaaSP-DVD-Incidents&arch=x86_64&machine=qam-caasp_x86_64&version=2.0" class="external">latest</a></p>
<p>In this scenario a NEW pkg got introduced. We have no mechanism to install this package in openQA yet. Let's discuss and think about how this can be handled.</p>
openQA Tests - action #37282 (Resolved): [qam][sle] Add docker-init and manpagehttps://progress.opensuse.org/issues/372822018-06-13T09:17:29Zpgeorgiadispgeorgiadis@suse.com
<p><a href="https://build.suse.de/request/show/166497" class="external">https://build.suse.de/request/show/166497</a> got released.</p>
<p>Please add/write two new test cases for the following bugs:</p>
<pre><code>* bsc#1085117 (man pages for individual docker CLI commands missing)
* bsc#1091633 ([TRACKERBUG] ECO#324652: [ECO] [MODULE] Add docker-init to the containers module)
</code></pre>
<p>e.g. extracted from Pavel's testreport:</p>
<pre><code>Before:
$ man docker build # works
$ man docker config # missing
After:
$ man docker build # works
$ man docker config # works
After:
# docker run --rm -it opensuse/tumbleweed bash
df94d595b715:/ # ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.3 0.1 16588 5852 pts/0 Ss 08:35 0:00 bash
root 19 0.0 0.0 30076 3120 pts/0 R+ 08:35 0:00 ps aux
df94d595b715:/ # exit
# docker run --rm -it --init opensuse/tumbleweed bash
88f58f80d00e:/ # ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 1048 4 pts/0 Ss 08:35 0:00 /dev/init -- bash
root 7 0.0 0.1 16588 5900 pts/0 S 08:35 0:00 bash
root 21 0.0 0.0 30076 3108 pts/0 R+ 08:35 0:00 ps aux
88f58f80d00e:/ # exit
</code></pre> openQA Tests - action #36964 (Resolved): [QAM][CAASP] docker engine doesn't have seccomp supporthttps://progress.opensuse.org/issues/369642018-06-07T14:27:39Zpgeorgiadispgeorgiadis@suse.com
<p>Add a new check as requested by the devs at <a href="https://bugzilla.suse.com/show_bug.cgi?id=1072367" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1072367</a></p>
openQA Tests - action #36319 (Resolved): [QAM][CAASP] Use salt grains to let Velum orchestrate th...https://progress.opensuse.org/issues/363192018-05-17T09:34:22Zpgeorgiadispgeorgiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Right now we manually trigger the update of the cluster using system.reboot state in Salt. This is not the right way to do it. We have to use the transactional-update salt pkg install and then take it from Velum.</p>
<p>e.g.</p>
<pre><code>1. Log in to admin node
2. Install the package like this:
docker exec -i $(docker ps | grep salt-master | awk '{print $1}') salt --batch 20 -P "roles:(admin|kube-(master|minion))" cmd.run "/usr/sbin/transactional-update salt pkg install -y $pkg"
3. Wait 10 minutes or refresh the grains right away:
docker exec -i $(docker ps | grep salt-master | awk '{print $1}') salt --batch 20 '*' saltutil.refresh_grains
4. Open Firefox and go to Velum and the rest are the same.
</code></pre>
<p>openQA test in scenario caasp-2.0-CaaSP-DVD-Incidents-x86_64-QAM-CaaSP-controller@qam-caasp_x86_64 fails in<br>
<a href="https://openqa.suse.de/tests/1689669/modules/stack_update/steps/27" class="external">stack_update</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/1689669" class="external">:7156:hyper-v.1526320658</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/1688652" class="external">:7413:kernel-ec2.1526451388</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?test=QAM-CaaSP-controller&distri=caasp&machine=qam-caasp_x86_64&arch=x86_64&version=2.0&flavor=CaaSP-DVD-Incidents" class="external">latest</a></p>
openQA Tests - action #36258 (Resolved): [QAM][CAASP] kubectl get failshttps://progress.opensuse.org/issues/362582018-05-16T08:51:41Zpgeorgiadispgeorgiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>This is happening ~once per 2 weeks. I don't know what's wrong since DEX is up and running. I would say, let's try to fix this by issuing the command again. If it fails 10 times in a row, then we can file a product bug.</p>
<p>openQA test in scenario caasp-2.0-CaaSP-DVD-Incidents-x86_64-QAM-CaaSP-controller@qam-caasp_x86_64 fails in<br>
<a href="https://openqa.suse.de/tests/1687332/modules/stack_kubernetes/steps/10" class="external">stack_kubernetes</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/1687332" class="external">:7219:bash.1526391680</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/1687311" class="external">:7191:icu.1526390919</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?flavor=CaaSP-DVD-Incidents&version=2.0&machine=qam-caasp_x86_64&arch=x86_64&distri=caasp&test=QAM-CaaSP-controller" class="external">latest</a></p>
openQA Tests - action #36154 (Resolved): [kubic] Add new test for kubeadmhttps://progress.opensuse.org/issues/361542018-05-14T12:33:37Zpgeorgiadispgeorgiadis@suse.com
<p>Kubeadm is the official upstream tools for bootstraping and managing kubernetes. So let's add a test for it in openQA.</p>
<p>PR has been sent: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5045" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5045</a><br>
Please review and provide feedback :)</p>
openQA Tests - action #35577 (Resolved): [QAM][CaaSP]Conformance k8s testsuite is failinghttps://progress.opensuse.org/issues/355772018-04-26T08:41:20Zpgeorgiadispgeorgiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario caasp-2.0-CaaSP-DVD-Incidents-x86_64-QAM-CaaSP-controller@qam-caasp_x86_64 fails in<br>
<a href="https://openqa.suse.de/tests/1644564/modules/stack_conformance/steps/117" class="external">stack_conformance</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/1640706" class="external">:7141:salt.1524508021</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/1640083" class="external">:7191:icu.1524491488</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?flavor=CaaSP-DVD-Incidents&test=QAM-CaaSP-controller&machine=qam-caasp_x86_64&version=2.0&arch=x86_64&distri=caasp" class="external">latest</a></p>
<p>We are running v.1.10.0 tests while we have v.1.8.9 version of k8s in CaaSP. According to mjura v.1.10.0 is working with 1.10 and 1.9 --- not 1.8.9. We have to point to the correct manifest file that works with 1.8.9.</p>
openQA Tests - action #34900 (Closed): [qam][sle15] Port Kubic container testshttps://progress.opensuse.org/issues/349002018-04-13T10:13:25Zpgeorgiadispgeorgiadis@suse.com
<p>Let's port some container tests :D</p>
<p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4733#discussion_r180353922" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4733#discussion_r180353922</a></p>
openQA Tests - action #34834 (Resolved): [QAM][CAASP] Enable single-master clusterhttps://progress.opensuse.org/issues/348342018-04-12T14:05:39Zpgeorgiadispgeorgiadis@suse.com
<p>We need to enable another scenario in CaaSP in QAM, one that requires only the minimum requirements to setup your cluster (thus less resources). This is going to be used in production, after <a href="https://fate.suse.com/325564" class="external">https://fate.suse.com/325564</a>. In the meantime, as soon as this PR gets merged, you need the following configuration in your openQA Instance (if you don't want to wait until the FATE request) :</p>
<p>Go to '<a href="https://pes.suse.de/QA_Maintenance/caasp/" class="external">https://pes.suse.de/QA_Maintenance/caasp/</a>' and read 'Setup for CaaSP single-master' section</p>
openQA Tests - action #34540 (Resolved): [QAM][CAASP] Add --flatten=truehttps://progress.opensuse.org/issues/345402018-04-09T11:42:00Zpgeorgiadispgeorgiadis@suse.com
<p>We have noticed in openQA for CaaSP v2.0 that the CA Certificate is 'REDACTED' (see bug: <a href="https://bugzilla.suse.com/show_bug.cgi?id=1088620" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1088620</a>). After discussion in #docker channel, we were advised to enhance the test, by adding '--flatten=true' in order to reveal more information.</p>
openQA Tests - action #33397 (Resolved): [QAM][CAASP] qw doesn't interpolate $nodehttps://progress.opensuse.org/issues/333972018-03-17T02:59:46Zpgeorgiadispgeorgiadis@suse.com
<p>Look: <a href="https://openqa.suse.de/tests/1550955#step/stack_update/16" class="external">https://openqa.suse.de/tests/1550955#step/stack_update/16</a></p>
<p>In this update, the meltdown bug get's fixed. As you can see from the logs, it checks only for one needle: the one with the bug:</p>
<p>[2018-03-16T20:23:42.0223 CET] [debug] >>> testapi::_check_backend_response: match=velum-$nodes-nodes-outdated,velum-sorry timed out after 300</p>
<p>This is happening because in Perl the qw doesn't interpolate:</p>
<p>assert_screen [qw(velum-$nodes-nodes-outdated velum-sorry)], 300;</p>
<p>this means 'velum-$nodes-nodes-outdated' == 'velum-$nodes-nodes-outdated'</p>
openQA Tests - action #33391 (Resolved): [QAM][CAASP] Workaround for bnc#1085677https://progress.opensuse.org/issues/333912018-03-16T15:05:25Zpgeorgiadispgeorgiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario caasp-2.0-CaaSP-DVD-Incidents-x86_64-QAM-CaaSP-controller@qam-caasp_x86_64 fails in<br>
<a href="https://openqa.suse.de/tests/1547985/modules/stack_update/steps/9" class="external">stack_update</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/1547985" class="external">:6868:grub2.1521115306</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/1547863" class="external">:6812:rdma-core.1521115525</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?machine=qam-caasp_x86_64&arch=x86_64&test=QAM-CaaSP-controller&flavor=CaaSP-DVD-Incidents&distri=caasp&version=2.0" class="external">latest</a></p>
<p>While this is filed as bug, at the same time openQA should mark this as a soft-fail and continue/proceed with testing. To do that, I assume we need to wait a little bit longer until the 'UPDATE ADMIN NODE' button appears on the screen. So, let's increase the timeout for this one.</p>
openQA Tests - action #33385 (Resolved): [QAM][CAASP] Fix the k8s conformance test to parse new o...https://progress.opensuse.org/issues/333852018-03-16T13:10:31Zpgeorgiadispgeorgiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario caasp-2.0-CaaSP-DVD-Incidents-x86_64-QAM-CaaSP-controller@qam-caasp_x86_64 fails in<br>
<a href="https://openqa.suse.de/tests/1548357/modules/stack_conformance/steps/109" class="external">stack_conformance</a></p>
<p>Sometimes the tests require more than 1.30 hour. This happened quite a few times now:<br>
e.g. <a href="https://openqa.suse.de/tests/1550131" class="external">https://openqa.suse.de/tests/1550131</a><br>
e.g. <a href="https://openqa.suse.de/tests/1550285" class="external">https://openqa.suse.de/tests/1550285</a> , etc</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/1547985" class="external">:6868:grub2.1521115306</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/1547863" class="external">:6812:rdma-core.1521115525</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?distri=caasp&version=2.0&arch=x86_64&machine=qam-caasp_x86_64&flavor=CaaSP-DVD-Incidents&test=QAM-CaaSP-controller" class="external">latest</a></p>
<p>My solution is to increase the timeout from 90 minutes up to 120 minutes.<br>
This will not delay any test without any reason, simply because if the test finishes earlier, it will exit the loop ;)</p>
openQA Tests - action #32368 (Resolved): [QAM][CaaSP] Enable kubernetes e2e testshttps://progress.opensuse.org/issues/323682018-02-27T10:36:34Zpgeorgiadispgeorgiadis@suse.com
<p>We need to maintainer the status of CaaSP being certified under CNCF Kubernetes certification.<br>
See: <a href="https://www.suse.com/communities/blog/suse-caas-platform-2-certified-kubernetes-conformance-software-certification/" class="external">https://www.suse.com/communities/blog/suse-caas-platform-2-certified-kubernetes-conformance-software-certification/</a><br>
and: <a href="https://www.cncf.io/announcement/2017/11/13/cloud-native-computing-foundation-launches-certified-kubernetes-program-32-conformant-distributions-platforms/" class="external">https://www.cncf.io/announcement/2017/11/13/cloud-native-computing-foundation-launches-certified-kubernetes-program-32-conformant-distributions-platforms/</a></p>
<p>In case a maintenance update break this, it's very difficult for the maintainer to find out which one cause the problem and fix it later.<br>
Also, this is how other companies verify their good status of kubernetes, so we need to do the same.</p>