openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-07T22:56:39ZopenSUSE Project Management Tool
Redmine openSUSE admin - communication #156874 (New): 2024-04-04 19:00 UTC: openSUSE Heroes meetinghttps://progress.opensuse.org/issues/1568742024-03-07T22:56:39Zcboltzsuse-beta@cboltz.de
<p>Where: <a href="https://meet.opensuse.org/heroes" class="external">https://meet.opensuse.org/heroes</a><br>
When: 2024-04-04 19:00 UTC / 20:00 CET<br>
Who: The openSUSE Heroes team and everybody else!</p>
<p>Topics:</p>
<ul>
<li>Questions and answers from the community</li>
<li>status reports about everything</li>
<li>review old tickets</li>
<li>(see/use checklist for additional topics)</li>
</ul>
openSUSE admin - tickets #135779 (Feedback): How's postfix mail queue doing?https://progress.opensuse.org/issues/1357792023-09-14T19:19:09Zluc14n0
<p>Yesterday - Wed Sep 13, 2023 -, or the day before, Icinga started showing an alarm (or maybe it was when I realized it, the alarm tells me it started 2d 4h ago) about Postfix mail queue been higher than its threshold for progress.i.o.o. Is this threshold there to avoid what exactly?</p>
<p><strong>progress.i.o.o</strong><br>
CRITICAL: <code>postfix mailq is 85 (threshold c = 50)</code></p>
<p>Other similar alarms that seem to be there for a while (or they come and go, I can't say right now):</p>
<p><strong>mailman3.i.o.o</strong></p>
<p>CRITICAL: <code>postfix mailq is 413 (threshold c = 50)</code></p>
<p><strong>openqa.i.o.o</strong></p>
<p>CRITICAL: <code>postfix mailq is 121 (threshold c = 50)</code></p>
openSUSE admin - tickets #122254 (New): Migrate away from login proxies to SSOhttps://progress.opensuse.org/issues/1222542022-12-20T20:31:20Zhellcphel@lcp.world
<p>It would be nice to slowly migrate over to using SSO instead of login proxies for logging into our infrastructure. The list below covers all of the services that still use login proxies. Some of them aren't under our jurisdiction, some may not even have login capabilities, but they still are behind login proxies, because why not (they shouldn't be, get them out of there).</p>
openSUSE admin - tickets #117166 (New): Archive redirecthttps://progress.opensuse.org/issues/1171662022-09-23T14:11:12Zyecril71plgiecrilj@stegny.2a.pl
<p>Kiedy pakiet staje się niedostępny do pobrania z repozytorium Tumbleweed i przenosi się do archiwum, klient, próbujący i pobrać, otrzymuje wynik 404 (zasób nie znaleziony), którego oprogramowanie pobierające pakiety nie umie dobrze obsłużyć. Omawiając zgłoszenie błędu 1203303, doszliśmy do wniosku, że w takiej sytuacji serwer powinien zwracać przekierowanie stałe do odpowiedniego pakietu, znajdującego się w archiwum.</p>
openQA Tests - action #87791 (New): [s390x] Extend test suite for openSUSE Tumbleweed/s390xhttps://progress.opensuse.org/issues/877912021-01-15T09:42:58Zdimstardimstar@opensuse.org
<p>as the openSUSE s390x Tumbleweed port is back in 'rolling mode', and the general openQA issues have been resolved, we should start to enable more of the test suites that make sense for openSUSE Tumbleweed on s390x.</p>
<p>The goal should be to get good coverage, comparable to what we test on x86_64 AND to make sure that most of what goes to SLE at any point is already pre-tested on Tumbleweed, causing less disruption when SLE is being forked from TW again.</p>
<ul>
<li>(iterative) Identify tests to be enabled on s390x</li>
<li>Enable those identified tests in the Tumbleweed dev group on openQA, to not block the product with non-functional tests.</li>
<li>Once tests are stable, move them to the Tumbleweed s390x group</li>
<li>If needed, work with Ihno on changing / extending the configuration on the s390 farm for openQA/openSUSE</li>
</ul>
openQA Tests - action #43655 (Workable): [qe-core][functional] Increase robustness of using bootl...https://progress.opensuse.org/issues/436552018-11-11T16:03:17Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p><a class="issue tracker-4 status-3 priority-6 priority-high2 closed" title="action: [sle][functional][u][medium][tools][sporadic] test fails in welcome - typos in kernel boot parame... (Resolved)" href="https://progress.opensuse.org/issues/40670">#40670</a> showed that typing in the bootloader screen can impede the robustness. Using a "info-file" might be more robust.</p>
<a name="Further-information"></a>
<h2 >Further information<a href="#Further-information" class="wiki-anchor">¶</a></h2>
<p>Syntax of info file:</p>
<ul>
<li>Each parameter goes in one line.</li>
<li>Key and value are separated by colon plus white space ': '.</li>
</ul>
<a name="Sample"></a>
<h4 >Sample:<a href="#Sample" class="wiki-anchor">¶</a></h4>
<pre><code>ssh: 1
sshpassword: nots3cr3t
</code></pre>
<a name="Usage-from-bootloader"></a>
<h4 >Usage from bootloader<a href="#Usage-from-bootloader" class="wiki-anchor">¶</a></h4>
<pre><code>info=http://$WORKER_IP/files/info
</code></pre>
<a name="References"></a>
<h4 >References<a href="#References" class="wiki-anchor">¶</a></h4>
<ul>
<li><a href="https://en.opensuse.org/SDB:Linuxrc#Parameter_Reference" class="external">https://en.opensuse.org/SDB:Linuxrc#Parameter_Reference</a>)</li>
<li><a href="https://www.suse.com/documentation/sles11/book_autoyast/data/sect1_appendix_book_autoyast.html" class="external">https://www.suse.com/documentation/sles11/book_autoyast/data/sect1_appendix_book_autoyast.html</a></li>
</ul>
openQA Project - action #20162 (New): Create a group `openqa` during installationhttps://progress.opensuse.org/issues/201622017-06-29T15:24:48ZSLindoMansillaslindomansilla@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>As an openQA test developer, I want that the package openQA installs a group for the files that are accesed by user geekotest and _openqa-worker to have an easier way to access and modify the files installed by the package openQA without using the root user and without loosing the my file permissions each time that I install an update of the package.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The package openQA create during installation a group named <code>openqa-test-developers</code></li>
<li><strong>AC2:</strong> The files and directories listed bellow are owned by the group <code>openqa-test-developers</code>, they have read-write permission for the group owner and have the <code>gid</code> set.
<ul>
<li><code>/var/lib/openqa/pool/</code></li>
<li><code>/var/lib/openqa/share/factory/</code></li>
<li><code>/var/lib/openqa/share/tests/</code></li>
</ul></li>
</ul>
<a name="Tasks"></a>
<h2 >Tasks<a href="#Tasks" class="wiki-anchor">¶</a></h2>
<ol>
<li>Modify the installation/specfile to create a group named <code>openqa-test-developers</code></li>
<li>Install the files and directories listed on AC2 with group owner <code>openqa-test-developers</code>,</li>
<li>and add read-write permissions to them,</li>
<li>and add the gid bit to them.</li>
</ol>
<a name="Further-information"></a>
<h2 >Further information<a href="#Further-information" class="wiki-anchor">¶</a></h2>
<ul>
<li><a href="https://build.opensuse.org/package/show/Base:System/system-users" class="external">https://build.opensuse.org/package/show/Base:System/system-users</a></li>
<li><a href="https://build.opensuse.org/package/view_file/Base:System/system-users/system-user-wwwrun.conf" class="external">https://build.opensuse.org/package/view_file/Base:System/system-users/system-user-wwwrun.conf</a></li>
<li><a href="https://www.commandlinux.com/man-page/man5/sysusers.d.5.html" class="external">https://www.commandlinux.com/man-page/man5/sysusers.d.5.html</a></li>
</ul>