<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:10:36 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-809] Jenkins Ubuntu build does not use &apos;--disable-server&apos; configure option</title>
                <link>https://jira.whamcloud.com/browse/LU-809</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;The Jenkins automated build does not use the &apos;--disable-server&apos; configure option when building the lustre client for Ubuntu. This prevents the ldiskfs configure script from knowing whether it should enable or disable building ldiskfs.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12289">LU-809</key>
            <summary>Jenkins Ubuntu build does not use &apos;--disable-server&apos; configure option</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="adilger">Andreas Dilger</assignee>
                                    <reporter username="prakash">Prakash Surya</reporter>
                        <labels>
                    </labels>
                <created>Mon, 31 Oct 2011 18:55:31 +0000</created>
                <updated>Wed, 2 Nov 2011 11:52:13 +0000</updated>
                            <resolved>Wed, 2 Nov 2011 11:52:13 +0000</resolved>
                                    <version>Lustre 2.1.0</version>
                    <version>Lustre 2.2.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                            <comments>
                            <comment id="22233" author="adilger" created="Mon, 31 Oct 2011 19:21:55 +0000"  >&lt;p&gt;I don&apos;t know that this should be a defect in the build system, since every user that tries to build on a kernel that cannot work as a server (missing patch series or &lt;/p&gt;
{ldiskfs,zfs}-devel) will fail in a similar manner.&lt;br/&gt;
&lt;br/&gt;
I think the configure system itself should be able to determine whether it &lt;em&gt;can&lt;/em&gt; build against the current kernel, and only use --disable-server if this automatic check should be overridden.  That is the behaviour of the current build system (build server support if available, build client only if server cannot be built).&lt;br/&gt;
&lt;br/&gt;
The current server build detects whether the kernel is patched based on the presence or absence of the lustre-version.h file, but I think this is obsolete and should be replaced by proper checks for actually needed symbol exports and -devel packages.  Much of this work has been done already, but I think the last missing check is for the {ldiskfs,zfs}
&lt;p&gt;-devel package (or more correctly headers from them, in case the package name is different on different distros), or falling back to checking whether the in-tree ldiskfs contains a patch series for the current kernel.&lt;/p&gt;</comment>
                            <comment id="22285" author="adilger" created="Wed, 2 Nov 2011 11:52:13 +0000"  >&lt;p&gt;Prakash fixed this within the ldiskfs configure scripts by detecting whether ldiskfs was available, or if there is an available patch series for the kernel.  If no ldiskfs is available for this kernel then no server support will be built.&lt;/p&gt;

&lt;p&gt;For Orion the configure script will have to detect whether either ldiskfs or ZFS is available before disabling the server build.&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|hzvhsn:</customfieldvalue>

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