openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-07-18T13:35:03ZopenSUSE Project Management Tool
Redmine qe-yam - action #113725 (Rejected): Make autoyast tests exit when the autoyast profile encounter ...https://progress.opensuse.org/issues/1137252022-07-18T13:35:03Zybonatakisioannis.bonatakis@suse.com
<a name="observation"></a>
<h1 >observation<a href="#observation" class="wiki-anchor">¶</a></h1>
<p>What happens is that when the autoyast profile is wrong or not found, the tests keep trying to match needles and continue.</p>
<p>One such case is [0]. The problem appears something like 5 minutes after it starts but keeps running for 2h where the job time limits are reached.<br>
Because this cause a slow feedback loop of the tests, in combination of the resources which are occupied without any good reason i would like to propose a solution.</p>
<p>the easier would be to match a needle with the popup and abort. <br>
I dont know if there is already a module for it but we could run a check on the xml profile before installation module. I am not sure but i think there was something implemented for this specific reason. </p>
<p>To reproduce:<br>
you can use <a href="https://gist.github.com/b10n1k/bca22757c5e4eb11473ceda30820f6d2" class="external">https://gist.github.com/b10n1k/bca22757c5e4eb11473ceda30820f6d2</a> as <u>profile.xml</u></p>
<p>Actual results:<br>
<a href="http://aquarius.suse.cz/tests/11324#step/installation/2" class="external">http://aquarius.suse.cz/tests/11324#step/installation/2</a></p>
<p>Expected:<br>
i am not sure about that. should that be one of the following:</p>
<ul>
<li>Exit after some rational time when the error exists.</li>
<li>terminate needle checking after some expected time??
the while loop have specific expectations during installation. When those expectation do not ever match, the loop run for even.</li>
<li>Validate xml before installation and exit then if problem appears</li>
</ul>
<p>[0] <a href="http://aquarius.suse.cz/tests/11324" class="external">http://aquarius.suse.cz/tests/11324</a></p>
qe-yam - action #72277 (Closed): [y] Modify check in autoyast installation testhttps://progress.opensuse.org/issues/722772020-10-06T08:42:52Zybonatakisioannis.bonatakis@suse.com
<p>See <a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" title="action: [y][timeboxed:12h] Modify check in autoyast installation test (Resolved)" href="https://progress.opensuse.org/issues/69655">#69655</a></p>
<p>Ioannis proposes to implement retry mechanism to make check more stable.</p>
<p>Recent example: <a href="https://openqa.opensuse.org/tests/1421061#step/installation/1" class="external">https://openqa.opensuse.org/tests/1421061#step/installation/1</a></p>
<p>Due to the connections issues it would be meaningful to retry the request in <code>test_ayp_url</code> before show the record_info.</p>
<p>List of affected workers:</p>
<ul>
<li>openqaworker4 <a href="https://openqa.opensuse.org/admin/workers/97" class="external">https://openqa.opensuse.org/admin/workers/97</a></li>
<li>imagetester <a href="https://openqa.opensuse.org/admin/workers/41" class="external">https://openqa.opensuse.org/admin/workers/41</a></li>
<li>falafel.suse.cz :))</li>
</ul>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Retry mechanism is implemented and tested against problematic workers</li>
<li>If 1. doesn't stabilize, we investigate what is different in those workers configuration</li>
</ol>
qe-yam - action #72274 (Rejected): [y] nfs mount timeout investigationhttps://progress.opensuse.org/issues/722742020-10-06T06:45:51Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>I file this for investigation of the timeout during the nfs mount.<br>
The network looks ok and i cant see anything wrong from the y2logs. The logs ends the following</p>
<pre><code>2020-10-06 01:04:29 <1> s390kvm086(11263) [Ruby] clients/nfs_server.rb(main):156 NFS module finished
2020-10-06 01:04:29 <1> s390kvm086(11263) [Ruby] clients/nfs_server.rb(main):157 ----------------------------------------
2020-10-06 01:04:29 <1> s390kvm086(11263) [Interpreter] clients/nfs-server.rb:10 Called YaST client returned.
2020-10-06 01:04:29 <0> s390kvm086(11263) [Interpreter] clients/nfs-server.rb:10 Called YaST client returned: `ws_finish
2020-10-06 01:04:29 <1> s390kvm086(11263) [Interpreter] bin/y2start:60 Called YaST client returned.
2020-10-06 01:04:29 <0> s390kvm086(11263) [Interpreter] bin/y2start:60 Called YaST client returned: `ws_finish
2020-10-06 01:04:29 <0> s390kvm086(11263) [ui] YUI.cc(terminateUIThread):254 Sending shutdown message to UI thread
2020-10-06 01:04:29 <0> s390kvm086(11263) [ui] YUI.cc(uiThreadMainLoop):378 Shutting down UI main loop
2020-10-06 01:04:29 <0> s390kvm086(11263) [ui] YUI.cc(terminateUIThread):261 UI thread shut down correctly
2020-10-06 01:04:29 <1> s390kvm086(11263) [ncurses] YNCursesUI.cc(~YNCursesUI):121 Stop YNCursesUI
2020-10-06 01:04:29 <1> s390kvm086(11263) [ncurses] NCurses.cc(~NCurses):145 Shutdown NCurses...
2020-10-06 01:04:29 <1> s390kvm086(11263) [ncurses] NCurses.cc(~NCurses):164 NCurses down
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-ini] IniParser.cc(write):942 File /etc/sysconfig/nfs did not change. Not saving.
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-ini] IniParser.cc(write):942 File /etc/idmapd.conf did not change. Not saving.
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-ini] IniParser.cc(write):942 File /etc/os-release did not change. Not saving.
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-ini] IniParser.cc(write):942 File /usr/share/applications/YaST2/org.opensuse.yast.NFSServer.desktop did not change. Not saving.
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-ini] IniParser.cc(write):942 File /usr/share/applications/YaST2/org.opensuse.yast.NFSServer.desktop did not change. Not saving.
2020-10-06 01:04:29 <0> s390kvm086(11263) [Pkg] Y2CCPkg.cc(~Y2CCPkg):64 ~Y2CCPkg
2020-10-06 01:04:29 <0> s390kvm086(11263) [Pkg] PkgModule.cc(destroy):101 Deleting PkgModule object...
2020-10-06 01:04:29 <0> s390kvm086(11263) [Pkg] Callbacks.cc(~CallbackHandler):1925 Deleting callback handler
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-system] SystemAgent.cc(remove_directory):99 Removing temporary file /tmp/YaST2-11263-eK3ktS/exit
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-system] SystemAgent.cc(remove_directory):99 Removing temporary file /tmp/YaST2-11263-eK3ktS/stderr
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-system] SystemAgent.cc(remove_directory):99 Removing temporary file /tmp/YaST2-11263-eK3ktS/stdout
2020-10-06 01:04:29 <0> s390kvm086(11263) [agent-system] SystemAgent.cc(remove_directory):99 Removing temporary file /tmp/YaST2-11263-eK3ktS
2020-10-06 01:04:29 <1> s390kvm086(11263) [liby2] Y2ProgramComponent.cc(result):161 Sending result: `result (nil)
2020-10-06 01:04:29 <0> s390kvm086(11263) [Y2Ruby] binary/Y2RubyComponent.cc(~Y2RubyComponent):45 Destroying Y2RubyComponent
2020-10-06 01:04:29 <1> s390kvm086(11263) [Y2Ruby] binary/YRuby.cc(~YRuby):117 Shutting down ruby interpreter.
2020-10-06 01:04:29 <0> s390kvm086(11263) [YCPDeclarations] ../../src/YCPDeclarations.cc(~YCPDeclarations):221 Destructor called
</code></pre>
<p>and no error appears. </p>
<p>openQA test in scenario sle-15-SP3-Online-s390x-yast2_ncurses_gnome@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/4778612/modules/yast2_nfs_server/steps/61" class="external">yast2_nfs_server</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 yast2 UI, ncurses only.<br>
Test suite requires HDD settings to be set, we use inheritance for that.</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/4774110" class="external">50.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/4725363" class="external">44.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=Online&machine=s390x-kvm-sle12&test=yast2_ncurses_gnome&version=15-SP3" class="external">latest</a></p>
qe-yam - action #71842 (Closed): [y][powervm] select_patterns does not select software linkhttps://progress.opensuse.org/issues/718422020-09-24T12:13:17Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>ssh with x forwarding is known to perform worse than vnc, and problem is that we start to tab before screen is fully loaded.</p>
<p>Straight forward solutions:</p>
<ul>
<li>do more tabbing and get to software section eventually</li>
<li>sync and validate that screen is loaded ( we might be able to simply reuse installation-settings-overview-loaded from tests/installation/installation_overview.pm module )</li>
<li>sync and validate that there is no "analyzing your system" label to be sure that screen is loaded</li>
</ul>
<p>openQA test in scenario sle-15-SP3-Online-ppc64le-ssh-X@ppc64le-hmc-single-disk fails in<br>
<a href="https://openqa.suse.de/tests/4730915/modules/select_patterns/steps/26" class="external">select_patterns</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Conduct an installation using ssh with X-Forwarding. Might only be effective for zVM and powerVM</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/4553477" class="external">13.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=ppc64le&distri=sle&flavor=Online&machine=ppc64le-hmc-single-disk&test=ssh-X&version=15-SP3" class="external">latest</a></p>
qe-yam - action #71830 (Closed): [y] Set default target based on the expectationshttps://progress.opensuse.org/issues/718302020-09-24T11:29:35Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>As it is explained in the <a href="https://bugzilla.suse.com/show_bug.cgi?id=1164556">https://bugzilla.suse.com/show_bug.cgi?id=1164556</a> this is expected as they depend on how system was installed.<br>
This means that even if the "minimal" system role is selected the target is determined by the installed x11 packages and the xdm[0]<br>
Also from the logs </p>
<pre><code>2020-09-23 15:49:22 <1> redcurrant-1(4140) [Pkg] clients/default_target_proposal.rb:237 Pkg Builtin called: IsSelected
2020-09-23 15:49:22 <1> redcurrant-1(4140) [Pkg] Package.cc(IsSelected):505 Tag xdm provided by xdm is selected to install
2020-09-23 15:49:22 <1> redcurrant-1(4140) [Ruby] clients/default_target_proposal.rb:273 Systemd target detection says: X11 packages have been selected for installation
2020-09-23 15:49:22 <1> redcurrant-1(4140) [Ruby] clients/default_target_proposal.rb:268 Detected target proposal 'graphical'
2020-09-23 15:49:22 <1> redcurrant-1(4140) [Ruby] clients/default_target_proposal.rb:231 Setting systemd default target to graphical
2020-09-23 15:49:22 <1> redcurrant-1(4140) [Ruby] modules/services_manager_target.rb:118 New default target has been set: graphical
2020-09-23 15:49:22 <1> redcurrant-1(4140) [Ruby] clients/default_target_proposal.rb:193 Systemd default target is set to 'graphical'
2020-09-23 15:49:22 <1> redcurrant-1(4140) [Interpreter] installation/proposal_store.rb:480 Called YaST client returned.
2020-09-23 15:49:22 <0> redcurrant-1(4140) [Interpreter] installation/proposal_store.rb:480 Called YaST client returned: $["preformatted_proposal":"<ul><li>Graphical mode</li></ul>"]
2020-09-23 15:49:22 <0> redcurrant-1(4140) [Ruby] installation/proposal_store.rb:492 default_target_proposal MakeProposal() returns {"preformatted_proposal"=>"<ul><li>Graphical mode</li></ul>"}
</code></pre>
<p>So we need to fix the validation for the expected target in the system.</p>
<p>[0] <a href="https://github.com/yast/yast-services-manager/blob/master/src/modules/services_manager_target.rb#L126">https://github.com/yast/yast-services-manager/blob/master/src/modules/services_manager_target.rb#L126</a><br>
openQA test in scenario sle-15-SP3-Online-ppc64le-minimal+role_minimal@ppc64le-hmc-4disk fails in<br>
<a href="https://openqa.suse.de/tests/4725230/modules/verify_default_target/steps/5" class="external">verify_default_target</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Like default but explicitly select the system role "minimal". The resulting system should roughly correspond to an unregistered system but with access to modules for optional installation.</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/4557811" class="external">14.2</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=ppc64le&distri=sle&flavor=Online&machine=ppc64le-hmc-4disk&test=minimal%2Brole_minimal&version=15-SP3" class="external">latest</a></p>
qe-yam - action #71608 (Closed): [y] post_fail_hooks fails with script timeout, no logs collectedhttps://progress.opensuse.org/issues/716082020-09-21T15:26:48Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>there are a few tests that failed in the current build 36.5 but their logs are not presented in the logs&assets<br>
~~the reason (at least in the allmodules+allpatterns+registration seems to be a timeout</p>
<pre><code>�[0m�[37m[2020-09-17T15:35:54.176 CEST] [debug] post_fail_hook failed: script timeout: dmesg | grep "Out of memory" at /usr/lib/os-autoinst/testapi.pm line 1121.
</code></pre>
<p>The post_fail_hook should never fail, ideally, at least not fatal and it should continue even if some of the commands fail.~~</p>
<p>Problem was with sysrq command, which got fixed with <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11054/files" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11054/files</a><br>
But we don't switch to log console for whatever reason, and next step fails, we even don't see it typed properly and somehow byebug is called.</p>
<p>openQA test in scenario sle-15-SP3-Full-x86_64-allmodules+allpatterns+registration@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4701956/modules/addon_products_sle/steps/59" class="external">addon_products_sle</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Full Medium installation that covers the following cases:<br>
1. Additional modules enabled using SCC (Legacy, Development Tools, Web and<br>
Scripting, Containers, Desktop Applications);<br>
2. All patterns installed;<br>
3. System registration is skipped during installation;<br>
4. Installation is validated by successful boot and that YaST does not<br>
report any issues;<br>
5. Registration is performed on the installed system.</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/4693343" class="external">34.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/4688752" class="external">33.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=Full&machine=64bit&test=allmodules%2Ballpatterns%2Bregistration&version=15-SP3" class="external">latest</a></p>
qe-yam - action #71026 (Rejected): [y] Validate updated package version with self_updatehttps://progress.opensuse.org/issues/710262020-09-07T07:33:28Zybonatakisioannis.bonatakis@suse.com
<p>With the work on <a href="https://bugzilla.suse.com/show_bug.cgi?id=1175614" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1175614</a> done, we can check what version the self update download and use in the inst-sys. Rodion has already created validation module <code>tests/installation/validate_self_update.pm</code> checking that the feature attempts to download some packages from the update repo but it does not check/compare the package version between the default inst-sys and the update repo. The inst-sys stores the package version in <code>/.packages.root</code>. With yast2-installation-4.3.16 and above we should find <code>/.packages.self_update</code> file which we can use to compare</p>
qe-yam - action #70546 (Closed): [y] Remove soft fail for bsc#1175374https://progress.opensuse.org/issues/705462020-08-26T04:32:59Zybonatakisioannis.bonatakis@suse.com
<p><a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=addon-module-http&version=15-SP3" class="external">https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=addon-module-http&version=15-SP3</a><br>
<a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=addon-module-ftp&version=15-SP3" class="external">https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=addon-module-ftp&version=15-SP3</a></p>
<p>revert workaround from <a href="https://progress.opensuse.org/issues/70174" class="external">https://progress.opensuse.org/issues/70174</a> [0]</p>
<p>[0] <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10870" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10870</a></p>
qe-yam - action #69259 (Rejected): [y] Test fully qualified domain name as an input for yast2-net...https://progress.opensuse.org/issues/692592020-07-23T06:10:53Zybonatakisioannis.bonatakis@suse.com
<p>Although it is recommended to not use a FQDN as the static hostname there is not a restriction in the kernel or hostnamectl to use it and thus, there should not be a restriction in YaST in case that the user has a use case in which it is needed. YaST has recent changes in yast2-network to address this.</p>
<p>This is not typical use case, so low priority.</p>
qe-yam - action #69142 (Resolved): [y] Adjust bootloader for MM on aarch64https://progress.opensuse.org/issues/691422020-07-20T13:34:04Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>aarch64 uses uefi in the bootloader. <br>
The bootloader for the MM tests are not setup properly the parameters as you can see for instance on remote_ssh_target_ftp in <a href="https://openqa.suse.de/tests/4466996/modules/bootloader_start/steps/8" class="external">bootloader_start</a></p>
<p>the bootloader for the x86_64 loads parameters as you can find in <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/bootloader.pm#L59" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/bootloader.pm#L59</a>. basically <code>ssh</code> and <code>ssh.password</code>. Other parameters might are required based on the media. for example, Online installation, might need dns.</p>
<p>bootloader_start uses the correct bootloader as now.</p>
<p>We are missing at least following boot params:<br>
nameserver= ssh=1 sshpassword=nots3cr3t for ssh<br>
nameserver= vnc=1 vncpassword=nots3cr3t for vnc</p>
<p>So we need to make sure those are added to uefi bootloader.</p>
<p>Don't hesitate to contact Anton Smorodsky in case you need support with MM tests on arm.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>uefi bootloader passes the required parameters for networking(ssh, vnc, etc)</li>
</ul>
qe-yam - action #68579 (Rejected): [y] gitlab-ci needs another stage for verify_file_existencehttps://progress.opensuse.org/issues/685792020-07-02T11:14:45Zybonatakisioannis.bonatakis@suse.com
<p>We used to create new files in new PR. We usually have a test PR open while we create a MR to the qa-sle-functional-y. And this makes the test pipeline to fail. Which it should not.<br>
There are many solutions. </p>
<p>My propose is to create another stage in pipeline which will suit our logic.</p>
qe-yam - action #65447 (Rejected): Extend form of salt-formulas testhttps://progress.opensuse.org/issues/654472020-04-08T11:25:00Zybonatakisioannis.bonatakis@suse.com
<p>we want to extend smoke test for salt formulas using more element in the UI.<br>
As now the formula in use looks like <a href="http://aquarius.suse.cz/tests/2209#step/installation/9" class="external">http://aquarius.suse.cz/tests/2209#step/installation/9</a>.</p>
<p>we need to edit the /data/yast2/salt.tar.gz modify the formula/motd/form.yaml.</p>
<p>take a look at the relative ticket <a href="https://progress.opensuse.org/issues/49550" class="external">https://progress.opensuse.org/issues/49550</a></p>
<p>Also good to add validation for cloned profile( need to be added)</p>
<p>** Acceptance criteria</p>
<ul>
<li>Validation of cloned profile for relevant part</li>
<li>use additional components in the formula and we validate them after installation</li>
</ul>
openQA Tests - action #59411 (Rejected): [functional][y] betawarning appears for every selected p...https://progress.opensuse.org/issues/594112019-11-14T08:35:24Zybonatakisioannis.bonatakis@suse.com
<p>The Full_installer popups the beta warning each time we select a product in the "select extension and modules" dialog. The beta warning appears first time in the welcome dialog and it should not appears twice.</p>
<p>For now we have to find a workaround to let the test continue and display a soft_failure instead of breaking the test.</p>
openQA Tests - action #59318 (Resolved): [functional][u] packages are not gettting installed https://progress.opensuse.org/issues/593182019-11-11T16:04:24Zybonatakisioannis.bonatakis@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-lvm+resize_root@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3571728/modules/eog/steps/4" class="external">eog</a></p>
<p>Due to some misconfiguration(??) in the repos the system is incapable to find and install some packages.</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/3529472" class="external">72.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=Online&machine=64bit&test=lvm%2Bresize_root&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #57743 (Resolved): [functional][y][timeboxed:8h] test tries to reboot when ...https://progress.opensuse.org/issues/577432019-10-07T08:37:16Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Installer-DVD-s390x-cryptlvm@s390x-zVM-hsi-l2 fails in<br>
<a href="https://openqa.suse.de/tests/3445507/modules/shutdown/steps/3" class="external">shutdown</a></p>
<p>The shutdown module makes a call to the power_action to poweroff. I think the type_string "$action\n"; is not reach in power_action which makes the flow to check the else statement. from there it should drop into the poweroff_x11. Maybe it would be better to pass the textmode parameter explicitly in to the power_action.</p>
<p>This is cause by the change that we start testing gnome on s390x again and therefore use gnome menu to shutdown the system.<br>
Console way of shutting down worked fine: <a href="https://openqa.suse.de/tests/3305529#step/shutdown/6" class="external">https://openqa.suse.de/tests/3305529#step/shutdown/6</a></p>
<p>We need to investigate why gnome way doesn't work (maybe we don't press authenticate button).<br>
If problem is not resolved, we need follow-up ticket to apply the solution.</p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainers: okurz</p>
<p>Conduct installation with encrypted LVM selected during installation. Generated disk image used in downstream jobs.</p>
<p>(crypt-)LVM installations can take longer, especially on non-x86_64 architectures.</p>
<p>YAML_SCHEDULE=schedule/yaml/cryptlvm/cryptlvm_sle.yaml</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/3355212" class="external">36.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/3305529" class="external">27.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=Installer-DVD&machine=s390x-zVM-hsi-l2&test=cryptlvm&version=15-SP2" class="external">latest</a></p>