<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:36:08 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-10556] lustre client rebuild not building lnetctl</title>
                <link>https://jira.whamcloud.com/browse/LU-10556</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Similar to &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7887&quot; title=&quot;lbuild not building lnetctl&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7887&quot;&gt;&lt;del&gt;LU-7887&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;lnetctl not present in lustre-client rpm rpm rebuild from source. lnetctl is present in prebuilt rpm.&lt;/p&gt;

&lt;p&gt;It will be extremely helpful to have &quot;rpmbuild --rebuild&quot; to build lustre client rpm with the same content and functionality as lustre-client rpm from distro. &lt;/p&gt;

&lt;p&gt;The lustre client rpm rebuild is required time to time through lifecycle of the cluster. It shall be possible to do this type of work by administrators without knowledge of lustre internals.&lt;br/&gt;
There are several mails on lustre-discuss list reporting lnetctl is not in rpm.&lt;/p&gt;

&lt;p&gt;I had to explicitly use flags as listed below to get lnetctl:&lt;br/&gt;
 rpmbuild  --rebuild --without servers --with lnet-dlc --with lustre-utils ./lustre-2.10.2-1.src.rpm&lt;/p&gt;

&lt;p&gt;I did not  try rpm rebuild for SLF 7.4 as distro version worked for me.&lt;/p&gt;

&lt;p&gt;The other aspect, we have to document rpm rebuild procedure.&lt;br/&gt;
There are clear and detailed instructions on client rebuild on Cray website for their distro. I can not easily find &quot;rebuild&quot; in lustre manual linked from lustre.org. &lt;br/&gt;
There are detailed instructions on lustre wiki; they have to be updated with lnet-dlc lustre-utils until rpm build fixed.&lt;/p&gt;</description>
                <environment>OS: SLF 6.8&lt;br/&gt;
Kernel: 2.6.32-642.15.1.el6.x86_64&lt;br/&gt;
</environment>
        <key id="50366">LU-10556</key>
            <summary>lustre client rebuild not building lnetctl</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="simmonsja">James A Simmons</assignee>
                                    <reporter username="alex.ku">Alex Kulyavtsev</reporter>
                        <labels>
                    </labels>
                <created>Tue, 23 Jan 2018 22:29:07 +0000</created>
                <updated>Wed, 28 Mar 2018 17:11:38 +0000</updated>
                            <resolved>Mon, 26 Mar 2018 21:06:15 +0000</resolved>
                                    <version>Lustre 2.10.2</version>
                                    <fixVersion>Lustre 2.11.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="218942" author="simmonsja" created="Tue, 23 Jan 2018 22:36:46 +0000"  >&lt;p&gt;Do you have libyaml-devel package installed?&lt;/p&gt;</comment>
                            <comment id="218946" author="alex.ku" created="Tue, 23 Jan 2018 23:34:01 +0000"  >&lt;p&gt;Yes, both  libyaml libyaml-devel installed - I learned that during the server build.&lt;br/&gt;
config log explicitly shows that &quot;configure&quot; got libyaml* during rpm build.&lt;/p&gt;

&lt;p&gt;I rebuilt rpm with / without disable-dlc flag and it made the difference so it is not related to host configuration (with libyaml present).&lt;/p&gt;

&lt;p&gt;config.status shows for the plain rebuild &quot;--without servers&quot; and without explicitly setting flags lnet-dlc that enable_dlc is set no (disabled) by default and this prevents building lnetctl.&lt;/p&gt;

&lt;p&gt;aclocal.m4 :&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;# LN_CONFIG_DLC
#
# Configure dlc if enabled
#
# if libyaml is set (IE libyaml installed) and enable_dlc = yes then build
# dlc other wise (IE if libyaml is not set or enable_dlc = no) then don&apos;t
# build dlc.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Because distro rpm has dlc enabled, we shall have set enable_dlc = yes by default (at least when libyaml installed) and explicitly disable dlc when it is not needed and/or libyaml not installed. &lt;/p&gt;

&lt;p&gt;At this point I&apos;m OK with workaround; &lt;/p&gt;

&lt;p&gt;It is important to have client rpm to be rebuild with the same configuration as rpm in distro without unpacking and digging into source rpm.&lt;/p&gt;</comment>
                            <comment id="218949" author="adilger" created="Tue, 23 Jan 2018 23:50:21 +0000"  >&lt;p&gt;If we are marking the &lt;tt&gt;lctl&lt;/tt&gt; versions of the commands deprecated in 2.11 (per &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10003&quot; title=&quot;lnetctl error &amp;quot;cannot add network: invalid argument&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10003&quot;&gt;LU-10003&lt;/a&gt;) it makes sense to have &lt;tt&gt;enable_dlc&lt;/tt&gt; set by default.&lt;/p&gt;

&lt;p&gt;Alex, if you already have a patch for this, could you please submit it to Gerrit so we can land that for 2.11 and backport it for a 2.10 maintenance release.&lt;/p&gt;

