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>
openQA Tests - action #95455 (Rejected): [qac][kernel] Make record_soft_failure shows error as re...https://progress.opensuse.org/issues/954552021-07-13T15:29:46Zybonatakisioannis.bonatakis@suse.com
<p>The idea is that when there is a bug open we have <code>record_soft_failure</code> to workaround in the test level.<br>
But when the bug is resolved there are two approach AFAIK. remove the softfail or leave it intact to find regressions. <br>
however when the bug is gone and softfail still exists in the code, there is not an easy way to distinguish the regression.</p>
<p>I propose to enhance the <code>record_soft_failure</code> to show the regression. One idea is to introduce a flag(extra param?) which we can switch <br>
when the bug has been resolved. Then we can either make the test fail*[1] or show the soft_fail with another colour.</p>
<p>I am not sure if this is the best approach so please comment below if something better comes in your mind.</p>
<p>*[1] maybe we can introduce a parameter to define severity. Then if(critical)->(fail)->else(pass) </p>
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>
openQA Tests - action #71896 (Rejected): [y] Expert partitioning framework refactoringhttps://progress.opensuse.org/issues/718962020-09-25T10:38:14Zybonatakisioannis.bonatakis@suse.com
<p>As we are expanding and adding new subroutines in the framework we need to consider some refactoring to avoid duplication and make it more usable. </p>
<p>Things to refactor:</p>
<ul>
<li>_set_partitioning subroutine</li>
<li>this does not work for all the partitioning options</li>
<li>_encrypt_with_lvm subroutine</li>
<li>The encryption should work for a higher level for all the Pages that implement encryption</li>
<li>select_item_in_system_view_table subroutine</li>
<li>replace if-else with state design or find another solution.</li>
<li>Consider expansion?</li>
<li>naming of the Pages</li>
<li>The pages use the name of the page that they access but it is hard to tell if which proposal(current or suggested) comes from </li>
</ul>
<p>Let start with small things because more can come up but design is something that need to be always a task in progress but we cant cover everything.</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 #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>
openQA Tests - action #68908 (Rejected): [y] Remove deprecated sections from autoyast profilehttps://progress.opensuse.org/issues/689082020-07-13T07:10:25Zybonatakisioannis.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-autoyast_tftp@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4445217/modules/installation/steps/5" class="external">installation</a></p>
<p>As the warning shows there are sections that they have removed from the xml profile.<br>
We need to adjust the xml.</p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Tests installation with tftp configured. Uses profile from <a href="https://github.com/yast/aytests-tests" class="external">https://github.com/yast/aytests-tests</a> repo.</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/4424929" class="external">209.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/4344368" class="external">209.2</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&test=autoyast_tftp&version=15-SP2" class="external">latest</a></p>
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>
openQA Tests - action #68515 (Rejected): [y] iscsi_client wont be fixed in SLE15SP2https://progress.opensuse.org/issues/685152020-06-29T19:29:07Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>bsc#1162514 is resolved but the fix for SLE15SP2 is declined[0]. Although the fix is submitted as maintenance update[1]. </p>
<p>I think we need to act on those jobs that fail in OSD and update the packages or move them in development group. </p>
<p>[0] <a href="https://build.suse.de/request/show/219816" class="external">https://build.suse.de/request/show/219816</a><br>
[1] <a href="https://build.suse.de/request/show/220839" class="external">https://build.suse.de/request/show/220839</a></p>
<p>openQA test in scenario sle-15-SP2-Online-x86_64-iscsi_client_normal_auth_backstore_fileio@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4399148/modules/iscsi_client/steps/64" class="external">iscsi_client</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>iSCSI multimachine test suite with manually configure the static network between SUTs.<br>
Authentication: 2way normal authentication, discovery authentication is not configured <br>
Backstore: fileIO<br>
Test data are included in enclosed yaml file.</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/4222729" class="external">190.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/4201288" class="external">189.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=Online&machine=64bit&test=iscsi_client_normal_auth_backstore_fileio&version=15-SP2" class="external">latest</a></p>
openQA Project - action #66427 (Rejected): openqa-cli cant trigger single jobhttps://progress.opensuse.org/issues/664272020-05-05T11:05:58Zybonatakisioannis.bonatakis@suse.com
<p>I used </p>
<pre><code class="text syntaxhl" data-language="text">openqa-cli api --pretty --osd -X POST isos ISO=SLE-15-SP2-Online-x86_64-Build188.1-Media1.iso DISTRI=sle VERSION=15-SP2 FLAVOR=Online ARCH=x86_64 BUILD=188.1 TEST=autoyast_home_encrypted
</code></pre>
<p>to trigger a single job named <em>autoyast_home_encrypted</em> but it wound up running all the jobs for the Online medium. The corresponding command with openqa-client was </p>
<pre><code class="text syntaxhl" data-language="text">openqa-client isos post --host=http://openqa.suse.de ISO=SLE-15-SP2-Online-x86_64-Build188.1-Media1.iso DISTRI=sle VERSION=15-SP2 FLAVOR=Online ARCH=x86_64 BUILD=188.1 TEST=autoyast_home_encrypted
</code></pre>
<p>Expected:<br>
To run only the test job with name autoyast_home_encrypted from the TEST variable</p>
<p>Actual:<br>
Seems to ignore the TEST variable and match all the others with reasult to trigger many jobs</p>
openQA Tests - action #66043 (Rejected): [functional][y][hyperv] test failing in shutdown needs i...https://progress.opensuse.org/issues/660432020-04-24T05:23:42Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The system is booting properly and it shutdown without problem but the openqa is hanging for some reason after login. <br>
Some logs for the serial terminal[0] </p>
<p>[0] <a href="https://gitlab.suse.de/snippets/486" class="external">https://gitlab.suse.de/snippets/486</a></p>
<p>openQA test in scenario sle-15-SP2-Full-x86_64-allmodules+allpatterns+registration@svirt-hyperv-uefi fails in<br>
<a href="https://openqa.suse.de/tests/4159856/modules/shutdown/steps/14" class="external">shutdown</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/4134956" class="external">179.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/4128392" class="external">178.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=svirt-hyperv-uefi&test=allmodules%2Ballpatterns%2Bregistration&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #65882 (Rejected): [functional][y][sporadic] test fails in first_boot cant ...https://progress.opensuse.org/issues/658822020-04-20T13:05:05Zybonatakisioannis.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-aarch64-allmodules+allpatterns@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/4139668/modules/first_boot/steps/10" 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>Maintainer: jrauch</p>
<p>Perform an installation enabling all modules and selecting all patterns.<br>
This test suite always registers to have access to all modules.</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/4135055" class="external">179.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/4126364" class="external">178.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=allmodules%2Ballpatterns&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #65858 (Rejected): [functional] ppc64le iso is not bootablehttps://progress.opensuse.org/issues/658582020-04-20T09:25:27Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Verified also manual that the image can not boot.<br>
the output looks like:</p>
<pre><code class="text syntaxhl" data-language="text">Trying to load: from: /pci@800000020000000/scsi@5/disk@100000000000000 ... SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
failed to load CHRP boot loader.SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
SCSI-DISK: Access beyond end of device !
E3404: Not a bootable device!
E3407: Load failed
Type 'boot' and press return to continue booting the system.
Type 'reset-all' and press return to reboot the system.
Ready!
</code></pre>
<p>openQA test in scenario sle-15-SP2-Online-ppc64le-cryptlvm@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/4135453/modules/bootloader_start/steps/2" class="external">bootloader_start</a></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/4135453" class="external">179.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="https://openqa.suse.de/tests/4124651" class="external">178.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=Online&machine=ppc64le&test=cryptlvm&version=15-SP2" class="external">latest</a></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 #64328 (Rejected): [functional][y] fix hostname_inst from btrfs_libstorage-nghttps://progress.opensuse.org/issues/643282020-03-09T22:50:23Zybonatakisioannis.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-btrfs_libstorage-ng@64bit-ipmi fails in<br>
<a href="https://openqa.suse.de/tests/3972161/modules/hostname_inst/steps/7" class="external">hostname_inst</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainers: QSF-y.</p>
<p>Test installation with btrfs filesystem and libstorage-ng.<br>
Validates no_COW attributes on subvolumes, file system on partitions, checks whether /home is on separate partition or not (depending on the 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/3592332" class="external">89.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-ipmi&test=btrfs_libstorage-ng&version=15-SP2" class="external">latest</a></p>