openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-08-30T13:50:42ZopenSUSE Project Management Tool
Redmine 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 - 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>