openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-22T10:52:59ZopenSUSE Project Management Tool
Redmine QA - action #157753 (Workable): Bring back automatic recovery for openqaworker-arm-1 size:Mhttps://progress.opensuse.org/issues/1577532024-03-22T10:52:59Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>In #132614 openqaworker-arm-1 was moved to FC Basement so that we have one hot-redundant aarch64 OSD machine outside of PRG2. For that to be setup we need to also accomodate the automatic recovery feature.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The automatic recovery of openqaworker-arm-1 on crashes works</li>
<li><strong>AC2:</strong> openqaworker-arm-1 runs OSD production jobs in a stable way</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Read <a class="issue tracker-4 status-3 priority-3 priority-lowest closed child" title="action: Move of openqaworker-arm-1 to FC Basement size:M (Resolved)" href="https://progress.opensuse.org/issues/133748">#133748</a> about notes regarding PDU auto-control</li>
<li>Find on <a href="https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs" class="external">https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs</a> how the new PDU can be used</li>
<li>Integrate the new PDU in <a href="https://gitlab.suse.de/openqa/grafana-webhook-actions" class="external">https://gitlab.suse.de/openqa/grafana-webhook-actions</a></li>
<li>After openqaworker-arm-1 is fully back including recovery remove silences in <a href="https://monitor.qa.suse.de/alerting/silences" class="external">https://monitor.qa.suse.de/alerting/silences</a></li>
<li>Remove the "Mute All times" in <a href="https://monitor.qa.suse.de/alerting/routes" class="external">https://monitor.qa.suse.de/alerting/routes</a> for <code>__contacts__ =~ .*"Trigger reboot of openqaworker-arm-1".*</code></li>
</ul>
<a name="Rollback-actions"></a>
<h2 >Rollback actions<a href="#Rollback-actions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Bring back openqaworker-arm-1 into production <a href="https://progress.opensuse.org/projects/openqav3/wiki/#Bring-back-machines-into-salt-controlled-production" class="external">https://progress.opensuse.org/projects/openqav3/wiki/#Bring-back-machines-into-salt-controlled-production</a></li>
</ul>
QA - action #157741 (Workable): Approve/reject SLE maintenance release requests on IBS synchronou...https://progress.opensuse.org/issues/1577412024-03-22T10:23:10Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>One of the most important responsibilities within SLE maintenance testing is to approve/reject SLE maintenance release requests based on openQA test results. So far <a href="https://github.com/openSUSE/qem-bot" class="external">qem-bot</a> is sufficient to schedule openQA tests but merely does a mediocre job of reporting back results as test results are asynchronously polled based on a periodic schedule <a href="https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipeline_schedules" class="external">https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipeline_schedules</a> causing unnecessary delays, inefficient polling, using outdated results <a class="issue tracker-4 status-4 priority-4 priority-default child" title="action: Use live openQA test results instead of inconsistent qem-dashboard database in qem-bot approver (Feedback)" href="https://progress.opensuse.org/issues/122311">#122311</a> and not even reporting back on blocking test failures <a class="issue tracker-6 status-1 priority-4 priority-default child parent" title="coordination: [epic] enable qem-bot comments on IBS (was: enable qa-maintenance/openQABot comments on smelt again) (New)" href="https://progress.opensuse.org/issues/97121">#97121</a>. Let's use a proper architecture with efficient event based triggers providing relevant information back to release requests on IBS using core openQA features rather than too much custom lacking downstream tooling: After the PoC in <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: [spike][timeboxed:20h][integration] Approve/reject SLE maintenance release requests on IBS synchr... (Resolved)" href="https://progress.opensuse.org/issues/154498#note-14">#154498-14</a> we should fully implement that to approve/reject the according release request synchronously after AMQP event listening.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> something synchronously approves based on AMQP events</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow-on with the PoC of <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: [spike][timeboxed:20h][integration] Approve/reject SLE maintenance release requests on IBS synchr... (Resolved)" href="https://progress.opensuse.org/issues/154498#note-14">#154498-14</a></li>
<li>Setup qem-bot or an alternative on existing or new server but make access to the logs</li>
<li>Add it as part of qem-dashbaord which already has AMQP support</li>
<li>Ensure that qem-bot runs near-continuous to be able to listen to all AMQP events accordingly, maybe back-to-back gitlab CI jobs with limits to prevent parallel execution which we already have?</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Also related to <a class="issue tracker-4 status-4 priority-4 priority-default child" title="action: Use live openQA test results instead of inconsistent qem-dashboard database in qem-bot approver (Feedback)" href="https://progress.opensuse.org/issues/122311">#122311</a>, <a class="issue tracker-6 status-1 priority-3 priority-lowest" title="coordination: [saga][epic] Re-combined Maintenance QA tooling covering both SLE+openSUSE (New)" href="https://progress.opensuse.org/issues/123088">#123088</a>, <a class="issue tracker-6 status-1 priority-4 priority-default child parent" title="coordination: [epic] enable qem-bot comments on IBS (was: enable qa-maintenance/openQABot comments on smelt again) (New)" href="https://progress.opensuse.org/issues/97121">#97121</a>, <a class="issue tracker-6 status-1 priority-4 priority-default parent behind-schedule" title="coordination: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, ... (New)" href="https://progress.opensuse.org/issues/99303">#99303</a>, <a class="issue tracker-4 status-3 priority-3 priority-lowest closed child" title="action: Find "last build" of a product over API size:M (Resolved)" href="https://progress.opensuse.org/issues/152939">#152939</a>, <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: [timeboxed:6h][spike solution] a single command line or openQA webUI search view to show all test... (Resolved)" href="https://progress.opensuse.org/issues/131279">#131279</a>, <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: Provide API to get job results for a particular incident, similar to what dashboard/qem-bot does ... (Resolved)" href="https://progress.opensuse.org/issues/117655">#117655</a></p>
openQA Infrastructure - action #157555 (Workable): [spike][timeboxed:10h] Use a different ssh roo...https://progress.opensuse.org/issues/1575552024-03-19T21:34:02Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>In <a href="https://sd.suse.com/servicedesk/customer/portal/1/SD-150437" class="external">https://sd.suse.com/servicedesk/customer/portal/1/SD-150437</a> we are asked to handle "compromised root passwords in QA segments" including s390zl11…16</p>
<a name="Goals"></a>
<h2 >Goals<a href="#Goals" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>G1:</strong> Have an s390x kvm openQA installation job with non-default password succeed as far as possible</li>
<li><strong>G2:</strong> Identify which follow-up steps need to be done to fully support non-default passwords in such scenarios</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>os-autoinst-distri-opensuse in principle supports using a different password, see <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/main_common.pm#L165" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/main_common.pm#L165</a></li>
<li>Clone a default s390x kvm openQA installation job <a href="https://openqa.suse.de/tests/13875911" class="external">https://openqa.suse.de/tests/13875911</a> from this scenario <a href="https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online&machine=s390x-kvm&test=default&version=15-SP6" class="external">https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online&machine=s390x-kvm&test=default&version=15-SP6</a> but with <code>PASSWORD=<new_password></code> with <code><new_password></code> being anything you setup temporary and see how far the test can reach</li>
<li>Fix obvious small problems and identify bigger follow-up tasks</li>
<li>Actually s390x shouldn't really matter that much in this context, could also be an "svirt" job</li>
</ul>
openQA Project - action #157273 (Workable): Run os-autoinst-distri-openQA directly from git witho...https://progress.opensuse.org/issues/1572732024-03-14T16:38:04Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>With <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: [spike][timeboxed:10h] Run os-autoinst-distri-example directly from git and ensure candidate need... (Resolved)" href="https://progress.opensuse.org/issues/154783">#154783</a> we have proper git caching so we can run git based tests efficiently on our workers now. Now we should go the next step and migrate one "production" test distribution to use only git and not hold anything provided by admins on o3 in o3:/var/lib/openqa/share/tests for this test distribution.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> /var/lib/openqa/share/tests/open{qa,QA} do not exist</li>
<li><strong>AC2:</strong> openqa-in-openqa tests still pass consistently</li>
<li><strong>AC3:</strong> openqa-in-openqa test details, needle candidates and source code views still show content as expected</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Change test definitions in <a href="https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml" class="external">https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml</a> in your branch to use <a href="https://github.com/os-autoinst/os-autoinst-distri-openQA" class="external">https://github.com/os-autoinst/os-autoinst-distri-openQA</a> for test code (and needles)</li>
<li>Check that tests can be triggered this way on a test instance</li>
<li>Do not put anything in /var/lib/openqa/share/tests and ensure tests still work as well as source code view and needle candidates in test details pages</li>
<li>To provide needle candidates there are multiple possibilities when and where the needle candidate data can be provided, try out one or multiple of the following:
<ol>
<li><em>Given</em> a test distribution/needledir does not yet exist in a local cache (like asset downloads work or GIT_CACHE_DIR in os-autoinst and/or worker implementation), <em>When</em> tests are triggered on the side of web UI, <em>Then</em> the relevant data is git cloned, e.g. in the same steps as or similar to *_URL asset download</li>
<li><em>Given</em> a test distribution/needledir does not yet exist in a local cache, <em>When</em> the worker uploads the general test structure, e.g. which modules will be executed, <em>Then</em> the relevant data is git cloned</li>
<li><em>Given</em> a test distribution/needledir does not yet exist in a local cache, <em>When</em> the worker uploads individual needle check results, <em>Then</em> it also uploads as part of the JSON result files and image uploads all the necessary information to display needle candidates <em>And</em> the webUI in the receiving upload handler handles that somewhat … but does not overload when 1k workers upload in parallel or something :)</li>
<li><em>Given</em> a test distribution/needledir does not yet exist in a local cache, <em>When</em> the worker uploads final results (or "finalizes" the job), <em>Then</em> the webUI triggers a download of test files and/or needle files to a local git cache dir as necessary</li>
<li><em>Given</em> a test distribution/needledir does not yet exist in a local cache, <em>When</em> the first person reviews test results and selects needle candidates, <em>Then</em> the webUI triggers a download of test files and/or needle files to a local git cache dir as necessary</li>
</ol></li>
<li>If you identify any bigger feature implementation in openQA or os-autoinst itself being necessary then ensure those requirements are covered in other tickets and block on those tickets accordingly</li>
</ul>
<a name="Out-of-scope"></a>
<h2 >Out of scope<a href="#Out-of-scope" class="wiki-anchor">¶</a></h2>
<ul>
<li>Any bigger feature implementation in openQA or os-autoinst itself.</li>
</ul>
QA - action #157204 (Workable): Sync openQA job removal events to qem-dashboard listening to AMQP...https://progress.opensuse.org/issues/1572042024-03-14T05:33:51Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p><a href="https://suse.slack.com/archives/C02CLB8TZP1/p1709892527534149?thread_ts=1709883106.021479&cid=C02CLB8TZP1" class="external">https://suse.slack.com/archives/C02CLB8TZP1/p1709892527534149?thread_ts=1709883106.021479&cid=C02CLB8TZP1</a><br>
When openQA jobs are deleted then the according reference in qem-dashboard should also be removed. Listen to AMQP events to sync the removal accordingly</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> SLE maintenance openQA jobs previously blocking SLE maintenance updates on <a href="http://dashboard.qam.suse.de/blocked" class="external">http://dashboard.qam.suse.de/blocked</a> do not block approval after such openQA jobs are deleted from the openQA database</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Use TDD: Extend <a href="https://github.com/openSUSE/qem-dashboard/blob/main/t/amqp.t" class="external">https://github.com/openSUSE/qem-dashboard/blob/main/t/amqp.t</a> and ensure there is a failing test first</li>
<li>Extend <a href="https://github.com/openSUSE/qem-dashboard/blob/08cea810f936faeb6af35b645270d85f6569c6b9/lib/Dashboard/Model/AMQP.pm#L33" class="external">https://github.com/openSUSE/qem-dashboard/blob/08cea810f936faeb6af35b645270d85f6569c6b9/lib/Dashboard/Model/AMQP.pm#L33</a> to update the database entry accordingly or delete, whatever is applicable</li>
<li>For all current openQA job result entries in the dashboard database crosscheck if there are entries for jobs that do not exist anymore in the openQA database. Remove accordingly.</li>
<li>Verify operation in production: E.g. create an artificial, failed openQA job in OSD for a non-critical SLE maintenance update, wait till it shows up as blocking on <a href="http://dashboard.qam.suse.de/blocked" class="external">http://dashboard.qam.suse.de/blocked</a> or in log files of the qem-bot "approve" cycle, remove the job over <code>openqa-cli -X delete jobs/$id</code> again and verify that <a href="http://dashboard.qam.suse.de/blocked" class="external">http://dashboard.qam.suse.de/blocked</a> does not show up as blocked on that job anymore</li>
</ul>
<a name="Out-of-scope"></a>
<h2 >Out of scope<a href="#Out-of-scope" class="wiki-anchor">¶</a></h2>
<ul>
<li>Regular cleanup of results when we missed or have otherwise not received according AMQP events</li>
</ul>
openQA Infrastructure - action #156130 (Workable): Install Intel GPU on one of the servers in FC ...https://progress.opensuse.org/issues/1561302024-02-27T08:43:01Zszarate
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Steve Quinata provided a intel GPU ideally we should be able to connect it to one of our servers for further testing, and/or openQA enablement so we can also test hardware encoding, openCL, and other libraries that benefit from having extra hardware</p>
<p><a href="https://www.anandtech.com/show/17266/intels-arctic-soundm-server-accelerator-to-land-mid2022-with-hardware-av1-encoding" class="external">https://www.anandtech.com/show/17266/intels-arctic-soundm-server-accelerator-to-land-mid2022-with-hardware-av1-encoding</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> One remotely accessible computer features the GPU adapter</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Identify usable hardware from FC Basement or order if not too expensive in coordination with requester</li>
<li>Put the GPU into the suitable hardware</li>
<li>Update racktables</li>
<li>Inform szarate about the usable hardware setup</li>
</ul>
openQA Project - action #153475 (Workable): Reconsider the formatting of variable-names in the re...https://progress.opensuse.org/issues/1534752024-01-12T10:16:51Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>From the SUSE QE Tools coordination call when we had a demonstration about <a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" title="action: Many incomplete jobs endlessly restarted over several weeks size:M (Resolved)" href="https://progress.opensuse.org/issues/152569">#152569</a> we realized that a string like <code>[Not restarting because job has been restarted already $auto_clone_limit times and failed with /$auto_clone_regex/]</code> is confusing because of the dollar signs. And it doesn't reveal the values so it's not obvious what the number or the regex is.<br>
For reference the "already cloned n times" message does state the maximum.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The user facing informational messages avoids dollar-signs as those are implementation-specifics</li>
<li><strong>AC2:</strong> The messages still state explicitly that those values can be configured somehow</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Consider using explicit wording like "variables" or "settings" (or ALL_CAPS) and/or reference the actual values</li>
<li>Consider prefixing the config section, e.g. "global:auto_clone_regex" or "global.auto_clone_regex"</li>
<li>Add a help icon or URL to the point where the actual value is defined</li>
<li>Expand the values, either within the reason or somewhere else like in a comment, the investigation tab or elsewhere</li>
<li>Clarify limitations of the reason, and if they can be addressed</li>
</ul>
openQA Infrastructure - action #152101 (Workable): Allow salt to properly configure non-productio...https://progress.opensuse.org/issues/1521012023-12-05T13:41:36Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>See lessons learned meeting <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Conduct "lessons learned" with Five Why analysis for "test fails in iscsi_client due to salt 'hos... (Resolved)" href="https://progress.opensuse.org/issues/139136">#139136</a>. Would diesel now work with the MTU related changes? We should ensure that diesel is treated as tap worker regardless of not being used as production tap-worker.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> non-production workers within the OSD salt config are properly configured as multi-machine openQA workers with suffixes e.g. <code>WORKER_CLASS=tap_poo1234</code> (no GRE tunnels required)</li>
<li><strong>AC2:</strong> non-production openQA workers with a special worker class can execute multi-machine jobs correctly if triggered against the special worker class</li>
<li><strong>AC3:</strong> non-production openQA workers with a special worker class do not pick up production multi-machine jobs</li>
<li><strong>AC4:</strong> The team knows how to configure non-production multi-machine workers for development/setup/debugging</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Read how <a href="https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/openvswitch.sls?ref_type=heads#L24" class="external">https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/openvswitch.sls?ref_type=heads#L24</a> matches on "tap" in WORKER_CLASS. We used to disable production tap worker classes by adding a suffix that include a ticket reference, e.g. "tap_poo1234"</li>
<li><del>Extend that to be able to match on variants of "tap"</del> It will still work with e.g. "tap_poo1234". The last part of <code>multihostclass in pillar['workerconf'][host]['workers'][wnum]['WORKER_CLASS']</code> refers to a string (and not a list) so Python does in fact just check whether the string contains <code>tap</code> at all.</li>
<li>Take a look at OSD workers that currently have "tap_$something", see <a href="https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls" class="external">https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls</a>, e.g. qesapworker-prg4 or diesel, and verify that those workers can still execute multi-machine clusters if scheduled against those specific classes</li>
<li>Document that this is how one can ensure a worker is configured for multi-machine tests but not for production jobs</li>
</ul>
<a name="Out-of-scope"></a>
<h2 >Out of scope<a href="#Out-of-scope" class="wiki-anchor">¶</a></h2>
<ul>
<li>We don't strictly care about GRE tunnels here</li>
</ul>
openQA Project - action #128318 (Workable): [spike][timeboxed:20h] Current openQA+os-autoinst+dep...https://progress.opensuse.org/issues/1283182023-04-26T09:13:06Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>As the parent project about QAaaS progresses we should assess our expected efforts and risks about "openQA in SLE" ASAP for further planning. As according to hsehic openQA needs to be provided from pure SLE, i.e. no PackageHub, we should try what we can achieve in this regard by submitting packages and seeing the effect of that. Maybe some submissions can be directly accepted, maybe some need special treatment. Maybe SLE release managers tell us what processes we need to follow, which bugzilla or Jira tickets we need to create first or which contracts to sign with blood ;)</p>
<a name="Goal"></a>
<h2 >Goal<a href="#Goal" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>G1:</strong> All packages for current openQA+os-autoinst+dependencies have non-rejected (open or accepted) submit requests towards SLE</li>
<li><strong>G2:</strong> We know what process we need to follow to get openQA+os-autoinst+dependencies into SLE</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Identify all packages not yet in SLE: See the latest pipeline run within <a href="https://github.com/os-autoinst/scripts/actions/workflows/obs-list-dependencies.yml" class="external">https://github.com/os-autoinst/scripts/actions/workflows/obs-list-dependencies.yml</a></li>
<li>With a simple for-loop submit all packages from <a href="https://build.opensuse.org/project/show/devel:openQA:Leap:15.4" class="external">https://build.opensuse.org/project/show/devel:openQA:Leap:15.4</a> + <a href="https://build.opensuse.org/project/show/devel:openQA:tested" class="external">https://build.opensuse.org/project/show/devel:openQA:tested</a> (or openSUSE:Factory accordingly) to SLE (following <a href="https://en.opensuse.org/openSUSE:Maintenance_update_process" class="external">https://en.opensuse.org/openSUSE:Maintenance_update_process</a>)</li>
<li>Make sure the source is openSUSE:Factory to improve chances requests will be accepted (devel:openQA could be seen as a list of relevant packages in that sense)</li>
<li>React to comments/rejections in SRs accordingly</li>
<li>List all unattended SRs, i.e. the ones that have open review but apparently after some day receive no update</li>
<li>If you never worked with build.suse.de okurz suggests to use <a href="https://github.com/okurz/scripts/tree/master/isc" class="external">https://github.com/okurz/scripts/tree/master/isc</a></li>
<li>Submit request to <a href="https://build.suse.de/package/show/SUSE:SLE-15-SP4:GA/000product" class="external">https://build.suse.de/package/show/SUSE:SLE-15-SP4:GA/000product</a> to define a new SLE module for openQA</li>
</ul>
openQA Project - action #127037 (Workable): os-autoinst on SLE+packagehub size:Mhttps://progress.opensuse.org/issues/1270372023-03-31T13:23:07Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> os-autoinst is continuously built+tested+published on latest SLE+packagehub</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Wait for the outcome of <a class="issue tracker-4 status-3 priority-6 priority-high2 closed child" title="action: [spike][timeboxed:20h] Run openQA (webUI+worker) based on SLE to find out problems size:M (Resolved)" href="https://progress.opensuse.org/issues/127034">#127034</a> and <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Test os-autoinst+openQA against openSUSE:Backports:SLE-X in pull request OBS CI checks size:M (Resolved)" href="https://progress.opensuse.org/issues/127541">#127541</a></li>
<li>Refresh one's memory on how to publish on PackageHub</li>
<li>Find out where <a href="https://packagehub.suse.com/packages/os-autoinst" class="external">https://packagehub.suse.com/packages/os-autoinst</a> comes from
<ul>
<li>The package hub documentation suggests to develop packages in <em>some</em> project with <code>openSUSE:Backports:SLE-15</code> repository enabled.</li>
<li>Apparently there is <a href="https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP4/os-autoinst" class="external">https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP4/os-autoinst</a> and <a href="https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP5/os-autoinst" class="external">https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP5/os-autoinst</a> but it is not clear where those packages are developed at.
<ul>
<li>Looks like at this point packages are submitted directly from openSUSE:Factory from non-tools-team members, e.g. <a href="https://build.opensuse.org/request/show/941302" class="external">https://build.opensuse.org/request/show/941302</a>
<ul>
<li>We already submit to Factory via <a href="https://build.opensuse.org/package/show/devel:openQA:tested/os-autoinst" class="external">https://build.opensuse.org/package/show/devel:openQA:tested/os-autoinst</a>. So would it make sense to add the Backports repository here (to verify that packages are actually able to build against it)?</li>
<li>Maybe submit manually or automatically from Factory to openSUSE:Backports:SLE-15-SP4 and openSUSE:Backports:SLE-15-SP5 from our side?</li>
</ul></li>
</ul></li>
<li>What backport repos are actually relevant? Supposedly openSUSE:Backports:SLE-15-SP4 and openSUSE:Backports:SLE-15-SP5.
<ul>
<li>We decided to go for SP4 only for now.</li>
</ul></li>
</ul></li>
</ul>
QA - action #119176 (Workable): Automated alerts and reminders about SLO's for openqatests size:Mhttps://progress.opensuse.org/issues/1191762022-10-21T10:12:45Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Some tickets don't see regular updates, even with automated reminders in some cases. See <a href="https://progress.opensuse.org/projects/openqatests/wiki#SLOs-service-level-objectives" class="external">https://progress.opensuse.org/projects/openqatests/wiki#SLOs-service-level-objectives</a> for the documented workflows/goals. We assume processes are followed better if there is automation that reminds people about missed targets and makes it easier to understand what updates are missing.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> <strong>DONE</strong> SLOs are reflected in automated reminders</li>
<li><strong>AC2</strong>: <strong>DONE</strong> The first reminder is implemented based on the documented workflow</li>
<li><strong>AC3</strong>: The second reminder is known to update the priority automatically</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li><em>DONE:</em> Wait for <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Automated alerts and reminders about SLO's for openqatests (only one reminder) size:M (Resolved)" href="https://progress.opensuse.org/issues/116545">#116545</a></li>
<li><em>DONE:</em> Same as in queries for QA tools we likely should only look at the update time of tickets with no subtasks, e.g. see the definition of <a href="https://progress.opensuse.org/issues?query_id=542" class="external">https://progress.opensuse.org/issues?query_id=542</a>, to prevent cases like <a href="https://progress.opensuse.org/issues/113749#note-13" class="external">https://progress.opensuse.org/issues/113749#note-13</a> ff which is Urgent but hasn't been updated for a long time.</li>
<li><em>DONE:</em> Only write the same comment once -> <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Automated alerts and reminders about SLO's for openqatests (only one reminder) size:M (Resolved)" href="https://progress.opensuse.org/issues/116545">#116545</a></li>
<li>Research what has been done in <a class="issue tracker-4 status-3 priority-5 priority-high3 closed" title="action: Automated alerts and reminders about SLO's for openqatests size:M (Resolved)" href="https://progress.opensuse.org/issues/113797">#113797</a></li>
<li>Review and understand <a href="https://github.com/openSUSE/openqa-tests-backlog" class="external">https://github.com/openSUSE/openqa-tests-backlog</a> as well as <a href="https://github.com/openSUSE/backlogger" class="external">https://github.com/openSUSE/backlogger</a> and <a href="https://opensuse.github.io/openqa-tests-backlog/" class="external">https://opensuse.github.io/openqa-tests-backlog/</a></li>
<li>As the queries in <a href="https://github.com/openSUSE/openqa-tests-backlog/blob/main/queries.yaml#L5" class="external">https://github.com/openSUSE/openqa-tests-backlog/blob/main/queries.yaml#L5</a> are not named queries but defined in place we could just define a "grace period" for each query and only act automatically if not done already by users, e.g. don't remind on urgent tickets after 7 days but only 7+2 days</li>
<li>Follow the SLO about the suggestion of the "second reminder"</li>
</ul>
QA - action #112871 (Workable): obs_rsync_run Minion tasks fail with no error message size:Mhttps://progress.opensuse.org/issues/1128712022-06-22T11:01:40Zlivdywanliv.dywan@suse.com
<a name="Observation"></a>
<h3 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h3>
<p>Periodically <code>obs_rsync_run</code> Minion tasks fail like so:</p>
<pre><code>---
args:
- project: SUSE:SLE-15-SP3:Update:BCI
attempts: 1
children: []
created: 2022-06-20T13:16:56.947614Z
delayed: 2022-06-20T13:35:47.741627Z
expires: ~
finished: 2022-06-20T13:35:48.639216Z
id: 4720491
lax: 0
notes:
gru_id: 31834209
project_lock: 1
parents: []
priority: 100
queue: default
result:
code: 256
message: No message
retried: 2022-06-20T13:34:47.741627Z
retries: 18
started: 2022-06-20T13:35:47.983500Z
state: failed
task: obs_rsync_run
time: 2022-06-22T10:24:43.930467Z
worker: 767
</code></pre>
<p>There is no error message and I can't guess what might have caused this. There seems to be a code path that consumes errors without propagating them.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The jobs do not fail with unknown errors anymore</li>
</ul>
<a name="Suggestions"></a>
<h3 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h3>
<ul>
<li>Research the plugin and try to understand what the code is meant to achieve</li>
<li>Maybe just make the job not fail, if there is no real error and this is an expected condition (Minion jobs are only supposed to fail for real errors that need human intervention)</li>
<li><a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">https://github.com/os-autoinst/openqa-trigger-from-obs</a></li>
<li>Hypothesising the project in question was not configured, there is no files
<ul>
<li><a href="https://download.suse.de/ibs/SUSE:/ALP:/Source:/Standard:/1.0:/Staging:/V/images/iso/" class="external">https://download.suse.de/ibs/SUSE:/ALP:/Source:/Standard:/1.0:/Staging:/V/images/iso/</a> is empty</li>
<li>add a list of files to "notes" of the minion</li>
<li>Add a IBS/OBS/GitLab URL to the "notes"</li>
<li>Add stderr to "notes"</li>
</ul></li>
</ul>
openQA Infrastructure - action #76951 (Workable): Check if new firmware for kerosene (aka. power8...https://progress.opensuse.org/issues/769512020-11-04T06:06:17Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>New firmware might help to prevent qemu failing to run. If we find new firmware we could remove the parameters in os-autoinst again, see clone source ticket</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Read about context of the needed workaround <a class="issue tracker-4 status-3 priority-6 priority-high2 closed" title="action: 100% of powerpc tests incomplete auto_review:"(?s)Running on power8.*qemu-system-ppc64: Requested... (Resolved)" href="https://progress.opensuse.org/issues/75259">#75259</a></li>
<li>Currently <a href="https://kerosene-sp.qe.nue2.suse.org" class="external">https://kerosene-sp.qe.nue2.suse.org</a> lists FW840.00. Compare to other machines like diesel+petrol to see if there is a newer ASM version?</li>
<li>Look for new firmware for the machine, just search for new firmware on IBM web pages</li>
<li>Check if the new firmware means we do not need <a href="https://github.com/os-autoinst/os-autoinst/pull/1554" class="external">https://github.com/os-autoinst/os-autoinst/pull/1554</a> anymore, if yes, remove again, if no, remove again but add according settings to the machine settings in openQA, this is also what "adamw" did:</li>
</ul>
<pre><code>[04/11/2020 17:41:52] <adamw> okurz: i don't really know what the consequences of it are, but i tend to the idea that qemu wouldn't be trying to make it the default without reason :) i can ask some virt guys if you like
[04/11/2020 17:42:09] <adamw> okurz: but on the whole, yes, it seems to be it'd be more appropriate to put it in your templates rather than hardwire it into os-autoinst.
[04/11/2020 17:42:29] <adamw> that's what i was doing when we had the problem (i was setting an older machine type in our ppc64le Machine vars)
</code></pre>