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>
openQA Tests - action #108551 (Rejected): [sle][migration][sle15sp4][Regression]test fails in scc...https://progress.opensuse.org/issues/1085512022-03-18T05:54:33Zcoolgwwegao@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-SLE12-SPx-s390x-offline_sles12sp3_ltss_pscc_sdk-asmm-contm-lgm-tcm-wsm-pcm_all_full_x11@s390x-kvm-sle12 fails in<br>
<a href="http://openqa.suse.de/tests/8343749/modules/scc_registration/steps/20" class="external">scc_registration</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>we encounter lot of scc timeout issue on migration group, so we use this for flag scc issue.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="http://openqa.suse.de/tests/8181638" 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="http://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Regression-on-Migration-from-SLE12-SPx&machine=s390x-kvm-sle12&test=offline_sles12sp3_ltss_pscc_sdk-asmm-contm-lgm-tcm-wsm-pcm_all_full_x11&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #90572 (Blocked): [sle][migration][backlog] tracking 1183405 L3: Delayed ou...https://progress.opensuse.org/issues/905722021-04-01T02:14:33Zcoolgwwegao@suse.com
<p>This ticket used for tracking 1183405, to check whether any action point can be done from migration team view.</p>
openQA Tests - action #69961 (Rejected): [sle][migration][SLE15SP3] service check on ldap and lda...https://progress.opensuse.org/issues/699612020-08-13T00:38:11Zcoolgwwegao@suse.com
<p>backgroud:<br>
Bug 1158921 - systemwide ldap.conf is removed after update (edit) // ldap.conf not used on new systemd<br>
We should enable ldap service status check and also ldap conf file</p>
openQA Tests - action #68563 (Blocked): [SLE][Migration][backlog]: check wheter ldap can be integ...https://progress.opensuse.org/issues/685632020-07-02T03:35:54Zcoolgwwegao@suse.comopenQA Tests - action #65465 (Rejected): [SLE][Migration][SLE15SP2]test fails in first_boot - per...https://progress.opensuse.org/issues/654652020-04-09T08:57:15Zcoolgwwegao@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Migration-to-HPC15-SP2-aarch64-offline_hpc12sp5_media_def_full@aarch64 fails in<br>
<a href="http://149.44.176.58/tests/4105696/modules/first_boot/steps/9" class="external">first_boot</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="http://149.44.176.58/tests/4105696" class="external">174.1</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="http://149.44.176.58/tests/4094707" class="external">173.6</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="http://149.44.176.58/tests/latest?arch=aarch64&distri=sle&flavor=Migration-to-HPC15-SP2&machine=aarch64&test=offline_hpc12sp5_media_def_full&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #60065 (Rejected): [SLE][Migration][backlog]: need workround for test openq...https://progress.opensuse.org/issues/600652019-11-20T03:00:00Zcoolgwwegao@suse.com
<p>software thind this is only warning msg so we need make workround in openqa, so we need open ticket for further investigate it and make workround if really not an issue.</p>
<p><a href="https://bugzilla.suse.com/show_bug.cgi?id=1153819&GoAheadAndLogIn=" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1153819&GoAheadAndLogIn=</a></p>
<ol>
<li>And finally, the 'error' is only informational and does not affect the
installation at all. In this regard, the openqa test case should be adjusted
to ignore the message.</li>
</ol>
openQA Tests - action #59217 (Rejected): [sle][migration][SLE12 SP5]test fails in patch_slehttps://progress.opensuse.org/issues/592172019-11-08T03:13:05Zcoolgwwegao@suse.com
<p>We need firstly upgrade zypper self before do "zypper patch", since zypper self exist issue.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP5-Regression-on-migrated-system-from-SLE12-SPx-x86_64-offline_sles12sp3_ltss_pscc_sdk_we_lp_asmm_contm_lgm_pcm_tcm_wsm_all_full_x86_64@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3567020/modules/patch_sle/steps/311" class="external">patch_sle</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>offline_sles12sp3_ltss_pscc_sdk_we_lp_asmm_contm_lgm_pcm_tcm_wsm_all_full x86_64</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/3167945" class="external">0251</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-migrated-system-from-SLE12-SPx&machine=64bit&test=offline_sles12sp3_ltss_pscc_sdk_we_lp_asmm_contm_lgm_pcm_tcm_wsm_all_full_x86_64&version=12-SP5" class="external">latest</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>
openQA Tests - coordination #54995 (Resolved): [SLE][Migration][SLE12SP5][EPIC]:Integrate service...https://progress.opensuse.org/issues/549952019-08-02T01:32:20Zcoolgwwegao@suse.com
<p>This EPIC is used for tracking service check task:<br>
Detail info please check the attachment.<br>
Currently we plan following service list for 12sp5:<br>
ntp<br>
postfix<br>
nfs<br>
rpcbind<br>
autofs<br>
cups<br>
apparm<br>
dhcp <br>
kdump</p>
openQA Tests - action #54245 (Resolved): [SLE][Migration][backlog]:smt/rmt migrationhttps://progress.opensuse.org/issues/542452019-07-15T09:06:05Zcoolgwwegao@suse.com
<p>Check smt regression whether cover all support scenario<br>
Implement the smt regression check if missing on some scenario/platform</p>
openQA Tests - action #53987 (Resolved): [SLE][Migration][backlog][enhance]: using openqa var to ...https://progress.opensuse.org/issues/539872019-07-09T07:58:52Zcoolgwwegao@suse.com
<p>Base jlausuch's feedback on <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7643" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7643</a><br>
As a future improvement, we could get the support_ver from OpenQA variables, since everytime we want to test a new version we will have to amend the code here, which is not scalable for maintaining all the services using this approach</p>