<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:35:01 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-3566] not strictly a lustre problem, but git not working?</title>
                <link>https://jira.whamcloud.com/browse/LU-3566</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I tried to go to &lt;a href=&quot;http://git.whamcloud.com/fs/lustre-release.git&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://git.whamcloud.com/fs/lustre-release.git&lt;/a&gt; on/via &lt;a href=&quot;https://wiki.hpdd.intel.com/display/PUB/Lustre+Development&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki.hpdd.intel.com/display/PUB/Lustre+Development&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;but that doesn&apos;t seem to work?&lt;/p&gt;

&lt;p&gt;&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/check.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Initial code complete&lt;br/&gt;
&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/check.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Change testing is complete&lt;br/&gt;
&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/information.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Documentation changes made - N/A&lt;br/&gt;
&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/check.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Review done&lt;br/&gt;
&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/check.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Demo/review/approval from Andi&lt;br/&gt;
&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/check.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Changes are communicated&lt;br/&gt;
&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/check.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Changes are completed in production&lt;/p&gt;</description>
                <environment></environment>
        <key id="19707">LU-3566</key>
            <summary>not strictly a lustre problem, but git not working?</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="joshua">Joshua Kugler</assignee>
                                    <reporter username="ronc">Ron Croonenberg</reporter>
                        <labels>
                            <label>no_restart</label>
                    </labels>
                <created>Mon, 8 Jul 2013 16:52:06 +0000</created>
                <updated>Thu, 14 Jun 2018 21:41:36 +0000</updated>
                            <resolved>Thu, 19 Jun 2014 18:55:42 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="61898" author="rread" created="Mon, 8 Jul 2013 17:32:00 +0000"  >&lt;p&gt;I updated the wiki page to point to correct link for the Lustre repo: &lt;a href=&quot;http://git.hpdd.intel.com/?p=fs/lustre-release.git&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://git.hpdd.intel.com/?p=fs/lustre-release.git&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="61942" author="adilger" created="Tue, 9 Jul 2013 16:35:48 +0000"  >&lt;p&gt;I thought we had DNS forwarding enabled for these hosts?&lt;/p&gt;

&lt;p&gt;Also it makes sense to make a pass through the wiki and update URLs to the new site.&lt;/p&gt;</comment>
                            <comment id="61948" author="rread" created="Tue, 9 Jul 2013 16:53:49 +0000"  >&lt;p&gt;DNS is forwarding, but I&apos;m seeing error 403 pages when I use short pathnames like &lt;a href=&quot;http://git.whamcloud.com/fs/lustre-relelase.git&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://git.whamcloud.com/fs/lustre-relelase.git&lt;/a&gt;, though it does work if you use the full &lt;a href=&quot;http://git.whamcloud.com/?p=fs/lustre-release.git&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://git.whamcloud.com/?p=fs/lustre-release.git&lt;/a&gt;.   So I&apos;m guessing this is actually an apache redirect is issue.&lt;/p&gt;
</comment>
                            <comment id="61984" author="joshua" created="Tue, 9 Jul 2013 23:11:22 +0000"  >&lt;p&gt;This is odd.  The configuration was copied from our old host at Rackspace to our new machine at Intel.  If it doesn&apos;t work now, it most likely didn&apos;t work before...unless there was an additional variable we don&apos;t know about.&lt;/p&gt;</comment>
                            <comment id="61986" author="rread" created="Tue, 9 Jul 2013 23:38:34 +0000"  >&lt;p&gt;I&apos;m pretty sure the simpler URLs worked at one point, but don&apos;t recall when I last tried to use them. It certainly possible they might have been broken before the server migration.&lt;/p&gt;</comment>
                            <comment id="62167" author="joshua" created="Fri, 12 Jul 2013 01:11:19 +0000"  >&lt;p&gt;I just modified my /etc/hosts to point to the old rackspace site, and confirmed that &lt;a href=&quot;http://git.whamcloud.com/fs/lustre-release.git/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://git.whamcloud.com/fs/lustre-release.git/&lt;/a&gt; does in fact work.  I&apos;ll have to find out why.&lt;/p&gt;

&lt;p&gt;One thing that may be in play here is the fact that we were running git(web) 1.8 on Rackspace, and when we migrated to the Intel environment, on SLES11SP1, that took us back to git(web) 1.6.&lt;/p&gt;</comment>
                            <comment id="62201" author="rread" created="Fri, 12 Jul 2013 15:53:07 +0000"  >&lt;p&gt;That&apos;s interesting we had to downgrade.  Hopefully we won&apos;t run into any compatibility issues with gerrit, but it should be ok since it&apos;s readonly.&lt;/p&gt;</comment>
                            <comment id="86056" author="joshua" created="Sat, 7 Jun 2014 00:55:49 +0000"  >&lt;p&gt;I&apos;ve been doing some debugging on this, and this is what I have uncovered so far:&lt;/p&gt;

