openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-06T13:56:17ZopenSUSE Project Management Tool
Redmine openQA Project - action #156769 (Resolved): openQA nightly documentation build CI jobs fail with ...https://progress.opensuse.org/issues/1567692024-03-06T13:56:17Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://app.circleci.com/pipelines/github/os-autoinst/openQA/13086/workflows/c5beef2e-d0f1-4516-93cd-552ea903e83f/jobs/122001" class="external">https://app.circleci.com/pipelines/github/os-autoinst/openQA/13086/workflows/c5beef2e-d0f1-4516-93cd-552ea903e83f/jobs/122001</a></p>
<pre><code>Building native extensions. This could take a while...
ERROR: Error installing asciidoctor-pdf:
ERROR: Failed to build gem native extension.
current directory: /home/squamata/project/.gem/gems/bigdecimal-3.1.6/ext/bigdecimal
/usr/bin/ruby.ruby2.5 -r ./siteconf20240306-923-t3r9gw.rb extconf.rb
mkmf.rb can't find header files for ruby at /usr/lib64/ruby/include/ruby.h
extconf failed, exit code 1
Gem files will remain installed in /home/squamata/project/.gem/gems/bigdecimal-3.1.6 for inspection.
Results logged to /home/squamata/project/.gem/extensions/x86_64-linux/2.5.0/bigdecimal-3.1.6/gem_make.out
Exited with code exit status 1
</code></pre>
<p>I think I have seen that reproducing over the past days</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Check where ruby2.5 is pulled in which is possibly outdated and ensure to use a current version</li>
<li>Consider quick fixes or dropping PDF support at all but also keep in mind references in "gh-pages" itself</li>
<li>Consider updating the stack but then the base of Leap is a problem, so maybe switch to a different container base, e.g. Tumbleweed or use pandoc or something else to generate the PDF or headless web-browser</li>
</ul>
openQA Project - action #152855 (Resolved): ci: Warning in test output about Devel::Cover: This v...https://progress.opensuse.org/issues/1528552023-12-21T16:28:35Ztinitatina.mueller+trick-redmine@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>We are seeing the following informational message in CI:<br>
<a href="https://github.com/os-autoinst/os-autoinst/actions/runs/7289133602/job/19863136097#step:3:610" class="external">https://github.com/os-autoinst/os-autoinst/actions/runs/7289133602/job/19863136097#step:3:610</a></p>
<pre><code>7: This version of Devel::Cover was built with Perl version 5.038000.
7: It is now being run with Perl version 5.038002.
7: Attempting to make adjustments, but you may find that some of your modules do
7: not have coverage data collected. You may need to alter the +-inc, +-ignore
7: and +-select options.
</code></pre>
<p>Didn't check openQA+circleCI yet.<br>
It's not a problem right now, but annoying output and to me it sounds wrong that a module was built with an older perl version.<br>
No warning: <a href="https://github.com/os-autoinst/os-autoinst/actions/runs/7059044905/job/19215824140#step:3:638" class="external">https://github.com/os-autoinst/os-autoinst/actions/runs/7059044905/job/19215824140#step:3:638</a> (Dec 1)<br>
Warning: <a href="https://github.com/os-autoinst/os-autoinst/actions/runs/7098226502/job/19319753215#step:3:610" class="external">https://github.com/os-autoinst/os-autoinst/actions/runs/7098226502/job/19319753215#step:3:610</a> (Dec 5)</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> No "informational message" about Devel::Cover version mismatch in CI output</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Crosscheck different variants of our repositories, e.g. os-autoinst GHA and openQA circleCI</li>
<li>Do a web research about the message</li>
<li><a href="https://github.com/pjcj/Devel--Cover/blob/156fd4c4e195ea5aac994f92380f33587bb93059/Makefile.PL#L62" class="external">https://github.com/pjcj/Devel--Cover/blob/156fd4c4e195ea5aac994f92380f33587bb93059/Makefile.PL#L62</a></li>
<li>Crosscheck the package versions we have in our openSUSE containers</li>
<li>Prevent the message in all relevant repositories or state clearly why we can not feasibly achieve this</li>
<li>Open a Bug for the Package Maintainer to ensure that this package is always rebuilt when perl is updated</li>
</ul>
openQA Infrastructure - action #134900 (Resolved): salt states fail to apply due to "Pillar openq...https://progress.opensuse.org/issues/1349002023-08-31T08:29:28Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/1794135#L1178" class="external">https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/1794135#L1178</a></p>
<pre><code>----------
ID: apache2
Function: service.running
Result: False
Comment: One or more requisite failed: openqa.server./etc/apache2/ssl.crt/openqa.oqa.prg2.suse.org.crt, openqa.server./etc/apache2/ssl.key/openqa.oqa.prg2.suse.org.key
Started: 08:56:57.086043
Duration: 0.004 ms
Changes:
----------
</code></pre> openQA Infrastructure - action #134852 (New): gitlab CI job fails in telegraf check with unsuppor...https://progress.opensuse.org/issues/1348522023-08-30T13:50:42Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/1792173#L85">https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/1792173#L85</a> shows a failed telegraf check:</p>
<pre><code>Error running agent: Error loading config file /etc/telegraf/telegraf.d/slo.conf: plugin inputs.exec: line 1: configuration specified the fields ["environment"], but they weren't used
</code></pre>
<p>This is due to telegraf 1.22 not supporting the option. Current telegraf version is 1.26. Erroneously the host monitor.qa.suse.de downgraded the telegraf package today due to <code>journalctl -u auto-upgrade --since=today</code>:</p>
<pre><code>Aug 30 03:55:38 monitor systemd[1]: Started Automatically upgrade packages..
Aug 30 03:55:40 monitor sh[4129]: Retrieving repository 'devel_openQA' metadata [.....done]
Aug 30 03:55:41 monitor sh[4129]: Building repository 'devel_openQA' cache [...done]
Aug 30 03:55:47 monitor sh[4129]: Retrieving repository 'Update repository of openSUSE Backports' metadata [......error]
Aug 30 03:55:47 monitor sh[4129]: Repository 'Update repository of openSUSE Backports' is invalid.
Aug 30 03:55:47 monitor sh[4129]: [repo-backports-update|http://download.opensuse.org/update/leap/15.4/backports/] Valid metadata not found at specified URL
Aug 30 03:55:47 monitor sh[4129]: History:
Aug 30 03:55:47 monitor sh[4129]: - File './repodata/74d0b705b4bb64056928ad7f19a7d2424b5bb0e526df9b95dff98b8c901d4b3e-deltainfo.xml.gz' not found on medium 'http://download.opensuse.org/update/leap/>
Aug 30 03:55:47 monitor sh[4129]: - Can't provide ./repodata/74d0b705b4bb64056928ad7f19a7d2424b5bb0e526df9b95dff98b8c901d4b3e-deltainfo.xml.gz
Aug 30 03:55:47 monitor sh[4129]: Please check if the URIs defined for this repository are pointing to a valid repository.
Aug 30 03:55:47 monitor sh[4129]: Warning: Skipping repository 'Update repository of openSUSE Backports' because of the above error.
Aug 30 03:55:54 monitor sh[4129]: Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15' metadata [........................................done]
Aug 30 03:56:21 monitor sh[4129]: Building repository 'Update repository with updates from SUSE Linux Enterprise 15' cache [....done]
Aug 30 03:56:22 monitor sh[4129]: Some of the repositories have not been refreshed because of an error.
Aug 30 03:56:22 monitor sh[4129]: Loading repository data...
Aug 30 03:56:23 monitor sh[4129]: Reading installed packages...
Aug 30 03:56:26 monitor sh[4129]: Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' >
Aug 30 03:56:26 monitor sh[4129]: Computing distribution upgrade...
Aug 30 03:56:28 monitor sh[4129]: The following 31 packages are going to be upgraded:
Aug 30 03:56:28 monitor sh[4129]: bind-utils device-mapper libdevmapper-event1_03 libdevmapper1_03 libdevmapper1_03-32bit libicu-suse65_1 libicu65_1-ledata liblvm2cmd2_03 libopenjp2-7 libparted0 li>
Aug 30 03:56:28 monitor sh[4129]: The following 3 packages are going to be downgraded:
Aug 30 03:56:28 monitor sh[4129]: libqt5-qtstyleplugins-platformtheme-gtk2 php7-imagick telegraf
Aug 30 03:56:28 monitor sh[4129]: The following 2 NEW packages are going to be installed:
Aug 30 03:56:28 monitor sh[4129]: libfstrm0 libprotobuf-c1
Aug 30 03:56:28 monitor sh[4129]: 31 packages to upgrade, 3 to downgrade, 2 new.
</code></pre>
<p>The problem is <code>Skipping repository 'Update repository of openSUSE Backports' because of the above error.</code> meaning that we continue the upgrade despite an error to refresh a repo causing the downgrade.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Upgrade is only conducted when all configured repositories can be successfully refreshed</li>
<li><strong>AC2:</strong> We are alerted if the situation of broken repos persists</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Research how to only continue with the upgrade after the refresh was successful and abort otherwise</li>
</ul>
<a name="Workaround"></a>
<h2 >Workaround<a href="#Workaround" class="wiki-anchor">¶</a></h2>
<p>Apply the upgrade manually when this happens.</p>
openQA Infrastructure - action #134135 (New): openqa-monitor.qa.suse.de salt CI deploy telegraf c...https://progress.opensuse.org/issues/1341352023-08-11T13:08:47Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>From <a href="https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/1751110#L5155" class="external">https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/1751110#L5155</a></p>
<pre><code>openqa-monitor.qa.suse.de:
2023-08-11T13:00:13Z E! [inputs.x509_cert] could not find file: [/etc/dehydrated/certs/monitor.qe.nue2.suse.org/fullchain.pem]
2023-08-11T13:00:18Z E! [telegraf] Error running agent: input plugins recorded 1 errors
</code></pre>
<p>likely related to the move of the VM along with its hypervisor to FC Basement in the domain .qe.nue2.suse.org</p>
openQA Project - action #132125 (Resolved): Automatic submission from devel:openQA:tested into op...https://progress.opensuse.org/issues/1321252023-06-29T08:58:45Zjbaier_czjbaier@suse.cz
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The version of os-autoinst in TW is from 2 months ago, apparently the auto-submit is no longer working. This is problem for derived containers like isotovideo:qemu-x86-os-autoinst-distri-opensuse used in CI tests (see <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/runs/5406505265/jobs/9830108237?pr=17306" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/runs/5406505265/jobs/9830108237?pr=17306</a>). To make it worse, there was no notification about any issue until now.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<p><strong>AC1:</strong> New versions of os-autoinst are submitted into Factory automatically<br>
<strong>AC2:</strong> We are notified about problems</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Look at the pipeline: <a href="http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/lastFailedBuild/console" class="external">http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/lastFailedBuild/console</a></li>
<li><em>DONE</em> Fix the faulty package, in this case devel-container</li>
<li>Monitor the jenkins builds</li>
<li>As needed extend <a href="https://github.com/os-autoinst/scripts/blob/master/os-autoinst-obs-auto-submit" class="external">https://github.com/os-autoinst/scripts/blob/master/os-autoinst-obs-auto-submit</a></li>
<li>Make sure that all relevant jenkins builds are configured to notify us, e.g. send an email to a related mailing list. Just configure as post build action "email notification" and add the corresponding mailing list. Here I suggest <a href="mailto:o3-admins@suse.de">o3-admins@suse.de</a> and also consider the other related jobs.</li>
</ul>
openQA Infrastructure - action #125531 (Resolved): salt-pillar C pipeline runs into 1h timeouthttps://progress.opensuse.org/issues/1255312023-03-07T14:57:55Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://gitlab.suse.de/openqa/salt-pillars-openqa/-/jobs/1441277" class="external">https://gitlab.suse.de/openqa/salt-pillars-openqa/-/jobs/1441277</a> fails with "The script exceeded the maximum execution time set for the job" after 1h.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> salt-pillar CI jobs take significantly less than 2h</li>
<li><strong>AC2:</strong> salt-pillar CI jobs do not commonly fail due to gitlab CI timeout</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Try to just bump the timeout</li>
<li>Look into the history of previous jobs how long it usually takes to apply the salt pillar triggered high state</li>
<li>Find out if there are specific machines that are problematic</li>
</ul>
openQA Project - action #125237 (Resolved): os-autoinst codecov check "fully_covered" returns 99%...https://progress.opensuse.org/issues/1252372023-03-01T20:06:09Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>So it looks like the problem first mentioned in <a href="https://github.com/os-autoinst/os-autoinst/pull/2260#issuecomment-1448414226" class="external">https://github.com/os-autoinst/os-autoinst/pull/2260#issuecomment-1448414226</a> shows up in other pull requests as well now. Who can understand why codecov says that we have 99.28% coverage in the "fully_covered" section as configured in <a href="https://github.com/os-autoinst/os-autoinst/blob/master/codecov.yml#L18" class="external">https://github.com/os-autoinst/os-autoinst/blob/master/codecov.yml#L18</a> even though <a href="https://app.codecov.io/gh/os-autoinst/os-autoinst/pull/2270/tree" class="external">https://app.codecov.io/gh/os-autoinst/os-autoinst/pull/2270/tree</a> shows all referenced paths to be covered by 100%?</p>
<a name="Steps-to-reproduce"></a>
<h2 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<p>Seems to happen in all pull requests that are either opened anew or updated</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> It is known why the actual percentage doesn't match the expected 100%</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Bisect like it is done in <a href="https://github.com/os-autoinst/os-autoinst/pull/2271" class="external">https://github.com/os-autoinst/os-autoinst/pull/2271</a> and similar PRs</li>
<li>Click on "View details" in merged PRs to see the checks</li>
</ul>
openQA Project - action #113138 (Resolved): sporadic failure in openQA test "t/ui/23-audit-log.t"...https://progress.opensuse.org/issues/1131382022-07-01T08:30:32Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://app.circleci.com/pipelines/github/os-autoinst/openQA/9895/workflows/bd749c46-c563-4fcd-9d17-6195780465f3/jobs/93334/steps" class="external">https://app.circleci.com/pipelines/github/os-autoinst/openQA/9895/workflows/bd749c46-c563-4fcd-9d17-6195780465f3/jobs/93334/steps</a> shows</p>
<pre><code>[06:59:35] t/ui/23-audit-log.t ........................ 12/?
# Failed test 'correct number of elements'
# at t/ui/23-audit-log.t line 132.
# got: '9'
# expected: '1'
# less than a minute ago Demo job_create {
# "TEST": "foo",
# "id": 1
# }, less than a minute ago Demo comment_create {
# "id": 1,
# "job_id": 1
# }, less than a minute ago Demo table_create {
# "backend": "qemu",
# "description": null,
# "id": 1,
# "name": "foo",
# "settings": [],
# "table": "Machines"
# }, less than a minute ago Demo table_create {
# "description": null,
# "id": 1,
# "name": "testsuite",
# "settings": [],
# "table": "TestSuites"
# }, less than a minute ago Demo table_create {
# "arch": "x86_64",
# "description": null,
# "distri": "opensuse",
# "flavor": "DVD",
# "id": 1,
# "name": "",
# "settings": [],
# "table": "Products",
# "version": "13.2"
# }, less than a minute ago Demo user_login null, less than a minute ago system startup openQA restarted, less than a minute ago Demo user_login null, less than a minute ago system startup openQA restarted
# Looks like you failed 1 test of 18.
[06:59:35] t/ui/23-audit-log.t ........................ 13/?
# Failed test 'clickable events'
# at t/ui/23-audit-log.t line 140.
[06:59:35] t/ui/23-audit-log.t ........................ 14/? # Looks like you failed 1 test of 14.
[06:59:35] t/ui/23-audit-log.t ........................ Dubious, test returned 1 (wstat 256, 0x100)
</code></pre>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> t/ui/23-audit-log.t stable in many runs</li>
<li><strong>AC2:</strong> t/ui/23-audit-log.t is not included in tools/unstable_tests.txt</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Read about the history of latest changes in <a href="https://progress.opensuse.org/issues/111539" class="external">https://progress.opensuse.org/issues/111539</a>, maybe okurz already tried to run 1000 runs locally and couldn't reproduce or something.</li>
<li>Try it out locally with coverage enabled and see if it can be reproduced. Maybe try NON_HEADLESS=1. Or try to spot the mistake by code analysis.</li>
<li>Fix the test race-free</li>
<li>Remove test module from tools/unstable_tests.txt</li>
<li>Optional: Try to gather statistics from circleCI because we have similar problems reappearing</li>
</ul>
openQA Project - action #90164 (Resolved): Make gitlab.suse.de/openqa/salt-states-openqa publichttps://progress.opensuse.org/issues/901642021-03-16T12:22:20Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>To be able to use the salt recipes for o3 as well as provide it as a solution to manage any openQA infrastructure we decided to make gitlab.suse.de/openqa/salt-states-openqa public, e.g. put it on github within github.com/os-autoinst/</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> gitlab.suse.de/openqa/salt-states-openqa is available on a public, non-personal git repository</li>
<li><strong>AC2:</strong> SUSE QE Tools team member have read-write access to the repository</li>
<li><strong>AC3:</strong> Changes in the repo are still automatically applied within the OSD infrastructure</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Research about best practices to move from internal gitlab repo to external github/gitlab</li>
<li>Copy gitlab.suse.de/openqa/salt-states-openqa to github, e.g. in <a href="https://github.com/os-autoinst" class="external">https://github.com/os-autoinst</a> scope, and create back-mirror into salt-states repo or get rid of it completely</li>
</ul>
openQA Infrastructure - action #77887 (Resolved): [tools][openqa] Enable automatic openQA investi...https://progress.opensuse.org/issues/778872020-11-14T15:46:47Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>SUSE QEM is challenged by a relative high false-positive rate of openQA tests. This is due to objectively higher product quality of released products in comparison to products in development, i.e. pre-GM SLE including Tumbleweed snapshots before release. We already use "openqa-investigate" for o3 which has been running there for multiple months and I received positive feedback. We can now extend the solution to osd.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Automatic investigation jobs are triggered and commented on new, unlabeled failures within osd production groups, e.g. not development groups</li>
<li><strong>AC2:</strong> Automatic investigation jobs run within a reasonable time to provide useful feedback to reviewers in their regular review routines</li>
<li><strong>AC3:</strong> No harmful performance impact on infrastructure due to too many automatic investigation jobs</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>There is a script based solution "openqa-investigate" which we already use automatically within o3, see <a href="https://gitlab.suse.de/openqa/auto-review/-/blob/master/.gitlab-ci.yml#L110" class="external">https://gitlab.suse.de/openqa/auto-review/-/blob/master/.gitlab-ci.yml#L110</a></li>
<li>Try out dry-runs of "openqa-investigate" against OSD and check for obvious things missing or going wrong, e.g. immediate errors or crashes or unreasonable results</li>
<li>Extending to osd can be just as simple as applying a similar block in .gitlab-ci.yml for osd</li>
<li>When activated monitor over couple of days for usefulness and performance impact</li>
<li>Consider changing the schedule of the scheduled pipeline, e.g. trigger more often over the day, or even "continuous" :)</li>
<li>Optional: Ensure that auto-review walks first over all issues, potentially even failed ones to detect known issues, and if unknown to auto-review, only then trigger investigation jobs</li>
</ul>
openQA Project - coordination #77698 (New): [epic] synchronous qemu based system level test in pu...https://progress.opensuse.org/issues/776982020-11-11T09:51:22Zokurzokurz@suse.com
<a name="User-Story"></a>
<h2 >User Story<a href="#User-Story" class="wiki-anchor">¶</a></h2>
<p>As a software stack developer I want to run synchronous qemu based tests in pull request CI runs to have system level test coverage before accepting PRs</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Easy instructions how to run qemu based system level tests in any github project exist</li>
<li><strong>AC2:</strong> Scalable for multiple projects</li>
<li><strong>AC3:</strong> One example github PR or gitlab MR shows a successful test in action for any product or repository</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Experiment with local runs of isotovideo, maybe based on github.com/os-autoinst/os-autoinst-distri-example
<ul>
<li>isotovideo supports setting all necessary test parameters on the command line but a file <code>vars.json</code> can be used as well</li>
</ul></li>
<li>Look into github actions and publish on github marketplace for easy inclusion
<ul>
<li>you can start with <a href="https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/creating-a-docker-container-action" class="external">https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/creating-a-docker-container-action</a> and <a href="https://github.com/actions/hello-world-docker-action" class="external">https://github.com/actions/hello-world-docker-action</a></li>
<li>read how to publish on marketplace: <a href="https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action" class="external">https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action</a></li>
</ul></li>
<li>If the above is not feasible or as alternative create documentation describing how to use the proof of concept</li>
<li>Try to have a generic solution that is not dependant on one specific CI provider but consider "polishing" it for at least one to be super-easy :)</li>
<li>Also upload test artifacts, e.g. serial terminal log and video.ogv , e.g. see <a href="https://docs.github.com/en/free-pro-team@latest/actions/guides/storing-workflow-data-as-artifacts#uploading-build-and-test-artifacts" class="external">https://docs.github.com/en/free-pro-team@latest/actions/guides/storing-workflow-data-as-artifacts#uploading-build-and-test-artifacts</a> . was suggested by pdostal in <a href="https://github.com/os-autoinst/os-autoinst-distri-example/pull/4#issuecomment-727800015" class="external">https://github.com/os-autoinst/os-autoinst-distri-example/pull/4#issuecomment-727800015</a></li>
</ul>
openQA Infrastructure - action #75235 (Resolved): container image devel:openQA:ci/base is unresol...https://progress.opensuse.org/issues/752352020-10-24T11:43:03Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>container image devel:openQA:ci/base in <a href="https://build.opensuse.org/package/show/devel:openQA:ci/base" class="external">https://build.opensuse.org/package/show/devel:openQA:ci/base</a> is unresolvable with "nothing provides this-is-only-for-build-envs needed by cmake-mini", probably caused by <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: Improve package and base OS version support: Bump versions to Leap 15.2 (Resolved)" href="https://progress.opensuse.org/issues/69154">#69154</a> and okurz switching the base OS config from openSUSE Leap 15.1 to openSUSE Leap 15.2</p>
<a name="Impact"></a>
<h2 >Impact<a href="#Impact" class="wiki-anchor">¶</a></h2>
<p>Likely we need this container in os-autoinst but not anymore in openQA but os-autoinst then could fail eventually</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<p>Research what the error message means, potentially ask in IRC e.g. <a href="irc://chat.freenode.net/opensuse-factory" class="external">#opensuse-factory</a> or mailing lists</p>
openQA Infrastructure - action #73345 (Resolved): [u] Cleanup of old needles from os-autoinst-nee...https://progress.opensuse.org/issues/733452020-10-14T08:33:58Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>In very active needle repos like we have for SLE and also openSUSE outdated needles should be deleted from time to time when they are not matched or used for long. If nobody wants to do it everything becomes worse. Also see <a href="https://chat.suse.de/channel/testing?msg=rYLtgxCr4a7GeKTsh" class="external">https://chat.suse.de/channel/testing?msg=rYLtgxCr4a7GeKTsh</a> and following messages</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Cleanup over sensible time range has been conducted on OSD</li>
<li><strong>AC2:</strong> Same as <em>AC1</em> for o3</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Look for needles that have not been matched and not used on OSD since 2 years, select all, review if the selection is sane or if there is too much deleted, then delete</li>
<li>Same for 1 year or smaller period than before</li>
<li>Same on o3</li>
</ul>