openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-08-21T13:18:15ZopenSUSE Project Management Tool
Redmine Jump 15.2 - action #70393 (New): gdb fails to build on non-intel arches since fpc is build only f...https://progress.opensuse.org/issues/703932020-08-21T13:18:15Zlkocmanlubos.kocman@suse.com
<p><a href="https://build.opensuse.org/package/show/openSUSE:Jump:15.2/gdb" class="external">https://build.opensuse.org/package/show/openSUSE:Jump:15.2/gdb</a></p>
<p>fpc rpms are produced only on x86_64 <a href="https://build.opensuse.org/package/binaries/openSUSE:Backports:SLE-15-SP2/fpc/standard" class="external">https://build.opensuse.org/package/binaries/openSUSE:Backports:SLE-15-SP2/fpc/standard</a></p>
<p>Just a note that openSUSE:Jump:15.2 has a submit request redirection in place therefore submission against openSUSE:Jump:15.2 fpc should target it correctly against backports.</p>
Jump 15.2 - action #70303 (New): Disable ignore_missing_packages bit in the ftp tree buildhttps://progress.opensuse.org/issues/703032020-08-20T11:09:57Zmlin7442mlin@suse.com
<p>Currently Jump have enabled ignore_missing_packages="true" in the ftp tree build for workaround package not found issue eg. scalapack-openmpi3, etc., we need to disable it before release and to ensure all RPMs was there, or filter them out from NON_FTP_PACKAGES list(bad choice though).</p>
Jump 15.2 - action #70300 (New): Create pool repository for SUSE:SLE-15-SP2:Updatehttps://progress.opensuse.org/issues/703002020-08-20T10:58:11Zmlin7442mlin@suse.com
<p>There are new maint. update appeared in SUSE:SLE-15-SP2:Update, we should add pool repository to SUSE:SLE-15-SP2:Update project and sync RPMs from IBS to there. And maybe we should uses this pool to instead of SUSE:SLE-15-SP2:GA pool in Jump:15.2?</p>
Jump 15.2 - action #70297 (New): Move to openSUSE:Backports:SLE-15-SP2:Update, openSUSE:Backports...https://progress.opensuse.org/issues/702972020-08-20T10:53:52Zmlin7442mlin@suse.com
<p>Jump:15.2 should uses openSUSE:Backports:SLE-15-SP2:Update to instead of openSUSE:Backports:SLE-15-SP2:GA since openSUSE:Backports:SLE-15-SP2:GA development is all done and was locked.<br>
Any further package update will go to openSUSE:Backports:SLE-15-SP2:Update, ie. any fix for Jump via Backports will appeared in :Update rather than :GA.</p>
MicroOS 15.2 - action #68770 (New): document how to integrate with health-checkerhttps://progress.opensuse.org/issues/687702020-07-08T13:07:04Zlnussellnussel@suse.com
<p>document how to write a health-checker plugin for your own service</p>
MicroOS 15.2 - action #68767 (New): Document how to create containers for MicroOShttps://progress.opensuse.org/issues/687672020-07-08T12:53:22Zlnussellnussel@suse.com
<p>Documentation is needed on how to</p>
<ul>
<li>deploy containers on MicroOS</li>
<li>create custom containers for MicroOS</li>
</ul>
MicroOS 15.2 - action #68746 (New): improve raspberry pi wiki pageshttps://progress.opensuse.org/issues/687462020-07-08T11:14:29Zlnussellnussel@suse.com
<p>Raspberry Pi support deserves some extra attention wrt documentation. I'd like to link to those pages when clicking on the raspberry pi logo in the download page.</p>
<p>Right now there are pages for each rpi model with differnt kinds of documentation, some of them outdated:</p>
<p><a href="https://en.opensuse.org/HCL:Raspberry_Pi" class="external">https://en.opensuse.org/HCL:Raspberry_Pi</a><br>
<a href="https://en.opensuse.org/HCL:Raspberry_Pi2" class="external">https://en.opensuse.org/HCL:Raspberry_Pi2</a><br>
<a href="https://en.opensuse.org/HCL:Raspberry_Pi3" class="external">https://en.opensuse.org/HCL:Raspberry_Pi3</a><br>
<a href="https://en.opensuse.org/HCL:Raspberry_Pi4" class="external">https://en.opensuse.org/HCL:Raspberry_Pi4</a></p>
<p>Also there are some nice articles that document extra attachments, especially the RTC one is important for MicroOS:<br>
<a href="https://en.opensuse.org/HCL:Raspberry_Pi3_RTC" class="external">https://en.opensuse.org/HCL:Raspberry_Pi3_RTC</a></p>
<p>My suggestion would be to</p>
<ul>
<li>[ ] rename HCL:Raspberry_Pi to HCL:Raspberry_Pi1</li>
<li>[ ] create a new HCL:Raspberry_Pi that explains the available boards and their difference (RPi1 is not really supported nor recommended anymore AFAIK)</li>
<li>[ ] identify sections common to several RPi versions and move each section to a separate subpage. Include the subpage in the board specific pages</li>
<li>[ ] create a category for the extra hardware documentation so there's an easy overview</li>
<li>[ ] find a way to indicate which board/OS combination this such a document applies to resp was tested with (similar to "tested on" in <a href="https://en.opensuse.org/SDB:System_upgrade" class="external">https://en.opensuse.org/SDB:System_upgrade</a>)</li>
<li>[ ] create board specific known issues pages to be able to track stuff like <a href="https://bugzilla.opensuse.org/show_bug.cgi?id=1140688" class="external">https://bugzilla.opensuse.org/show_bug.cgi?id=1140688</a></li>
</ul>
Jump 15.2 - action #67366 (New): [containers] test fails in docker_runc "Error exporting contain...https://progress.opensuse.org/issues/673662020-05-27T15:38:47Zmichel_mnonormand@linux.vnet.ibm.com
<p>test fails in docker_runc "Error exporting container" for ppc64le Leap15.2</p>
<p>failing command: 'docker export $(docker create busybox) | tar -C rootfs -xvf -' <br>
at /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/console/docker_runc.pm line 40.</p>
<p>failing output (manually copied from captured screen):</p>
<pre><code>Unable to find image 'busybox:latest' locally
latest: Pullingfrom library/busybox
368841f1202b: Pulling fs layer
368841f1202b: Verifying Checksum
368841f1202b: Download complete
368841f1202b: Pull complete
Digest: sha256:836945da1f3afe2cfff376d379852bbb82e0237cb2925d53a13f53d6e8a8c48c
Status: Downloaded ,ew image for busybox:latest
Error response from daemon: Error exporting container 139b131c1a521691017a4780015abf8686f05cb4d288141fc593633188d168f7: error processing tar file: docker-tar: relocation error: /lib64/libnss_files.so.2: symbol __libc_readline_unlocked, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
:exit status 127
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
</code></pre>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario opensuse-15.2-DVD-ppc64le-extra_tests_textmode_containers@ppc64le fails in<br>
<a href="https://openqa.opensuse.org/tests/1279017/modules/docker_runc/steps/30" class="external">docker_runc</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: dheidler. Extra tests about CLI software in container module</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.opensuse.org/tests/1279017" class="external">263.1</a> (current job)<br>
This is the first trial on openQA for ppc64le Leap15.2</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (or more recent) no trial for Leap 15.2 ppc64le Build 263.1</p>
<p>There were no failure for TW ppc64le:<br>
<a href="https://openqa.opensuse.org/tests/1276870#step/docker_runc/1" class="external">https://openqa.opensuse.org/tests/1276870#step/docker_runc/1</a> </p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensuse&flavor=DVD&machine=ppc64le&test=extra_tests_textmode_containers&version=15.2" class="external">latest</a></p>
Jump 15.2 - action #66274 (New): Numerous Packages in openSUSE:Jump:15.2 are outdated compared to...https://progress.opensuse.org/issues/662742020-04-30T10:03:43Zeeicheich@suse.com
<p>Numerous packages in openSUSE:Jump:15.2 are outdated compared to SUSE:SLE-15-SP2:GA.<br>
They seem to resemble the state of Leap 15.2 5 month ago. One example is '<a href="https://build.opensuse.org/package/show/openSUSE:Jump:15.2/scalapack" class="external">scalapack</a>' while <a href="https://build.opensuse.org/package/show/SUSE:SLE-15-SP2:GA/scalapack" class="external">scalapack on SLE-15-SP2</a> shows several updates since - the oldest almost 5 months ago.<br>
The problem seems to originate from Leap 15.2 which has been synced last 11 months ago <a href="https://build.opensuse.org/package/show/openSUSE:Leap:15.2/scalapack" class="external">package</a>.<br>
This is not the case for all packages: take for instances 'mrsh' which was updated on SLE-15-SP2 very recently. This is current in <a href="https://build.opensuse.org/package/show/openSUSE:Jump:15.2/mrsh" class="external">Jump</a>.</p>
MicroOS 15.2 - action #65762 (New): enable package list generatorhttps://progress.opensuse.org/issues/657622020-04-17T08:36:46Zlnussellnussel@suse.comJump 15.2 - action #65525 (New): Initial Project setuphttps://progress.opensuse.org/issues/655252020-04-09T14:20:40Zlkocmanlubos.kocman@suse.com
<p>The current Leap setup will no longer work with newly proposed changes.The project structure (rings etc.) have to be reworked so we can build on top of SLE binaries.</p>
invisAD-setup - action #63634 (New): We should publish a list with the expiry dates of all VPN cl...https://progress.opensuse.org/issues/636342020-02-20T07:36:54Zflaccostefan@invis-server.org
<p>The VPN client certs we create have a 24 month time to live. Actually the users have no information about this, the don't know when there clients certs epxire. More than once this caused problems in practice.</p>
invisAD-setup - action #54389 (New): DNS-Updates via DHCP-Server should be possiblehttps://progress.opensuse.org/issues/543892019-07-18T06:37:55Zflaccostefan@invis-server.org
<p>In our setup every try to update DNS-Records dynamically fails:</p>
<p>Unable to add forward map from LANCOM_884_VOIP.baettenhausen.local to 192.168.1.205: REFUSED</p>
<p>This should be possible.</p>
<p>How to setup: <a href="https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Setting_up_BIND" class="external">https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Setting_up_BIND</a></p>
invis-sub-setup - action #46718 (In Progress): Create a setup-script for invis-sub-serverhttps://progress.opensuse.org/issues/467182019-01-26T15:49:46Zflaccostefan@invis-server.org
<p>Major steps to realize with this Script:</p>
<ol>
<li>Establish an openVPN connection to the main invis-server</li>
<li>Join the Domain as a "Read Only Domain Controller" (RODC)</li>
<li>Setup sssd</li>
<li>Setup local samba shares</li>
<li>realize (owncloud based) data synchronization between sub and main-server</li>
</ol>
<p>Some of these steps are already realized inside the joininvis-script from the invisAD-client package.</p>
<p>Joining the domain as a rodc (<a href="https://de.wikipedia.org/wiki/Read_Only_Domain_Controller" class="external">https://de.wikipedia.org/wiki/Read_Only_Domain_Controller</a>) instead of a simple member server seems to be the better way. In a productive environment at one of our custumers I tried to realize a subsidiary server as a simple member-server. Nearly every time the vpn-connection caused by a not very stable internet-connection, I had to rejoin the domain with the sub-server to give the sub-users access to their local samba-shares. </p>
invisAD-setup - action #37414 (In Progress): Implementation of SingleSignOnhttps://progress.opensuse.org/issues/374142018-06-15T07:57:23Zflaccostefan@invis-server.org
<p>Step by step we should implement SSO for as much applications as possible. First step would be to fit the apache2 setup for SSO.</p>