openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-02-14T13:55:15ZopenSUSE Project Management Tool
Redmine openQA Project - coordination #155485 (New): [saga][epic] Efficient openQA worker pool resource h...https://progress.opensuse.org/issues/1554852024-02-14T13:55:15Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Based on a bootstrapping discussions between lvogdt+mgriessmeier+okurz and my general goal to make efficient use of computing resources.<br>
Our openQA instances especially openqa.suse.de but also openqa.opensuse.org hold ready ressources as in physical machines running openQA worker instances for different architectures and worker classes. There are enough resources put in place so that builds for products can finish testing in reasonable time, e.g. some hours for a new Tumbleweed snapshot. But in between builds often there are idle resources, e.g. idle x86_64 openQA workers. Both in on-premise datacenters as well as public cloud resources can be reassigned for other purposes. So we should teach our applications how to only request resources as needed, run necessary workloads from scratch when machines are dynamically switched and used for other purposes and give back resources to a resource pool if the workload schedules allow.</p>
openQA Project - action #154777 (New): [saga][epic] Shareable os-autoinst and test distribution p...https://progress.opensuse.org/issues/1547772024-02-01T18:29:33Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>This is linked to <a href="https://progress.opensuse.org/projects/openqav3/wiki#Use-case-4" class="external">Use case 4</a>. os-autoinst only provides a low-level test API while test distributions like <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/</a> re-implement common helper functions, e.g. for booting a system, logging into desktop sessions, install packages. To provide middle layers we would like to provide a plugin infrastructure for shareable os-autoinst and test distribution plugins.</p>
openQA Project - coordination #154768 (New): [saga][ux] State-of-art user experience for openQAhttps://progress.opensuse.org/issues/1547682024-02-01T14:44:29Zokurzokurz@suse.com
<p>The first thing to define is what "state of the art" means for openQA's ecosystem</p>
QA - coordination #153655 (New): [saga][epic] Future datacenter and network setup at SUSEhttps://progress.opensuse.org/issues/1536552024-01-16T15:32:29Zokurzokurz@suse.comopenQA Project - coordination #128429 (New): [saga][epic] Accessibility improvements in openQAhttps://progress.opensuse.org/issues/1284292023-04-28T18:10:30Zokurzokurz@suse.comQA - coordination #123088 (New): [saga][epic] Re-combined Maintenance QA tooling covering both SL...https://progress.opensuse.org/issues/1230882023-01-13T12:40:11Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>SUSE Maintenance QA tooling is essential for the SUSE product maintenance processes and will be for upcoming years. For that we would like to maintain only properly maintained open source tooling that is used for open source projects as well as SUSE internal products, e.g. openSUSE+SLE.</p>
<a name="Ideas"></a>
<h2 >Ideas<a href="#Ideas" class="wiki-anchor">¶</a></h2>
<ul>
<li>Re-combine <a href="https://github.com/openSUSE/openSUSE-release-tools/blob/master/openqa-maintenance.py" class="external">https://github.com/openSUSE/openSUSE-release-tools/blob/master/openqa-maintenance.py</a> and <a href="https://gitlab.suse.de/qa-maintenance/openQABot/" class="external">https://gitlab.suse.de/qa-maintenance/openQABot/</a> and <a href="https://github.com/openSUSE/qem-bot/" class="external">https://github.com/openSUSE/qem-bot/</a></li>
</ul>
openQA Project - coordination #121723 (New): [saga][epic] Scale out: Future uses of on-premise cl...https://progress.opensuse.org/issues/1217232022-12-08T19:49:52Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>After <a class="issue tracker-6 status-15 priority-4 priority-default parent" title="coordination: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containe... (Blocked)" href="https://progress.opensuse.org/issues/80142">#80142</a> we can streamline and improve our datacenter management using cloud solutions</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> TBD</li>
</ul>
<a name="Ideas"></a>
<h2 >Ideas<a href="#Ideas" class="wiki-anchor">¶</a></h2>
<p>In 2022-12 okurz had the opportunity to meet mflores, TL of SUSE EngInfra. Main takeaway for okurz regarding "move to cloud" are the following points:</p>
<ol>
<li>We already make use of public cloud where it makes sense, e.g. public-cloud specific testing as well as having cloud computing ressources connected to openqa.opensuse.org like ARM sponsored aarch64 ressources. We do not see it as cost-efficient to move more compute-heavy tasks, i.e. openQA workers, to the public cloud with the exception of temporary disaster-recovery scenarios</li>
<li>We plan to follow the development of SUSE-internal cloud developments and plan to use such services whenever ready for the purposes of QE applications including openQA as well as other uses</li>
<li>We are looking forward to learn about results from any experiments regarding more efficient datacenter management to apply ourselves, e.g. bare-metal provisioning</li>
</ol>
openQA Project - coordination #112862 (New): [saga][epic] Future ideas for easy multi-machine han...https://progress.opensuse.org/issues/1128622022-06-22T10:32:25Zokurzokurz@suse.com
<a name="Ideas"></a>
<h2 >Ideas<a href="#Ideas" class="wiki-anchor">¶</a></h2>
<ul>
<li>Restart button on every job in the "dependency" view on cluster jobs</li>
<li>Preview in "dependency" of which jobs in a cluster would be restarted by an according restart option, e.g. restart of current job, advanced restart options, restart button on any other job</li>
</ul>
openQA Project - coordination #110833 (New): [saga][epic] Scale up: openQA can handle a schedule ...https://progress.opensuse.org/issues/1108332022-05-10T09:40:25Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<ul>
<li>See <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: OSD incident 2022-05-09: Many scheduled jobs not picked up despite idle workers, blocked by one w... (Resolved)" href="https://progress.opensuse.org/issues/110785">#110785</a></li>
</ul>
<a name="Ideas"></a>
<h2 >Ideas<a href="#Ideas" class="wiki-anchor">¶</a></h2>
<ul>
<li>Test locally by scheduling something like 100k jobs and see how the scheduler scales</li>
<li>Test locally by scheduling many jobs on something like 1k worker instances and see how the scheduler scales</li>
<li>Note that there's a unit test for scalability which one might simply invoke with very high numbers for scheduled jobs and available workers</li>
</ul>
openQA Project - coordination #105624 (New): [saga][epic] Reconsider how openQA handles secretshttps://progress.opensuse.org/issues/1056242022-01-27T15:24:56Znicksingernsinger@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>In the ongoing effort to improve our security we introduced things like e.g. <a href="https://github.com/os-autoinst/os-autoinst/pull/1909" class="external">https://github.com/os-autoinst/os-autoinst/pull/1909</a> which is a necessary step to improve how we handle passwords/secrets.<br>
I'd like to see that openQA also supports accessing passwords over different channels which are specifically designed to store secrets.<br>
I know that our public cloud testers already had similar challenges. IIUC they currently use their own setup of "vault" (see 3. in Suggestions). Maybe we could unify this approach and apply it to our whole infrastructure.</p>
<a name="Ideas"></a>
<h2 >Ideas<a href="#Ideas" class="wiki-anchor">¶</a></h2>
<ul>
<li>Support variables with arbitrary commands to access password managers like e.g. keepass (for small, local installations), pass or whatever the user decides to use.</li>
<li>Support GPG encrypted variables (and an according configuration for a private key for openQA)</li>
<li>Support common interfaces for software which is specifically designed for such use-cases. E.g. <a href="https://www.vaultproject.io/" class="external">https://www.vaultproject.io/</a></li>
</ul>
openQA Project - coordination #103950 (New): [saga][epic] Scale up: Efficient handling of large s...https://progress.opensuse.org/issues/1039502021-12-14T10:16:12Zokurzokurz@suse.comopenQA Project - coordination #103944 (New): [saga][epic] Scale up: More robust handling of diver...https://progress.opensuse.org/issues/1039442021-12-14T10:04:26Zokurzokurz@suse.comopenQA Project - coordination #103941 (New): [saga][epic] Scale up: Efficient, event-based handli...https://progress.opensuse.org/issues/1039412021-12-14T09:59:15Zokurzokurz@suse.comopenQA Tests - coordination #50507 (New): [qe-core][functional][saga] document lib/ functionshttps://progress.opensuse.org/issues/505072019-04-17T09:17:05Zjorauchjrauch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>As we currently have no documentation for the functions in lib/ we need a mechanism to automatically generate it from POD inside the files.</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>The team decided to apply the best practices described in <a href="https://www.perl.com/pub/2005/07/14/bestpractices.html/" class="external">https://www.perl.com/pub/2005/07/14/bestpractices.html/</a></p>
openQA Tests - coordination #33859 (New): [qe-core][sles][functional][saga][s390x] Review s390x B...https://progress.opensuse.org/issues/338592018-03-27T13:35:25Zmgriessmeiermgriessmeier@suse.com
<a name="User-Story"></a>
<h2 >User Story<a href="#User-Story" class="wiki-anchor">¶</a></h2>
<p>In late february coolo and me were visiting the IBM Regression Testing team in Böblingen to talk about test coverage and unification of our testcase into openQA.<br>
There were two main topics in this meeting. One was about how we can integrate the automated testcases conducted by IBM into openQA (this discussion is still ongoing).</p>
<p>The second, more relevant topic atm, was to talk about Bugs in SLE* which were found by IBM and to see which of the executed scenarios are covered on our side and which are not. It turned out that we lack a lot of test-scenarios and therefore missed some bugs in the product</p>
<p>This ticket is about to collect all those bugs and act on them by creating subtasks for implementing those scenarios step-by-step</p>
<a name="Further-information"></a>
<h2 >Further information<a href="#Further-information" class="wiki-anchor">¶</a></h2>
<p>using tags to define those further:</p>
<ul>
<li>[INFRA] - needs to be clarified with Ihno or Gerhard, e.g. Hardware component/setup on system level is missing, blocks other tags</li>
<li>[YAST] - Affecting a YaST module, extending YaST module tests for s390x</li>
<li>[MANUAL] - Can be verified manually in first place</li>
<li>[AUTOMATE] - eligible for being automated in the future</li>
<li>[FIXED] - bug is verified fixed </li>
</ul>
<a name="Network"></a>
<h3 >Network<a href="#Network" class="wiki-anchor">¶</a></h3>
<ul>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1084096" class="external">Network is not configured during installation when performing a zPXE installation</a> - (sles15 beta7)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=706967" class="external">IPV6 default gateway not set by installer</a> - (sles11.2)</li>
<li>[INFRA][MANUAL][AUTOMATE][YAST] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1071287" class="external">Vlan package missing</a> - (sles15 beta1)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1002974" class="external">Not possible to install w/o network on s390x, making use of SLES installation process with DVD from HMC drive.</a> - (sles12.2)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1083158" class="external">Network not starting correctly when installing using a PCI network device</a> - (sles15 beta7)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1069295" class="external">Problems installing SLES 15 using VLAN and a custom MAC address</a> - (sles15 beta2)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1067915" class="external">Yast showing error during finalizing when firewall is disabled during installation</a> - (sles15 beta2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1042055" class="external">Error "Augeas parsing/serializing error: Failed to match" displayed during installation step "Saving network configuration" when VLAN is configured</a> - (sles12.3)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=982727" class="external">Installation via HTTPS not possible when using Self-Signed Certifcate</a> - (sles12.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=944349" class="external">autoyast2: yast2-network: Installation using AutoYast fails in second stage</a> - (sles12.1)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=941948" class="external">Network configuration missing in autoinst.xml</a> - (sles12.1)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=929524" class="external">Possible parameters for network installation using TFTP</a> - (sles11.4)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=927100" class="external">Netmask parameter is not fetched correctly from parmfile (yast)</a> - (sles11.4)</li>
</ul>
<a name="Access-amp-Package"></a>
<h3 >Access & Package*<a href="#Access-amp-Package" class="wiki-anchor">¶</a></h3>
<ul>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1067007" class="external">Installer does not make use of given password while adding installer repository</a> - (sles15)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=927993" class="external">Installation of SLES11-SP4 on z10 breaks after downloading 3 of 6 installation files</a> - (sles11.4)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=706605" class="external">LPAR installation expects even the default value of device address to be entred manually</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1068326" class="external">Package yast2-cio is missing</a> - (sles15 beta2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1073074" class="external">Package yast2-cio not installed by default on s390x</a> - (sles15 beta4)</li>
</ul>
<a name="System-hangs"></a>
<h3 >System hangs<a href="#System-hangs" class="wiki-anchor">¶</a></h3>
<ul>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1038255" class="external">Using zpxe.rexx script to perform zPXE installation on zVM results in kernel panic during boot</a> - (sles12.3)</li>
</ul>
<a name="Devices"></a>
<h3 >Devices<a href="#Devices" class="wiki-anchor">¶</a></h3>
<ul>
<li>[MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=943623" class="external">Installation on iSCSI failed</a> - (sles12.1)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=808695" class="external">DASD selection not updated in Expert partitioning</a> - (sles11.3)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=815259" class="external">DASD or zfcp/scsi disks are listed for partitioning, even after deselecting DASD or zfcp/scsi disks</a> - (sles11.3)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=584703" class="external">Installation is not happening on FBA emulated SCSI disk</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=709138" class="external">Installation fails when two DASDs are used.</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=707059" class="external">DASD devices onlined via Yast2 are not persistant across reboot</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=706911" class="external">AutoYast installation fails to detect/sense the DASD</a> - (sles11.2)</li>
<li>[MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=708617" class="external">Unable to install SLES on LVM in a z/VM guest</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1070265" class="external">Not possible to format EDEV device (yast)</a> - (sles15 beta3)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1009112" class="external">System is falling into maintenance mode when adding a dasd with chccwdef and adding partitions with yast</a> - (sles12.2)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081200" class="external">YaST Partitioner no longer offering /boot/zipl as mount point</a> - (sles15 beta6)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081194" class="external">YaST does not properly detect that a DASD is not formatted</a> - (sles15 beta6)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081198" class="external">Changing proposed file system defaults fstab mount option to "Device Name" (yast2-storage-ng)</a> - (sles15 beta6)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1070175" class="external">Cannot add a partition to a MDISK</a> - (sles15 beta3)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1070206" class="external">"No proposal possible" error message when installing on MDISK</a> - (sles15 beta3)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=982726" class="external">Filesystem and Mount point not reliably selectable in the Yast Expert Partitioner when using yast.ssh</a> - (sles12.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1076305" class="external">yast: Cannot remove mount point with the partitioner</a> - (sles15 beta4)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1020336" class="external">"yast onpanic" dialog does not offer prepared zFCP dump devices</a> - (sles12.3)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081018" class="external">yast2-s390x: internal error when trying to install on multipathed zfcp LUN without swap device</a> - (sles15 beta7)</li>
<li>[MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1070569" class="external">system installed with default partitioning (btrfs) on zfcp comes up in emergency shell</a> - (sles15 beta3)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1068389" class="external">Yast does not enable non-NPIV zfcp device when "Get WWPNs" is pressed for the first time (yast2-s390)</a> - (sles15 beta2)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1068260" class="external">yast2-s390: Yast shows "Unkown Error 10" when activating SCSI LUNs on NPIV-enabled zfcp device</a> - (sles15 beta2)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1067265" class="external">YaST detects a formatted DASD as unformatted</a> - (sles15 beta1)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1063393" class="external">YaST reports "Error Disks formatting failed. Exit code: 255" after formatting DASD</a> - (sles15 beta1)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=935127" class="external">SLES 12 as a guest can not be installed on a CDL formated ECKD disk</a> - (sles12.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=993382" class="external">iSCSI volume not activated after installation</a> - (sles12.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=926706" class="external">yast2 refuses to use a non-standard iqn as iSCSI initiator</a> - (sles11.4)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1084503" class="external">YaST does not offer to format an unformatted DASD</a> - (sles15 beta7)</li>
</ul>
<a name="Others"></a>
<h3 >Others<a href="#Others" class="wiki-anchor">¶</a></h3>
<ul>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081783" class="external">Time zone settings from installation dialog are ignored (yast?)</a> - (sles15 beta7)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1040944" class="external">Exiting the "yast dump" dialog always displays an error (yast2-s390)</a> - (sles12.3)</li>
</ul>