openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-07-06T07:33:49ZopenSUSE Project Management Tool
Redmine openSUSE admin - tickets #68657 (Closed): swish-e indexing broken because of wrong config permiss...https://progress.opensuse.org/issues/686572020-07-06T07:33:49Zlrupp
<p>Today I wondered why the search.cgi on lists.opensuse.org did not work. </p>
<p>Looks like the index file got somehow broken, which might be a result of the latest upgrade of the machine.</p>
<p>During further investigation/trying to rebuild the index, I noticed that the configuration file /etc/swish-e.conf was owned by root:root with permissions 640. This resulted in the user "archive" not being able to read the configuration any longer and the cron jobs were failing. Looks like they failed silently?</p>
<p>I fixed the permissions now and started to run a full reindex in a screen session of user "archive" (which will take some time, I guess). </p>
<p>So the original issue should be fixed - fixable now (the cron jobs should also be able to start working now).</p>
<p>BUT: we should think about a way to monitor the indexing somehow. This needs investigation.</p>
openSUSE admin - tickets #68512 (Closed): Adjust login.template pages to new layouthttps://progress.opensuse.org/issues/685122020-06-29T13:15:47Zlrupp
<p>Our current login pages are still using the old bento layout. </p>
<p>Time to refresh them...</p>
openSUSE admin - tickets #67600 (Resolved): IPv6 network migrationhttps://progress.opensuse.org/issues/676002020-06-02T15:16:06Zlrupp
<p>As SUSE is becoming independent, some networks need to be re-arranged. One of them is the IPv6 network.</p>
<p>The old IPv6 network range (2620:113:80c0:8000::/50) in Nuremberg will go away end of the month. openSUSE still has some machines using this old IPv6 address since 2012. These machines need to be switched to the new IPv6 range (2001:67c:2178::/50), which is already in place and can be used directly.</p>
openSUSE admin - tickets #67444 (Resolved): IPv4 network renumbering of machines in Provohttps://progress.opensuse.org/issues/674442020-05-29T08:44:53Zlrupp
<p>SUSE is getting a new ISP in Provo - and a new set of external IP addresses. </p>
<p>So far, openSUSE got 91.193.113.64/27 assigned, which allows the usage of 32 IPv4 addresses. There is currently no IPv6 available in the new network, but people are working on this.</p>
<p>Default Gateway for all machines will be 91.193.113.94</p>
<p>Please have a look at the checklist for affected machines and their (old) => new IP address assignments.</p>
<p>The new network is protected by a stateful firewall, managed by SUSE-IT. The attached pdf contains the services and ports that are currently requested.</p>
openSUSE Marketing - action #67435 (In Progress): Nice and shiny 404 pagehttps://progress.opensuse.org/issues/674352020-05-28T22:09:28Zlrupp
<p><a href="https://www.opensuse.org/foo" class="external">https://www.opensuse.org/foo</a> and similar, broken URLs are currently showing a standard 404 page.</p>
<p>We should have a nicer 404 with some additional information for people (like links to search engines?). Like a grumpy Geeko, who tried to find something which is not there - or similar.</p>
<p>In addition, other error pages (like 503 - Geeko unavailable) or maintenance pages might also be helpful.</p>
openSUSE admin - tickets #67195 (Closed): Wiki does not show news feedhttps://progress.opensuse.org/issues/671952020-05-24T19:55:55Zlrupp
<p><a href="https://en.opensuse.org/Portal:Distribution" class="external">https://en.opensuse.org/Portal:Distribution</a> (resp. <a href="https://en.opensuse.org/Portal:Distribution/News" class="external">https://en.opensuse.org/Portal:Distribution/News</a> ) is not showing any news, only:<br>
<code>Failed to load RSS feed from https://news.opensuse.org/category/distribution/feed/</code></p>
openSUSE admin - tickets #65810 (Resolved): Update Redmine to stable, supported versionhttps://progress.opensuse.org/issues/658102020-04-19T11:58:21Zlrupp
<p>The new Redmine instance here is running version 3.4.12.stable - upstream has released version 3.4.13 in December 2019.</p>
<p>In general, upstream declares only the latest 4.0.7 and 4.1.1 versions (original released.in December as well, but updated in April 2020) as "stable", so progress.opensuse.org - while thankfully updated - is already out of service again.</p>
<p>I like to request:</p>
<ul>
<li>Update the current instance to at least 3.4.13</li>
<li>Work on upgrade to 4.0 or 4.1 on a new test instance</li>
</ul>
openSUSE admin - tickets #65807 (Closed): Check for unneeded VMshttps://progress.opensuse.org/issues/658072020-04-19T11:47:26Zlrupp
<p>After the latest upgrade rounds (progress or gcc as example) it should be time to check the currently running machines and their services - and shut down unneeded hosts to reduce the needed administration.</p>
<p>Goal for this ticket is a list of candidate machines to be shut down. </p>
<p>This might be machines that are obsolete now with new machines in place - or machines that are up and running since a while (to be setup as replacements) but not used/worked on since more than a month.</p>
<p>So we might end up in two categories:</p>
<ul>
<li>Decommission machines (remove completely)</li>
<li>Delayed machines (needed, but no time/no volunteers to work on)</li>
</ul>
openSUSE admin - tickets #63979 (Resolved): UTF-8 problems with jekyllhttps://progress.opensuse.org/issues/639792020-02-28T15:02:33Zlrupp
<p>Please have a look at <a href="https://news.opensuse.org/2011/06/09/world-ipv6-day-results/" class="external">https://news.opensuse.org/2011/06/09/world-ipv6-day-results/</a></p>
<p>Nürnberg != Nürnberg</p>
<p>This is just an example I stumbled over. There might be more. IMHO something that should be fixable via "sed" in the source now. </p>
openSUSE Marketing - action #62744 (Resolved): Vote for openSUSEhttps://progress.opensuse.org/issues/627442020-01-29T00:48:58Zlrupp
<p>I know: voting is lame and there are 1000 votes available each day. But:</p>
<p><a href="https://opensource.com/article/20/1/favorite-linux-distribution" class="external">https://opensource.com/article/20/1/favorite-linux-distribution</a></p>
<p>Maybe someone can spread the word to our channels?</p>
openQA Infrastructure - action #62666 (New): Move openqa.opensuse.org into opensuse private networkhttps://progress.opensuse.org/issues/626662020-01-24T19:46:45Zlrupp
<p>Dear openQA admins</p>
<p>We are currently working towards a better separation of SUSE and openSUSE machines. This should finally allow more community contributors to be able to jump in and either help with the current infrastructure or deploy and develop new stuff - independent from any SUSE influence.</p>
<p>There are just a few machines left to finish this migration - and your openQA setup is one of it.</p>
<p>So it like to ask if you could consider to move your current admin machine (ariel) from the "SUSE owned" private network 192.168.254.0/24 into the "openSUSE Heroes owned" network 192.168.47.0/24?</p>
<p>Details:</p>
<p>Current situation:</p>
<ul>
<li>192.168.254.15 is the current IP of your host in this network</li>
<li>traffic to your webservice <a href="https://openqa.opensuse.org/">https://openqa.opensuse.org/</a> gets routed via a HAproxy pair from the internet to this interface</li>
<li>your machine currently reaches out to other networks ("the internet") via a gateway in this network</li>
<li>you access this machine (and the machines behind it) via a port forwarding rule </li>
</ul>
<p>New, proposed situation:</p>
<ol>
<li>47.78 will be the new IP of your host in the new network (this might change if you wait too long, but don't worry, we have enough IP addresses at the moment ;-)</li>
<li>traffic to your webservice <a href="https://openqa.opensuse.org/">https://openqa.opensuse.org/</a> gets routed via another HAproxy pair from the internet to this interface</li>
<li>your machine will reach out to other networks ("the internet") via another gateway in this network</li>
<li>you access this machine (and the machines behind it) via a dedicated openVPN, which is reachable from everywhere</li>
</ol>
<p>Especially the last point might be interesting for you, as all the others are more or less just cosmetic.</p>
<p>This openVPN is the "openSUSE heroes" openVPN, which has in general nothing to do with anything you might currently use. The openSUSE Heroes try to have security in mind with everything they do - and therefor decided to trust only themselves and their loved distribution. So they setup an own authentication provider and a this dedicated VPN to combine security, maintainability and effectiveness. The result are dedicated accounts for everyone who works on openSUSE related infrastructure - while including the ability to work from wherever he is at the moment. All you need is your account and the openVPN certificates for this. If you agree to get switched, I currently see two possible solutions to work on the infrastructure for openQA:</p>
<ol>
<li>use a jumphost, which has to be inside the SUSE network </li>
<li>get dedicated accounts and VPN credentials and use them</li>
</ol>
<p>Both options might be used in parallel (while - from a security point - only using the 2nd option would be preferred), which hopefully will not become too complicated for you. </p>
<p>Benefit: if there will be community members, who like to help and work on openQA, they could easily be allowed to do so.</p>
<p>Alternatively, you can decide to "stay on the SUSE side", which will imply no change of your current workflows. You might be the only openSUSE infrastructure project staying under SUSE-IT umbrella in this case - but this option clearly exists.</p>
<p>With kind regards,<br>
Lars <em>on behalf of the openSUSE heroes</em></p>
<p>PS: I tried to add everyone as "watcher" to this ticket, who has currently an account on ariel. I clearly missed some and apologize for this, but I could not really figure out everyone's "ariel login" <-> "bugzilla login" mapping. </p>
openSUSE admin - tickets #60479 (Closed): Cleanup openSUSE:Infrastructure project in OBShttps://progress.opensuse.org/issues/604792019-12-02T09:49:58Zlrupp
<p><a href="https://build.opensuse.org/project/show/openSUSE:infrastructure" class="external">https://build.opensuse.org/project/show/openSUSE:infrastructure</a> is currently in a not so good shape. <br>
I will try to get this cleaned up and hopefully some failing packages fixed.</p>
openSUSE admin - tickets #60419 (Closed): status.opensuse.org needs dist-upgradehttps://progress.opensuse.org/issues/604192019-11-28T16:31:26Zlrupp
<p>status2.opensuse.org is already upgraded to Leap 15.1. status1.opensuse.org (which is the main status.opensuse.org machine) should follow in the next weeks...</p>
openSUSE admin - tickets #59966 (Closed): DNS cleanuphttps://progress.opensuse.org/issues/599662019-11-18T14:24:41Zlrupp
<p>The .opensuse.org domain needs some cleanup. Will start doing this...</p>
openSUSE admin - tickets #59942 (Closed): IRC bot does not sent monitoring notifications any longerhttps://progress.opensuse.org/issues/599422019-11-18T09:23:44Zlrupp
<p>The current IRC bot on #<a href="mailto:opensuse-admin@irc.opensuse.org">opensuse-admin@irc.opensuse.org</a> does not forward notifications from the monitoring any longer. </p>
<p>Looks like an issue with the "latest" switch form Python2 to Python3.</p>
<p>=> needs investigation</p>