&lt;p&gt;The recommended &lt;tt&gt;RewriteRule&lt;/tt&gt; is this:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;RewriteRule ^/(.*\.git/(?!/?(HEAD|info|objects|refs)).*)?$ /gitweb%{REQUEST_URI}  [L,PT]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;But that generates 403 errors when trying to access URLs such as &lt;tt&gt;&lt;a href=&quot;http://git-stage.hpdd.intel.com/fs/lustre-release.git&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://git-stage.hpdd.intel.com/fs/lustre-release.git&lt;/a&gt;&lt;/tt&gt; as we know. If I modify the &lt;tt&gt;RewriteRule&lt;/tt&gt; and take out the slash after &lt;tt&gt;.git&lt;/tt&gt; like so:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;RewriteRule ^/(.*\.git(?!/?(HEAD|info|objects|refs)).*)?$ /gitweb%{REQUEST_URI}  [L,PT]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;The web site works fine, and I can clone via HTTP&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/star_yellow.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;.&lt;/p&gt;

&lt;p&gt;Not sure why the recommended configuration does not work. Does not appear to be a version thing, as git 1.8 generates the same behavior.&lt;/p&gt;

&lt;p&gt;&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/star_yellow.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; We do not support git clones via HTTP due to not running to post-commit hooks needed to make HTTP clones work. We might want to disable the ability to clone. It does work, but the clone one gets from an HTTP clone can be out of date.&lt;/p&gt;</comment>
                            <comment id="86872" author="joshua" created="Tue, 17 Jun 2014 22:39:49 +0000"  >&lt;p&gt;Testing done, and working.  Config file diff here:&lt;br/&gt;
The additional host name would not be inserted, obviously.&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;--- git.whamcloud.com.conf.prod 2014-06-17 22:21:51.000000000 +0000
+++ git.whamcloud.com.conf      2014-06-17 22:47:56.000000000 +0000
@@ -1,21 +1,34 @@
+&amp;lt;Directory /data/srv/source&amp;gt;
+       Options FollowSymLinks
+       Order deny,allow
+       Allow from all
+&amp;lt;/Directory&amp;gt;
+
+&amp;lt;Directory /usr/local/&amp;gt;
+       Order deny,allow
+       Allow from all
+&amp;lt;/Directory&amp;gt;
+
 &amp;lt;VirtualHost *:80&amp;gt;
        ServerName      git.whamcloud.com
        ServerAlias     git
        ServerAlias git.hpdd.intel.com
+       ServerAlias git-stage.hpdd.intel.com
        DocumentRoot /data/srv/source/git.whamcloud.com
        SetEnv GITWEB_CONFIG /etc/gitweb.conf
        RewriteEngine on
        RewriteRule ^/$                                            /gitweb [PT]
-       RewriteRule ^/(.*\.git/(?!/?(HEAD|info|objects|refs)).*)?$ /gitweb%{REQUEST_URI}  [L,PT]
+       RewriteRule ^/(.*\.git(?!/?(HEAD|info|objects|refs)).*)?$ /gitweb%{REQUEST_URI}  [L,PT]
 
        # Aliases
-       ScriptAlias /gitweb             /usr/share/git-web/gitweb.cgi
-       Alias       /gitweb.css         /usr/share/git-web/gitweb.css
-       Alias       /gitweb.js          /usr/share/git-web/gitweb.js
-       Alias       /git-logo.png       /usr/share/git-web/git-logo.png
-       Alias       /git-favicon.png    /usr/share/git-web/git-favicon.png
+       ScriptAlias /gitweb             /usr/local/share/gitweb/gitweb.cgi
+       Alias       /gitweb.css         /usr/local/share/gitweb/static/gitweb.css
+       Alias       /static/gitweb.js   /usr/local/share/gitweb/static/gitweb.js
+       Alias       /git-logo.png       /usr/local/share/gitweb/static/git-logo.png
+       Alias       /git-favicon.png    /usr/local/share/gitweb/static/git-favicon.png
+       Alias       /favicon.ico        /usr/local/share/gitweb/static/git-favicon.png
+
        # Logfiles
        ErrorLog  /data/logs/httpd/git.whamcloud.com-errors.log
        CustomLog /data/logs/httpd/git.whamcloud.com.log combined
 &amp;lt;/VirtualHost&amp;gt;
-
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="87034" author="mjs" created="Thu, 19 Jun 2014 15:25:32 +0000"  >&lt;p&gt;I haven&apos;t played with apache for ages, it looks reasonable to me.&lt;/p&gt;</comment>
                            <comment id="87074" author="jlevi" created="Thu, 19 Jun 2014 18:30:37 +0000"  >&lt;p&gt;Approved to deploy.&lt;/p&gt;</comment>
                            <comment id="87076" author="joshua" created="Thu, 19 Jun 2014 18:55:42 +0000"  >&lt;p&gt;Deployed. I had forgotten that this line was also added to &lt;tt&gt;/etc/gitweb.conf&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;{{$feature&lt;/p&gt;
{&apos;pathinfo&apos;}
{&apos;default&apos;}
&lt;p&gt; = &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt;}}&lt;/p&gt;

&lt;p&gt;so that URLs would be produced properly.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvuqf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8975</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>