<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:11:53 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-937] CLIENTONLY testing no longer works</title>
                <link>https://jira.whamcloud.com/browse/LU-937</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I&apos;m trying to run &quot;CLIENTONLY&quot; testing on 2.1.  CLIENTONLY testing is basically a test mode where test-framework.sh is not allowed to muck with the servers, and therefore has to skip much of the server configuration portion of the testing.  IIRC it assumes that lustre is already mounted on the client doing the testing.&lt;/p&gt;

&lt;p&gt;This seems to have gotten broken with 165400bbb8161b36764bd51056293375101329a6 back at the end of 2009.&lt;/p&gt;

&lt;p&gt;I have (na&#239;vely) applied the following patch to at least get past the blocking nature of this bug:&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;--- a/lustre/tests/test-framework.sh
+++ b/lustre/tests/test-framework.sh
@@ -2436,7 +2436,9 @@ check_and_setup_lustre() {
     fi
 
     init_gss
-    set_flavor_all $SEC
+    &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; [ -z &lt;span class=&quot;code-quote&quot;&gt;&quot;$CLIENTONLY&quot;&lt;/span&gt; ]; then
+        set_flavor_all $SEC
+    fi
 
     &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; [ &lt;span class=&quot;code-quote&quot;&gt;&quot;$ONLY&quot;&lt;/span&gt; == &lt;span class=&quot;code-quote&quot;&gt;&quot;setup&quot;&lt;/span&gt; ]; then
         exit 0
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I don&apos;t know if this really is an acceptable solution but I can&apos;t imagine why it would be acceptable to try to set/test the GSS flavour when the particular (CLIENTONLY) testing mode is supposed to keep it&apos;s hands off of the servers and just use the client mount as it is anyway.&lt;/p&gt;

&lt;p&gt;Probably before landing such a patch, somebody would need to investigate the entire nature of &lt;tt&gt;set_flavor_all()&lt;/tt&gt; to be sure this is the correct fix.&lt;/p&gt;</description>
                <environment>CLIENTONLY=true PDSH=&amp;quot;pdsh -R ssh -S -w&amp;quot; mds_HOST=mds1 mgs_HOST=mds2 ost1_HOST=oss1 ost2_HOST=oss2 OSTDEV1=&amp;quot;/dev/vdb&amp;quot; OSTDEV2=&amp;quot;/dev/vdb&amp;quot; bash /usr/lib64/lustre/tests/sanity.sh</environment>
        <key id="12705">LU-937</key>
            <summary>CLIENTONLY testing no longer works</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="brian">Brian Murrell</reporter>
                        <labels>
                    </labels>
                <created>Fri, 16 Dec 2011 18:36:33 +0000</created>
                <updated>Mon, 13 Mar 2017 13:12:34 +0000</updated>
                            <resolved>Sat, 6 Aug 2016 12:54:53 +0000</resolved>
                                    <version>Lustre 2.1.0</version>
                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="24898" author="adilger" created="Fri, 16 Dec 2011 19:15:18 +0000"  >&lt;p&gt;Brian,&lt;br/&gt;
it makes sense to push this to Gerrit and land it.  Since we don&apos;t test GSS at all (hopefully that will change next year when IU makes a &quot;simple shared key&quot; GSS plugin that we can test all of the time), I&apos;m expecting that there is no harm to land your fix now and leave it to others to catch any problems with it.&lt;/p&gt;</comment>
                            <comment id="152709" author="gerrit" created="Wed, 18 May 2016 16:22:37 +0000"  >&lt;p&gt;Dmitry Eremin (dmitry.eremin@intel.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/20312&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/20312&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-937&quot; title=&quot;CLIENTONLY testing no longer works&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-937&quot;&gt;&lt;del&gt;LU-937&lt;/del&gt;&lt;/a&gt; tests: fix CLIENTONLY mode for KNL testing&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: d99b5936b44ca6d6b12c33442eae2e035ab47432&lt;/p&gt;</comment>
                            <comment id="161021" author="gerrit" created="Sat, 6 Aug 2016 06:24:32 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/20312/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/20312/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-937&quot; title=&quot;CLIENTONLY testing no longer works&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-937&quot;&gt;&lt;del&gt;LU-937&lt;/del&gt;&lt;/a&gt; tests: fix CLIENTONLY mode for KNL testing&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 7b5f76efce503cdca836e138332fdbaae4b4bbf4&lt;/p&gt;</comment>
                            <comment id="161040" author="pjones" created="Sat, 6 Aug 2016 12:54:53 +0000"  >&lt;p&gt;Landed for 2.9&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="44669">LU-9205</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|hzw2vr:</customfieldvalue>

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