openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-05-24T11:03:29ZopenSUSE Project Management Tool
Redmine qe-yam - action #93032 (Closed): Use accept_license module with libyui-rest-api in all test suite...https://progress.opensuse.org/issues/930322021-05-24T11:03:29Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>There is <code>accept_license</code> module, implemented with LibyuiClient already: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm</a>. It is already used in <a href="https://openqa.suse.de/tests/5951331" class="external">installer_extended</a> test suite. </p>
<a name="Scope"></a>
<h2 >Scope:<a href="#Scope" class="wiki-anchor">¶</a></h2>
<p>Job Groups: YaST, openSUSE Tumbleweed, openSUSE Leap 15<br>
Test Cases: #1 - Accept license agreement (Please, see test cases in <a href="https://progress.opensuse.org/issues/93282" class="external">https://progress.opensuse.org/issues/93282</a>).</p>
<a name="Task"></a>
<h2 >Task<a href="#Task" class="wiki-anchor">¶</a></h2>
<ol>
<li>Replace the old <code>accept_license</code> module with the new <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">accept_license</a> module in all the test suites for SLE15-SP3 YaST Job Group;</li>
<li>Adapt existing implementation to be used on Tumbleweed and openSUSE Leap 15 also (i.e. use DistributionFactory to provide the proper controller for TW and Leap, so that the test module remains same, but implementation of <code>get_license_agreement()->accept_license()</code> is different), as on TW and Leap there is no checkbox for accepting License.</li>
<li>Replace the old <code>accept_license</code> module with the new <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">accept_license</a> module in all the test suites for Tumbleweed and openSUSE Leap 15. </li>
</ol>
<p><strong>Important Notes:</strong><br>
All the cases that do not related to accepting license are out of scope:</p>
<ul>
<li><code>switch_keyboard_gnome/textmode</code> is out of scope and will be implemented in separate ticket, so for now please leave the old 'welcome' module there for such cases;</li>
<li>Product Selection Screen is out of scope, it will be implemented in separate ticket.</li>
</ul>
<p>The new module should replace the old "accept_license" used in SLE, and "welcome" module used in opensuse. It should work for both textmode and graphical installations. Please see identified scenarios in <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="action: [timeboxed:16h] Define all the test scenarios in welcome and accept_license test modules (Closed)" href="https://progress.opensuse.org/issues/88939">#88939</a> as additional help.</p>
qe-yam - action #91136 (Rejected): Textmode test suite fails for s390x-kvmhttps://progress.opensuse.org/issues/911362021-04-14T13:20:42Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After implementing libyui for the mentioned tests, there is a strange network failure. The url that libyui is trying to connect to seems correct but the app doesn't connect successfully. The failure is the same for all machines:<br>
<a href="https://openqa.suse.de/tests/5814857#step/bootloader_start/30" class="external">https://openqa.suse.de/tests/5814857#step/bootloader_start/30</a> </p>
<p>Similar issue is visible on powerVM: <a class="issue tracker-4 status-5 priority-5 priority-high3 closed" title="action: [timeboxed:16h] libyui REST API cannot be accessed on powerVM (Closed)" href="https://progress.opensuse.org/issues/90776">#90776</a>, so might be that it's same issue for the both backends</p>
qe-yam - action #91130 (Closed): Use libyui for btrfs_libstorage-ng ipmi and zVMhttps://progress.opensuse.org/issues/911302021-04-14T13:15:03Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently we are using the old modules for the btrfs_libstorage-ng on the mentioned architectures. The libyui functionality shoudl be working after merging <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12298" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12298</a></p>
<p>For guided partitioning, there need to be additional steps implemented that will choose the disk(s) for the installation.<br>
Module tests/installation/partitioning/guided_setup.pm does not cover this option:<br>
<a href="https://openqa.suse.de/tests/5821208#step/guided_setup/2" class="external">https://openqa.suse.de/tests/5821208#step/guided_setup/2</a></p>
qe-yam - action #81248 (Rejected): test fails in snapshots_small_root on aarch64https://progress.opensuse.org/issues/812482020-12-21T13:42:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The warning for small root partition is successfully handled, but the cancellation of the partitioning is not taking effect, so the module is expecting for a second warning, related to losing changes, tries to press "yes" and receives the following error:</p>
<pre><code>Test died: Timed out:
Not Found
{ "error" : "Widget not found" }
http://localhost:39106/v1/widgets?action=press&id=yes at /var/lib/openqa/cache/openqa.suse.de/tests/sle/lib/YuiRestClient/Http/HttpClient.pm line 35.
</code></pre>
<p>Seems that the "cancel" button is not pressed.</p>
<p>openQA test in scenario sle-15-SP3-Online-aarch64-btrfs+warnings@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/5201644/modules/snapshots_small_root/steps/15" class="external">snapshots_small_root</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Test for feature with insufficient disk space on btrfs partition with snapshots.</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/5194534" class="external">109.1</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/5162094" class="external">102.1</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?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=btrfs%2Bwarnings&version=15-SP3" class="external">latest</a></p>
qe-yam - action #80220 (Rejected): test choses wrong product for installationhttps://progress.opensuse.org/issues/802202020-11-23T15:22:33Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>For full iso on x86_64 and ppc, the products have changed, so the shortcuts for product selection during "Welcome" page have also changed.</p>
<p>So far, the shortcuts are chosen based on the code:</p>
<pre><code>sub get_product_shortcuts {
# We got new products in SLE 15 SP1
if (is_sle '15-SP1+') {
return (
sles => (is_ppc64le() || is_s390x()) ? 'u'
: is_aarch64() ? 's'
: 'i',
sled => 'x',
sles4sap => is_ppc64le() ? 'i'
: (is_sle('15-SP2+') && is_x86_64()) ? 't'
: 'p',
hpc => is_x86_64() ? 'g' : 'u',
rt => is_x86_64() ? 't' : undef
);
}
</code></pre>
<p>openQA test in scenario sle-15-SP3-Full-ppc64le-textmode_installation_minimal_role@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/5057742/modules/welcome/steps/5" class="external">welcome</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/5032109" class="external">85.2</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/4964067" class="external">78.1</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?arch=ppc64le&distri=sle&flavor=Full&machine=ppc64le&test=textmode_installation_minimal_role&version=15-SP3" class="external">latest</a></p>
qe-yam - action #76888 (Closed): Unit test for yast2-metapackage-handler OneClickInstallWorkerFun...https://progress.opensuse.org/issues/768882020-11-02T19:12:01Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for OneClickInstallWorkerFunction.rb</p>
<p>InitSlideShow<br>
InstallPackages<br>
InstallPatterns<br>
RemovePackages</p>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
qe-yam - action #76885 (Resolved): Unit test for yast2-metapackage-handler OneClickInstallWorkerF...https://progress.opensuse.org/issues/768852020-11-02T19:10:38Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for <a href="https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstallWorkerFunctions.rb" class="external">OneClickInstallWorkerFunction.rb</a></p>
<p>DeDupe<br>
AddRepositories<br>
RemoveAddedRepositories</p>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
<p>See previous PRs for progress of unit testing coverage: <a href="https://github.com/yast/yast-metapackage-handler/pull/23" class="external">https://github.com/yast/yast-metapackage-handler/pull/23</a></p>
qe-yam - action #76879 (Resolved): Unit test for yast2-metapackage-handler OneClickInstall.rb (pa...https://progress.opensuse.org/issues/768792020-11-02T19:04:32Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for OneClickInstall.rb ( <a href="https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstall.rb" class="external">https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstall.rb</a> )</p>
<p>GetRequiredRepositories<br>
GetNonRequiredRepositories<br>
SetNonRequiredRepository<br>
SetRequiredRepositories<br>
GetRequiredSoftware<br>
GetRequiredPackages<br>
GetRequiredPatterns<br>
GetRequiredRemoveSoftware<br>
HaveAnyRecommended</p>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
qe-yam - action #73477 (Closed): Modify firstboot configuration for yast2_firstboot_customhttps://progress.opensuse.org/issues/734772020-10-18T12:46:33Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In order to extend coverage for yast2-firstboot, and given that we already have 2 test suites that verify the default configuration, we can modify yast2_firstboot_custom test suite. </p>
<p>Replace /etc/sysconfig/firstboot and /etc/YaST2/firstboot.xml files in order for the firstboot to:</p>
<ul>
<li>Display customized welcome message.</li>
<li>Display customized license.</li>
<li>Display customized finish text.</li>
<li>Set autologin checked by default for new user (in case we can change default value).</li>
<li>SHOW_Y2CC_CHECKBOX="yes", which enable yast2 control center after first boot configuration (this check is low prio and can be postponed as window cannot be easily closed)</li>
</ul>
<p>before proceeding to firstboot configuration, abort and reboot in order to verify that abort button doesn't cause crash and that firstboot will run again, if not completed.</p>
<p>Relevant bugs: <a href="https://bugzilla.suse.com/show_bug.cgi?id=1161048" class="external">bug#1161048</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1177797" class="external">bug#1177797</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1076798" class="external">bug#1076798</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=950335" class="external">bug#950335</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1173498" class="external">bug#1173498</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=615146" class="external">bug#615146</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1161045" class="external">bug#1161045</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1177757" class="external">bug#1177757</a></p>
qe-yam - action #73363 (Closed): sporadic failure for btrfs_libstorage-ng@64bit-ipmi https://progress.opensuse.org/issues/733632020-10-14T10:57:04Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The default partitioning proposal didn't include separate home partition, as was expected for a disk of 40GB. The particular failure happened only once so far for SLE 15 SP3 build.</p>
<p>We should check if this can be reproduced sporadically and add extra check in "tests/installation/partitioning_filesystem.pm" for separate home partition in order to stabilize the test suite.</p>
<p>As an alternative and/or addition, we can wipe disks before the test start, like we do for zVM and powerVM.</p>
<p>Note: <del>Not sure if related as the test suite disk setting for HDDSIZE is always 40GB.</del> (HDDSIZEGB is not effective on ipmi as those are bare metal machines). The ipmi workers have different size disks. The failure occurred when the test ran on worker grenache-1:10 and selected disk was /dev/sda 111.79 GB which is smaller related to other worker disks. On a previous run, on the same worker, selected disk was sdc :<br>
<a href="https://openqa.suse.de/tests/4788111#step/partitioning_filesystem/3" class="external">https://openqa.suse.de/tests/4788111#step/partitioning_filesystem/3</a></p>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-btrfs_libstorage-ng@64bit-ipmi fails in<br>
<a href="https://openqa.suse.de/tests/4816935/modules/verify_separate_home/steps/4" class="external">verify_separate_home</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Failed once Build <a href="https://openqa.suse.de/tests/4816935" class="external">57.4</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/4814794" class="external">57.4</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?arch=x86_64&distri=sle&flavor=Online&machine=64bit-ipmi&test=btrfs_libstorage-ng&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #67534 (Resolved): [functional][y] Change yast2_lan hostname validationhttps://progress.opensuse.org/issues/675342020-06-01T12:22:37Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In yast2_lan module, one of the steps is to verify that the hostname can be successfully changed. Currently in the code, the hostname used for the change comes from: <code>$hostname = get_var('HOSTNAME', 'susetest')</code> . For most architectures 'susetest' is also the hostname prior the change. So, in reality it doesn't verify if the hostname was changed ( <a href="https://openqa.suse.de/tests/4286250#step/yast2_lan/13" class="external">https://openqa.suse.de/tests/4286250#step/yast2_lan/13</a> ).</p>
<p>On some backends we cannot change hostname without breaking the setup (at least powerVM and zVM). So we might need to limit scope of test to qemu.</p>
<p>Running the module on xen hvm, where original hostname is not 'susetest', fails (<a href="https://openqa.suse.de/tests/4295089#step/yast2_lan/20" class="external">https://openqa.suse.de/tests/4295089#step/yast2_lan/20</a>).<br>
Running the module on x86, with different $hostname works (new needle needed for that to work) (<a href="http://falafel.suse.cz/tests/832#step/yast2_lan/23" class="external">http://falafel.suse.cz/tests/832#step/yast2_lan/23</a>).</p>
<p>Acceptance criteria:</p>
<ul>
<li>Change the code of yast2_lan so that the hostname after change is different than before.</li>
</ul>
qe-yam - action #67126 (Resolved): [functional][y] Add validation module for nis mm testshttps://progress.opensuse.org/issues/671262020-05-21T16:02:56Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In order to verify that "yast nis_server" and "yast nis" configuration on nis mm tests, works properly, a new module can be created for each test with following steps:</p>
<p>NIS server:<br>
(as root)</p>
<ul>
<li>useradd nis_user -> in the current test, /home/nis_user folder is created and shared via nfs, so in order to avoid extra steps, the user added should be "nis_user".</li>
<li>passwd nis_user</li>
<li>chmod nis_user:users /home/nis_user -> current owner of the folder is "root".</li>
<li>cd /var/yp </li>
<li>make -> nis database needs to be aware of the new user.</li>
<li>Check if /etc/defaultdomain and /etc/idmapd.conf contain the nis domain (nis.openqa.suse.de). At maps setup of nis_server module, all entries are selected. There can be a check in /var/yp/nis.openqa.suse.de/ if entries correspond</li>
</ul>
<p>NIS client:<br>
(after above actions on nis server are completed)</p>
<ul>
<li>ypcat passwd | grep nis_user / ypmatch nis_user passwd / getent passwd nis_user -> one option out of three, in order to verify that the client connection to nis server database is successful and new user is visible.</li>
<li>su - nis_user</li>
<li>pwd -> verify home directory of nis_user is /home/nis_user</li>
<li>echo "nis works"> file1 -> verify write </li>
<li>grep "nis works" -> verify read</li>
<li>Check if /etc/yp.conf exists and has the entry "ypserv"</li>
<li>Check if /etc/nsswitch.conf has expected entries e.g. "netgroup: files nis"</li>
<li>Check if /etc/defaultdomain contains the nis domain</li>
</ul>
<p>We should also extract settings to use same value for configuration and validation.</p>
openQA Tests - action #67117 (Resolved): [functional][y]test fails in yast2_proxy and yast2_dns_s...https://progress.opensuse.org/issues/671172020-05-21T12:03:55Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Online-x86_64-yast2_ncurses_gnome@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4264234/modules/yast2_proxy/steps/23" class="external">yast2_proxy</a></p>
<p>When needle <a href="https://openqa.suse.de/tests/4264234#step/yast2_proxy/9">https://openqa.suse.de/tests/4264234#step/yast2_proxy/9</a> is matched, the system should choose "Start", verify the selection and then proceed with rest of the module yast2_proxy steps. In the autoinst logs:</p>
<pre><code>[2020-05-21T07:14:41.839 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_after_writing_conf", timeout=1)
�[32m[2020-05-21T07:14:41.961 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_start_after_writing_conf-20180827, similarity 1.00 @ 336/320
�[0m[2020-05-21T07:14:41.961 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:77 called testapi::send_key
[2020-05-21T07:14:41.962 CEST] [debug] <<< testapi::send_key(key="alt-a", wait_screen_change=0, do_wait=0)
[2020-05-21T07:14:42.297 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:78 called testapi::send_key
[2020-05-21T07:14:42.297 CEST] [debug] <<< testapi::send_key(key="end", do_wait=0, wait_screen_change=0)
[2020-05-21T07:14:42.565 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:79 called testapi::send_key_until_needlematch
[2020-05-21T07:14:42.565 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_on_boot_after_reboot", timeout=1)
�[37m[2020-05-21T07:14:42.910 CEST] [debug] no match: 2.7s, best candidate: yast2_proxy-yast2_ncurses_service_start_on_boot_after_reboot-20180827 (0.29)
</code></pre>
<p>Looks like the sent keys don't have the expected effect on the test. The worker is looking for the next needle "yast2_ncurses_service_start_on_boot_after_reboot" without actually verifying "yast2_ncurses_service_check_start_after_writing_conf" needle. </p>
<p>In test <a href="https://openqa.suse.de/tests/4231081#step/yast2_proxy/10">https://openqa.suse.de/tests/4231081#step/yast2_proxy/10</a> , where the result is the expected one, the autoinst logs:</p>
<pre><code>[2020-05-13T19:17:44.759 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_after_writing_conf", timeout=1)
[2020-05-13T19:17:44.968 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_start_after_writing_conf-20180827, similarity 1.00 @ 336/320
[2020-05-13T19:17:44.968 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:55 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:81 called testapi::send_key
[2020-05-13T19:17:44.969 CEST] [debug] <<< testapi::send_key(key="ret", do_wait=0, wait_screen_change=0)
[2020-05-13T19:17:45.255 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:55 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:82 called testapi::assert_screen
[2020-05-13T19:17:45.256 CEST] [debug] <<< testapi::assert_screen(mustmatch="yast2_ncurses_service_check_start_after_writing_conf", timeout=30)
[2020-05-13T19:17:45.945 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_check_start_after_writing_conf-20180827, similarity 1.00 @ 454/289
[2020-05-13T19:17:45.945 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:77 called testapi::send_key
[2020-05-13T19:17:45.945 CEST] [debug] <<< testapi::send_key(key="alt-a", wait_screen_change=0, do_wait=0)
[2020-05-13T19:17:46.281 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:78 called testapi::send_key
[2020-05-13T19:17:46.282 CEST] [debug] <<< testapi::send_key(key="end", do_wait=0, wait_screen_change=0)
[2020-05-13T19:17:46.552 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:79 called testapi::send_key_until_needlematch
[2020-05-13T19:17:46.552 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_on_boot_after_reboot", timeout=1)
[2020-05-13T19:17:46.879 CEST] [debug] no match: 2.7s, best candidate: yast2_proxy-yast2_ncurses_service_start_on_boot_after_reboot-20180827 (0.29)
</code></pre>
<p>looks like after the first needle much, 'ret' should be sent instead of 'alt-a' and 'end' that would be expected after the matching "yast2_proxy-yast2_ncurses_service_check_start_after_writing_conf" .</p>
<p>The issue needs further investigation and possibly, follow up ticket with tools team.</p>
openQA Tests - action #64466 (Resolved): [functional][y][hyper-v][timeboxed:16h] test fails in sh...https://progress.opensuse.org/issues/644662020-03-12T13:14:17Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Sporadic failure in shutdown module. Two types of failures observed:</p>
<ul>
<li>Display at password prompt is distorted and cause needle match failure ( <a href="https://openqa.suse.de/tests/3969518#step/shutdown/10">https://openqa.suse.de/tests/3969518#step/shutdown/10</a> )</li>
<li>After password is entered, system doesn't show desktop. ( <a href="https://openqa.suse.de/tests/3982260#step/shutdown/15">https://openqa.suse.de/tests/3982260#step/shutdown/15</a> ). According to autoinst-log, provided password was incorrect and then system "Stopped target Current graphical user session."</li>
</ul>
<p>As per Yanis, it fails constantly on uefi. Seems that it's issues with openQA setup, as Yanis managed to shutdown the system and it worked just fine. So we need to identify the actions needed to fix it.</p>
<p>[ 675.237199] gnome-keyring-daemon[2603]: couldn't initialize slot with master password: The password or PIN is incorrect</p>
<p>[ 675.297939] gdm-password][4597]: gkr-pam: unlocked login keyring</p>
<p>[2020-03-12T12:29:22.895 CET] [debug] tests/shutdown/shutdown.pm:28 called power_action_utils::power_action -> lib/power_action_utils.pm:255 called testapi::select_console -> lib/susedistribution.pm:883 called x11utils::ensure_unlocked_desktop -> lib/x11utils.pm:126 called testapi::wait_still_screen<br>
[2020-03-12T12:29:22.895 CET] [debug] <<< testapi::wait_still_screen(similarity_level=47, timeout=30, stilltime=1)<br>
[ 675.471356] systemd[4428]: Stopped target Current graphical user session.</p>
<p>[ 675.803774] systemd[4428]: Stopped target GNOME X11 Session (session: gnome-login).</p>
<p>[ 675.914330] gdm-Xorg-:1[4408]: (II) event3 - Microsoft Vmbus HID-compliant Mouse: device removed</p>
<p>[ 675.994240] gdm-Xorg-:1[4408]: (II) event4 - Power Button: device removed</p>
<p>[ 676.108023] gdm-Xorg-:1[4408]: (II) event2 - AT Translated Set 2 keyboard: device removed</p>
<p>[ 676.167890] gdm-Xorg-:1[4408]: (II) event0 - AT Translated Set 2 keyboard: device removed</p>
<p>[ 676.223982] gdm-Xorg-:1[4408]: (II) event1 - TPPS/2 IBM TrackPoint: device removed</p>
<p>[ 676.276254] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.316927] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.358856] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.418850] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.487558] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.546600] gdm-Xorg-:1[4408]: (II) Server terminated successfully (0). Closing log file.</p>
<p>[ 676.648098] gnome-session[4457]: gnome-session-binary[4457]: WARNING: Lost name on bus: org.gnome.SessionManager</p>
<p>[ 676.732171] gdm-launch-environment][4424]: pam_unix(gdm-launch-environment:session): session closed for user gdm</p>
<p>[ 676.834667] systemd[4428]: Stopped target GNOME Session.</p>
<p>[ 676.908222] gnome-session[4457]: Unable to init server: Could not connect: Connection refused</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Full-x86_64-skip_registration@svirt-hyperv fails in<br>
<a href="https://openqa.suse.de/tests/3982260/modules/shutdown/steps/14" class="external">shutdown</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/3658083#step/shutdown/10" class="external">101.1</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/3978952" class="external">154.1</a></p>
openQA Tests - action #63814 (Resolved): [functional][y][virtualization][hyperv][timeboxed:12h] m...https://progress.opensuse.org/issues/638142020-02-25T12:24:34Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Even though same module works for other architectures, validate_fs_table cannot verify that partitions were successfully created.</p>
<p>The point of the code that fails is when the output of command "lsblk -n", split at every new line, is saved in @lsblk_output and it is parsed by:</p>
<p>foreach (@lsblk_output) {<br>
if ($_ =~ /(?\Q$args->{mount_point}\E\z)/) {<br>
$check = $+{check};<br>
last;<br>
}</p>
<p>On step <a href="https://openqa.suse.de/tests/3904536#step/validate_fs_table/14" class="external">https://openqa.suse.de/tests/3904536#step/validate_fs_table/14</a><br>
it is shown that the mount point "/" is indeed created, but it cannot be identified by "$_ =~ /(?\Q$args->{mount_point}\E\z)/".</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Online-x86_64-msdos@svirt-hyperv fails in<br>
<a href="https://openqa.suse.de/tests/3904536/modules/validate_fs_table/steps/16" class="external">validate_fs_table</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Always.</p>