<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:15:09 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-1272] lbuild-sles11 and kernel versioning</title>
                <link>https://jira.whamcloud.com/browse/LU-1272</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Sometimes the version/release string in SLES kernel RPMs doesn&apos;t match the version of the kernel they&apos;re associated with.&lt;/p&gt;

&lt;p&gt;Case in point:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;-rw-r--r-- 1 jenkins jenkins 10081544 2011-04-15 01:38 kernel-&lt;span class=&quot;code-keyword&quot;&gt;default&lt;/span&gt;-base-2.6.32.36-0.5.2.x86_64.rpm
-rw-r--r-- 1 root    root     2513871 2011-04-15 01:38 kernel-&lt;span class=&quot;code-keyword&quot;&gt;default&lt;/span&gt;-devel-2.6.32.36-0.5.2.x86_64.rpm
-rw-r--r-- 1 jenkins jenkins 72416640 2011-04-15 00:29 kernel-source-2.6.32.36-0.5.2.x86_64.rpm
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The rpm %version is 2.6.32.36 and the %release is 0.5.2.  The kernel /inside/ the kernel source RPM is versioned 2.6.32.36-0.5, and the source directory reflects this:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;/&lt;span class=&quot;code-keyword&quot;&gt;var&lt;/span&gt;/lib/jenkins/workspace/lustre-reviews/arch/x86_64/build_type/client/distro/sles11/ib_stack/inkernel/BUILD/reused/usr/src/linux-2.6.32.36-0.5
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;This mismatch plays merry havoc with lbuild&apos;s ability to find the RPMs it needs to build lustre.  It also seems to have caused confusion over on the provisioning side of things (TT-468).&lt;/p&gt;

&lt;p&gt;Ideally, all of our code which deals with SLES kernels should be updated to deal with this crazy situation, because if it happened once it may happen again (who knows, it&apos;s SLES, maybe they always do it this way because ... it&apos;s SLES).  As a simple workaround, we could try to find a kernel which doesn&apos;t have this ridiculous mismatch and standardize on it.&lt;/p&gt;</description>
                <environment></environment>
        <key id="13803">LU-1272</key>
            <summary>lbuild-sles11 and kernel versioning</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="wc-triage">WC Triage</assignee>
                                    <reporter username="mjmac">Michael MacDonald</reporter>
                        <labels>
                    </labels>
                <created>Fri, 30 Mar 2012 09:59:12 +0000</created>
                <updated>Mon, 29 May 2017 04:11:44 +0000</updated>
                            <resolved>Mon, 29 May 2017 04:11:44 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="32916" author="brian" created="Fri, 30 Mar 2012 10:08:44 +0000"  >&lt;p&gt;There is code in lbuild already to try to deal with this.  It was landed in 16d51ff27b719f8ba31b18e64d9878843266fa8c.  That patch only dealt with the SRPM however.  It seems now that SUSE are now also playing games with the names of the binary RPMs that are produced from that SRPM.&lt;/p&gt;</comment>
                            <comment id="32920" author="mjmac" created="Fri, 30 Mar 2012 10:37:22 +0000"  >&lt;p&gt;I&apos;ve also created &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1273&quot; title=&quot;lbuild-sles11 and self-service capabilities&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1273&quot;&gt;&lt;del&gt;LU-1273&lt;/del&gt;&lt;/a&gt; to describe an enhancement to lbuild-sles11 which would allow it to download kernel packages automatically rather than requiring manual intervention.  This comment should also serve as a breadcrumb for someone looking to find out how to get at SLES kernel packages.&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|hzw293:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10447</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>