openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-06-09T04:51:18ZopenSUSE Project Management Tool
Redmine qe-yam - action #130573 (New): Adapt base class for agama test to be more generichttps://progress.opensuse.org/issues/1305732023-06-09T04:51:18Zcoolgwwegao@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Current lib/yam/agama/agama_base.pm we use for auto-installation includes few things we don't need.<br>
We should update agama_base.pm to more generic base class which can be used by other modules such as patch_agama etc..</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Generilize agama_base and consider how or where to use the specific parts.</p>
<a name="Additional-information"></a>
<h4 >Additional information<a href="#Additional-information" class="wiki-anchor">¶</a></h4>
<p>Try not create more than one level of inheritance there and consider to use libraries, the inheritance is nice to use to not include in the test layer things unrelated with tests but we should avoid to have too many parent class or we would end up as the current hierarchy for sle test.<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17228" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17228</a></p>
qe-yam - action #120151 (Rejected): Performance related failed cases in migraiton regression grouphttps://progress.opensuse.org/issues/1201512022-11-09T00:35:39Zcoolgwwegao@suse.com
<p>This ticket used for tracking timeout related issue in regression group.</p>
<p><a href="https://openqa.suse.de/tests/9873547#step/pre_migration/10" class="external">https://openqa.suse.de/tests/9873547#step/pre_migration/10</a><br>
<a href="https://openqa.suse.de/tests/9897712#step/yast2_nfs_server/52" class="external">https://openqa.suse.de/tests/9897712#step/yast2_nfs_server/52</a></p>
qe-yam - action #119170 (New): Upload correct log /var/log/zypper.solverTestCase and the /var/log...https://progress.opensuse.org/issues/1191702022-10-21T09:49:41Zcoolgwwegao@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>According to the <a href="https://bugzilla.suse.com/show_bug.cgi?id=1204572" class="external">bug</a> we might need some new test module to enable the debugging and only upload the log on that case.<br>
But first we will need to think about refactoring those patching modules.</p>
<p>upload correct log /var/log/zypper.solverTestCase and the /var/log/zypper.log after patch_sle failed</p>
<p>base <a href="https://openqa.suse.de/tests/9759142#step/zypper_patch/20" class="external">https://openqa.suse.de/tests/9759142#step/zypper_patch/20</a> result, we can not get zypper log</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: /var/log/zypper.solverTestCase and the /var/log/zypper.log should be upload if patch_sle failed</p>
<p>*NOTE:<br>
following function used to collect info: upload_solvertestcase_logs</p>
qe-yam - action #115973 (Rejected): Add validation to yast2 scchttps://progress.opensuse.org/issues/1159732022-08-30T07:33:44Zcoolgwwegao@suse.com
<p>*** draft ***</p>
<p><del>After new module tests/x11/addon_products_via_SCC_yast2.pm introduced(<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15333" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15333</a>).<br>
One thing miss is no check of the packages base on installation summary page. We should add check like below implementaion:</del></p>
<p><del>os-autoinst-distri-opensuse/tests/installation/partitioning/suggested_partitioning/verify_decrypted_partition_deleted.pm Line 24</del> <br>
<del><code>my @deletion_entries = Mojo::DOM->new($text)->find('b')->map('text')->each;</code></del></p>
<p>We cannot test if they YaST module did properly its job using the YaST module, checking that each *-release package is present should suffice for this case.<br>
Additionally we need to reduce the number of screenshots here making more clear what are the actions in the test:<br>
<a href="https://openqa.suse.de/tests/9563367#step/addon_products_via_SCC_yast2/1" class="external">https://openqa.suse.de/tests/9563367#step/addon_products_via_SCC_yast2/1</a></p>
qe-yam - action #115427 (Resolved): test fails in yast2_keyboardhttps://progress.opensuse.org/issues/1154272022-08-17T11:32:18Zcoolgwwegao@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Server-DVD-Updates-x86_64-mau-extratests-yast2ui@64bit fails in<br>
<a href="https://openqa.suse.de/tests/9347115/modules/yast2_keyboard/steps/41" class="external">yast2_keyboard</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>. Run YaST2 GUI tests</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/9335118" class="external">20220815-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/9331959" class="external">20220814-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=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=mau-extratests-yast2ui&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #112199 (Resolved): [sle][migration][sle15sp5][SAP] recreate all qcow files...https://progress.opensuse.org/issues/1121992022-06-08T09:39:05Zcoolgwwegao@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>This task used to verify the create qcow process for sap migration job , include all qcows which will be used for 15sp5.<br>
You can refer following ticket which already verify one of qcow.<br>
<a href="https://progress.opensuse.org/issues/111953" class="external">https://progress.opensuse.org/issues/111953</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<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/8181676" class="external">98.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (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=Regression-on-Migration-from-SLE15-SPx&machine=64bit&test=offline_sles15sp1_ltss_pscc_lp-we-basesys-srv-desk-dev-contm-lgm-tsm-wsm-pcm_all_full_x11&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #111183 (Rejected): [sle][migration][sle15sp5][regression]test fails in ins...https://progress.opensuse.org/issues/1111832022-05-17T06:39:05Zcoolgwwegao@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Regression-on-Migration-from-SLE15-SPx-s390x-offline_sles15sp3_pscc_basesys-srv-desk-dev-contm-lgm-tsm-wsm-pcm_all_full_console@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/8763860/modules/install_service/steps/263" class="external">install_service</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<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/8694133" class="external">140.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/8656132" class="external">137.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=s390x&distri=sle&flavor=Regression-on-Migration-from-SLE15-SPx&machine=s390x-kvm-sle12&test=offline_sles15sp3_pscc_basesys-srv-desk-dev-contm-lgm-tsm-wsm-pcm_all_full_console&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #110728 (Rejected): [sle][migration][sle15sp4]test fails in user_settings_r...https://progress.opensuse.org/issues/1107282022-05-06T23:06:57Zcoolgwwegao@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Migration-from-SLE15-SPx-s390x-offline_SLES_15_SP1_ltss_pscc_basesys-srv-phub_def_full_zVM_preparation@s390x-zVM-Upgrade-m1 fails in<br>
<a href="https://openqa.nue.suse.com/tests/8702846/modules/user_settings_root/steps/6" class="external">user_settings_root</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>The base test suite is used for job templates defined in YAML documents. It has no settings of its own.</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.nue.suse.com/tests/8443282" class="external">118.3</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.nue.suse.com/tests/8439691" class="external">118.3</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.nue.suse.com/tests/latest?arch=s390x&distri=sle&flavor=Migration-from-SLE15-SPx&machine=s390x-zVM-Upgrade-m1&test=offline_SLES_15_SP1_ltss_pscc_basesys-srv-phub_def_full_zVM_preparation&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #91040 (Rejected): [sle][migration][sle15sp4]tracking https://jira.suse.com...https://progress.opensuse.org/issues/910402021-04-13T07:14:53Zcoolgwwegao@suse.com
<p>This ticket used for tracking leap to sle, update bug status confluence etc..</p>
openQA Infrastructure - action #70474 (Rejected): Machine ppc64le-hmc-single-disk is downhttps://progress.opensuse.org/issues/704742020-08-25T00:49:06Zcoolgwwegao@suse.com
<p>Run following case we found power machine can not be reached.<br>
For detail please check following error:<br>
<a href="https://openqa.nue.suse.com/tests/4587001#step/bootloader/5" class="external">https://openqa.nue.suse.com/tests/4587001#step/bootloader/5</a></p>
<p>error show after "rmvterm -m reducurrant --id 8 "<br>
this operation is only allowd when the managed system is in the standby or operating state</p>
openQA Project - action #60254 (Rejected): check module src code through openqa webui link not co...https://progress.opensuse.org/issues/602542019-11-26T06:40:08Zcoolgwwegao@suse.com
<p>1) run openqa job using openqa-clone-custom-git-refspec such as:<br>
openqa-clone-custom-git-refspec <a href="https://github.com/coolgw/os-autoinst-distri-opensuse/tree/test" class="external">https://github.com/coolgw/os-autoinst-distri-opensuse/tree/test</a> <a href="http://openqa.suse.de/tests/3598332" class="external">http://openqa.suse.de/tests/3598332</a><br>
Created job #3631946: sle-15-SP2-Migration-from-SLE15-SPX-to-SLE15-SP2-ppc64le-Build89.1-online_sles15_pscc_basesys-srv-phub_all_full_y@ppc64le -> <a href="http://openqa.suse.de/t3631946" class="external">http://openqa.suse.de/t3631946</a></p>
<p>The source code of first module isosize.pm is changed by my branch like following<br>
# Maintainer: Alberto Planas <a href="mailto:aplanas@suse.com">aplanas@suse.com</a><br>
diag($result_text);<br>
record_info('isosize', $result_text, result => $result);</p>
<ul>
<li> record_info('isosize', $result_text, result => $result);</li>
<li> record_info('isosize', $result_text, result => $result);</li>
</ul>
<p>2) check the cloned job t3631946, click the web ui link check source code of isosize.pm through UI link: <a href="https://openqa.suse.de/tests/3631946/modules/isosize/steps/1/src" class="external">https://openqa.suse.de/tests/3631946/modules/isosize/steps/1/src</a>, the result is not consistent with the real running code, i mean it should show the branch code changed by me.</p>
openQA Tests - action #59379 (Rejected): 12-sp5 qcow has been deleted in openqahttps://progress.opensuse.org/issues/593792019-11-13T04:25:16Zcoolgwwegao@suse.com
<p>SLES-12-SP5-x86_64-BETA1-gnome_all.qcow2 has been deleted, you check the following job for example:<br>
<a href="https://openqa.suse.de/tests/3577114" class="external">https://openqa.suse.de/tests/3577114</a> <====4 days ago run ok<br>
<a href="https://openqa.suse.de/tests/3586159/file/autoinst-log.txt" class="external">https://openqa.suse.de/tests/3586159/file/autoinst-log.txt</a> <===no qcow now!!! </p>
<p>This will trigger lots of failure in Migration job group and will impact 12sp5 openqa test.<br>
BTW:what's the strategy of garbage collection?</p>
openQA Project - action #58730 (Rejected): log can not upload to the case if test execution incom...https://progress.opensuse.org/issues/587302019-10-28T08:58:54Zcoolgwwegao@suse.com
<p>Detail info please check <a href="https://openqa.suse.de/tests/3535288#" class="external">https://openqa.suse.de/tests/3535288#</a><br>
No any log file uploaded, so i can not do any thing.</p>
openQA Project - action #56417 (Rejected): child task should stop if parent task failedhttps://progress.opensuse.org/issues/564172019-09-03T06:56:52Zcoolgwwegao@suse.com
<p>Detail info you can check with following link: the third job should not start since the parent already failed.<br>
<a href="https://openqa.suse.de/tests/3319310#dependencies" class="external">https://openqa.suse.de/tests/3319310#dependencies</a></p>
openQA Tests - coordination #55142 (Resolved): [migration][PjM][saga] Extending Migration testing...https://progress.opensuse.org/issues/551422019-08-06T08:49:17Zcoolgwwegao@suse.com
<a name="Gao-WeiSince-i-delete-39812-by-my-mistake-we-can-using-this-to-continue-track"></a>
<h1 >[Gao Wei]:Since i delete 39812 by my mistake, we can using this to continue track.<a href="#Gao-WeiSince-i-delete-39812-by-my-mistake-we-can-using-this-to-continue-track" class="wiki-anchor">¶</a></h1>
<p>While QA SLE department has a migration team located in Beijing (part of Sunny's line team), there is an opportunity to collaborate better and thus enhance/extend migration testing.</p>
<p>Why do we talk about this? During SLE15 SP0 migration was problematic area, as:</p>
<ul>
<li>it was defined very late; at first we were acting on poorly communicated and not clear requirements;</li>
<li>during SLE15 SP0 some aspects (requirements) of migration were changing which was making automation nearly impossible;</li>
<li>finally our testing effort in limited migration team are focused on migration itself including testing RMT/SMT etc.</li>
</ul>
<p>Our testing of migration is about testing matrix of various migration paths where we check if this process can be accomplished successfully.</p>
<p>Discussed idea with Sunny, Thorsten Kukuk, Marita and number of other people is to now ask functional teams to introduce some migration testing for some "services".<br>
As Thorsten described it: check if certain services can survive migration.</p>
<p>Initial idea:</p>
<ul>
<li>migration functional team is working on testing migration and maintaining all migration openQA modules;</li>
<li>each of the functional team should then consider testing some services in the way that they set them up in older system, call migration openQA module and check if configured service survives the migration.</li>
</ul>
<p>During the talks with Thorsten following services were named as good to test:</p>
<ul>
<li>apache</li>
<li>bind</li>
<li>net-snmp</li>
<li>dhcp server</li>
<li>nfs-server</li>
<li>rpcbind</li>
<li>radvd</li>
<li>cron (including all cronjobs, e.g. the in /etc/crontab)</li>
<li>apparmor</li>
<li>autofs</li>
<li>cups</li>
<li>kdump</li>
<li>ntp/chrony</li>
<li>postfix</li>
<li>firewall</li>
<li>vsftpd</li>
</ul>
<p>Please note: this is not about asking you to do even more work within the same time. Product Owners should work with Project Manager on priorities, so perhaps some testing could be dropped in order to add some of these migration testing.</p>