&lt;p&gt;James, I see that in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9897&quot; title=&quot;Tracking of lustre library improvements.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9897&quot;&gt;LU-9897&lt;/a&gt; there is a change to the &lt;tt&gt;lustre.spec.in&lt;/tt&gt; file that removes the conditional build of &lt;tt&gt;liblnetconfig.so&lt;/tt&gt; but it doesn&apos;t add &lt;tt&gt;libyaml&lt;/tt&gt; or &lt;tt&gt;yaml-devel&lt;/tt&gt; (or whatever) package to the &lt;tt&gt;Build-requires:&lt;/tt&gt; line.&#160; That should probably be added.&lt;/p&gt;</comment>
                            <comment id="218954" author="simmonsja" created="Wed, 24 Jan 2018 01:33:34 +0000"  >&lt;p&gt;Yep. I missed adding that dependency. BTW while working with the &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9897&quot; title=&quot;Tracking of lustre library improvements.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9897&quot;&gt;LU-9897&lt;/a&gt; patch I noticed Debian/Ubuntu have no dependencies in its build files!!!! I was waiting for Martin&apos;s Ubuntu server patches to land first before I fix that.&lt;/p&gt;</comment>
                            <comment id="224213" author="gerrit" created="Wed, 21 Mar 2018 19:32:23 +0000"  >&lt;p&gt;Minh Diep (minh.diep@intel.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/31710&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/31710&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10556&quot; title=&quot;lustre client rebuild not building lnetctl&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10556&quot;&gt;&lt;del&gt;LU-10556&lt;/del&gt;&lt;/a&gt; build: add require libyaml and zlib&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: ac4da53c0f66b2f77b9f502bac6f4b26a45f2ceb&lt;/p&gt;</comment>
                            <comment id="224462" author="alex.ku" created="Fri, 23 Mar 2018 23:33:56 +0000"  >&lt;p&gt;I confirm&#160;/usr/sbin/lnetctl present in lustre-client rpm built from&#160;&#160;lustre-2.11.0_RC1_1_gac4da53-1.src.rpm&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;on SLF 7.4: &#160;&lt;/tt&gt;&lt;tt&gt;3.10.0-693.11.1.el7.x86_64&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;and&#160;SLF 6.8:&#160;&lt;/tt&gt;&lt;tt&gt;2.6.32-642.15.1.el6.x86_64&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;I grabbed source rpm from build server (artifact of build triggered by patch 31710)&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;wget &lt;a href=&quot;http://build.lustre.org/downloads/31710/1/centos/7.2/SRPM/lustre-2.11.0_RC1_1_gac4da53-1.src.rpm&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://build.lustre.org/downloads/31710/1/centos/7.2/SRPM/lustre-2.11.0_RC1_1_gac4da53-1.src.rpm&lt;/a&gt;&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;DIR=../downloads/build.lustre.org&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;SRPM=lustre-2.11.0_RC1_1_gac4da53-1.src.rpm&#160;&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;rpmbuild&#160; --rebuild --without servers --define &apos;configure_args --disable-gss --disable-gss-keyring&apos; $DIR/$SRPM&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="224463" author="alex.ku" created="Fri, 23 Mar 2018 23:49:25 +0000"  >&lt;p&gt;There is unrelated gss issue on SLF 7 node (it can be also some rpms are installed/missing).&lt;/p&gt;

&lt;p&gt;I had to add flags on SLF7 node to resolve error:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;--define &apos;configure_args --disable-gss --disable-gss-keyring&apos;&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;File not found: /root/rpmbuild/BUILDROOT/lustre-2.11.0_RC1_1_gac4da53-1.x86_64/etc/request-key.d/lgssc.conf&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Built completed OK on SLF 6.8 node.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;I guess gss is disabled by default in lustre.spec.in . If by some reason gss is enabled lustre build shall provide default on &lt;b&gt;&lt;ins&gt;build host&lt;/ins&gt;&lt;/b&gt; or do not complain.&lt;/p&gt;

&lt;p&gt;I read&#160;lgssc.conf is not used on client host until gss is configured:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LUDOC-197&quot; title=&quot;Complete Lustre Manual updates for IU Shared Secret Key authentication and encryption&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LUDOC-197&quot;&gt;&lt;del&gt;LUDOC-197&lt;/del&gt;&lt;/a&gt;:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;* is the /etc/request-key.d/lgssc.conf file included and installed with the Lustre RPMs? It seems that would be OK, since it would never be used unless there is a security flavor for a connection. The fewer things that users need to configure, the better.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="224465" author="simmonsja" created="Sat, 24 Mar 2018 02:22:29 +0000"  >&lt;p&gt;Alex I have a patch for the gss issues : &lt;a href=&quot;https://review.whamcloud.com/#/c/3175.&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/#/c/3175.&lt;/a&gt;&#160;That is tracked under &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10752&quot; title=&quot;Lustre rpm build issues due to improper lsvcgss packaging&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10752&quot;&gt;&lt;del&gt;LU-10752&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="224569" author="gerrit" created="Mon, 26 Mar 2018 20:40:02 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/31710/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/31710/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10556&quot; title=&quot;lustre client rebuild not building lnetctl&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10556&quot;&gt;&lt;del&gt;LU-10556&lt;/del&gt;&lt;/a&gt; build: add require libyaml and zlib&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: ab3185eb2b54ed2f616022956dca9bd5a849eb80&lt;/p&gt;</comment>
                            <comment id="224573" author="pjones" created="Mon, 26 Mar 2018 21:06:15 +0000"  >&lt;p&gt;Landed for 2.11&lt;/p&gt;</comment>
                            <comment id="224639" author="gerrit" created="Tue, 27 Mar 2018 18:53:54 +0000"  >&lt;p&gt;James Nunez (james.a.nunez@intel.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/31800&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/31800&lt;/a&gt;&lt;br/&gt;
Subject: Revert &quot;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10556&quot; title=&quot;lustre client rebuild not building lnetctl&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10556&quot;&gt;&lt;del&gt;LU-10556&lt;/del&gt;&lt;/a&gt; build: add require libyaml and zlib&quot;&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 8c206fdb6a2deae0cf60c4da4900518dad8360d4&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="48372">LU-10003</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="47888">LU-9897</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="51537">LU-10858</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|hzzrlb:</customfieldvalue>

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