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>
openQA Project - action #127568 (New): Openqa log can not show detail syntax errorhttps://progress.opensuse.org/issues/1275682023-04-13T02:32:20Zcoolgwwegao@suse.com
<p>Openqa can not show detail compile error <br>
If you check <a href="https://openqa.suse.de/tests/10911002" class="external">https://openqa.suse.de/tests/10911002</a></p>
<p>ONLY show following error<br>
"Reason: tests died: unable to load main.pm, check the log for the cause (e.g. syntax error)"</p>
<p>Actually i need following error which currently show in github CI:<br>
Global symbol "%args" requires explicit package name (did you forget to declare "my %args"?) at lib/Installation/ProductSelection/ProductSelectionController.pm line 41.</p>
openQA Infrastructure - action #121507 (New): Iscsi issue on OSD worker https://progress.opensuse.org/issues/1215072022-12-06T07:29:51Zcoolgwwegao@suse.com
<p>This ticket used for tracking fix progress on worker ibft issue.</p>
<p>After trying following actions we still encounter issue popup on iscsi.<br>
1)Try to use ip instead of url on sanhook parameter<br>
<a href="https://github.com/os-autoinst/os-autoinst/pull/2219" class="external">https://github.com/os-autoinst/os-autoinst/pull/2219</a><br>
2)Base <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=wegao_iscis_investigation_use_ip_url" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=wegao_iscis_investigation_use_ip_url</a> , we found ONLY worker3 has issue on ibft, so disable worker3 ibft test temporarily until someone can investigate further and fix the problem eventually.<br>
MR for remove worker3 ibft test<br>
<a href="https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/472#note_454772" class="external">https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/472#note_454772</a></p>
<p>NOTE: we also try to use external iscsi server instead of OSD tgt server and below result show good.<br>
<a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=wegao_iscis_investigation_private_server_openqa_salt_command" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=wegao_iscis_investigation_private_server_openqa_salt_command</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>
openQA Tests - action #104887 (Resolved): [sle][migration][sle15sp4] build new qcow for SLES-15-...https://progress.opensuse.org/issues/1048872022-01-14T02:09:15Zcoolgwwegao@suse.com
<p>Issue found during pam module integration, the su command has wrong permission lead the case failed, so we need recreate new one.<br>
Detail info can check following job<br>
<a href="http://openqa.suse.de/tests/7965886#step/pam/51" class="external">http://openqa.suse.de/tests/7965886#step/pam/51</a></p>
openQA Tests - action #104358 (In Progress): [sle][migration][backlog]test fails in check_upgrade...https://progress.opensuse.org/issues/1043582021-12-27T01:54:46Zcoolgwwegao@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_sles12sp4_ltss_pscc_sdk-asmm-contm-lgm-tcm-wsm_all_full@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.nue.suse.com/tests/7900515/modules/check_upgraded_service/steps/64" class="external">check_upgraded_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.nue.suse.com/tests/7888695" class="external">77.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.nue.suse.com/tests/7863534" class="external">74.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.nue.suse.com/tests/latest?arch=s390x&distri=sle&flavor=Regression-on-Migration-from-SLE12-SPx&machine=s390x-kvm-sle12&test=offline_sles12sp4_ltss_pscc_sdk-asmm-contm-lgm-tcm-wsm_all_full&version=15-SP4" class="external">latest</a></p>
openQA Project - action #101950 (Resolved): open.qa document need update base latest opensuse rel...https://progress.opensuse.org/issues/1019502021-11-05T01:42:33Zcoolgwwegao@suse.com
<p>When i use opensuse leap 15.3, i found nft used instead of iptables, so if you using iptables -L -v you will get nothing.<br>
So following debug description need update, better give correct guild for how to debug firewalld related command</p>
<p><a href="http://open.qa/docs/#_multi_machine_tests_setup" class="external">http://open.qa/docs/#_multi_machine_tests_setup</a><br>
iptables -L -v<br>
As long as the SUT has access to external network, there should be a non-zero packet count in the forward chain between the br1 and external interface.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: Docs cover nftables backend for firewalld</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Clarify docs to mention e.g. firewalld with nftables backend or iptables</li>
</ul>
openQA Tests - action #101435 (Resolved): [opensuse][migration][tw] fix openldap_to_389ds issue o...https://progress.opensuse.org/issues/1014352021-10-25T09:00:54Zcoolgwwegao@suse.com
<p><a href="https://bugzilla.opensuse.org/show_bug.cgi?id=1189868" class="external">https://bugzilla.opensuse.org/show_bug.cgi?id=1189868</a><br>
Base William's feedback, we likely need to add to /etc/hosts:<br>
127.0.0.1 susetest</p>
openQA Tests - action #93991 (New): [sle][Migration][backlog] investigate service check another s...https://progress.opensuse.org/issues/939912021-06-15T01:40:00Zcoolgwwegao@suse.com
<p>This ticket used for investigate following items:<br>
1)Is that possible call autoinst::loadtest dynamic, insert module during case running.<br>
2)This solution can work or not in openqa.</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 #70168 (Blocked): [SLE][Migration][backlog]: sssd.pm integrate into service...https://progress.opensuse.org/issues/701682020-08-18T08:18:35Zcoolgwwegao@suse.comopenQA 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 - 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 - action #49664 (Resolved): [sle][migration][SLE15SP1]test fails in patch_sle - WE ...https://progress.opensuse.org/issues/496642019-03-26T05:01:35Zcoolgwwegao@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP1-Installer-DVD-POST-x86_64-online_sled15_rmt_basesys+desk+phub+we_def_full_zdup@64bit fails in<br>
<a href="https://openqa.suse.de/tests/2710459/modules/patch_sle/steps/29" 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>
<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/2340465" class="external">125.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?distri=sle&version=15-SP1&arch=x86_64&flavor=Installer-DVD-POST&test=online_sled15_rmt_basesys%2Bdesk%2Bphub%2Bwe_def_full_zdup&machine=64bit" class="external">latest</a></p>
openQA Tests - action #44108 (Resolved): [migration] investigate why can not boot on ppc64le https://progress.opensuse.org/issues/441082018-11-21T07:49:55Zcoolgwwegao@suse.com
<p>sle-15-SP1-Installer-DVD-TEST-ppc64le-Build96.7-0001offline_sles12sp3_media_base_all_full@ppc64le</p>
<p>sles12sp3 to sle-15-SP1 meida upgrade case </p>