<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:17:15 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-8404] When service node nid is incorrect, MDT log message missing bad nid</title>
                <link>https://jira.whamcloud.com/browse/LU-8404</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;When entering a bad nid address in the &lt;tt&gt;--servicenode&lt;/tt&gt; argument. This caused the MDT to not be able to establish a connection and reports in the log as below.&lt;/p&gt;

&lt;p&gt;Note the &lt;tt&gt;0@&amp;lt;0:0&amp;gt;&lt;/tt&gt; at the end that, I am guessing, should be the servicenode failover args and is reporting &quot;&lt;tt&gt;0:0&lt;/tt&gt;&quot; instead. If it had reported the correct args, this would have been a much easier problem to figure out.&lt;/p&gt;

&lt;p&gt;Also in the mds log:&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;class_config_llog_handler()) MGC192.168.20.121@o2ib: cfg command failed: rc = -2
cmd=cf003 0:lustrefs-OST0010-osc-MDT0000  1:lustrefs-OST0010_UUID  2:0@&amp;lt;0:0&amp;gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="38199">LU-8404</key>
            <summary>When service node nid is incorrect, MDT log message missing bad nid</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="3">Duplicate</resolution>
                                        <assignee username="hongchao.zhang">Hongchao Zhang</assignee>
                                    <reporter username="ghagensen">Gary Hagensen</reporter>
                        <labels>
                    </labels>
                <created>Fri, 15 Jul 2016 05:32:06 +0000</created>
                <updated>Thu, 18 Aug 2016 21:32:32 +0000</updated>
                            <resolved>Thu, 18 Aug 2016 21:32:31 +0000</resolved>
                                    <version>Lustre 2.7.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="158977" author="adilger" created="Fri, 15 Jul 2016 17:25:51 +0000"  >&lt;p&gt;Gary, can you please provide more details about how the NID was incorrect, so that this can be debugged/fixed properly and there can be a test case added for this.  As it is, I have no idea how to reproduce this problem.&lt;/p&gt;</comment>
                            <comment id="158984" author="ghagensen" created="Fri, 15 Jul 2016 17:41:06 +0000"  >&lt;p&gt;The bad servicenode argument I used was the node&apos;s management interface @ tcp0 . So it was a valid IP, but not a valid NID as it is not on an LNET. The LNET interface was the IB interface. So I assume to reproduce all you would need is a system (or VMs) with 2 interfaces on the HA pair, one for management, one for LNET and define the service nodes to be on the non-lnet interface.&lt;/p&gt;</comment>
                            <comment id="160287" author="hongchao.zhang" created="Fri, 29 Jul 2016 11:03:20 +0000"  >&lt;p&gt;the patch &lt;a href=&quot;http://review.whamcloud.com/19933/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/19933/&lt;/a&gt; from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8091&quot; title=&quot;server_lsi2mti() should return error when fail to get nid&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8091&quot;&gt;&lt;del&gt;LU-8091&lt;/del&gt;&lt;/a&gt; can fix the problem.&lt;/p&gt;</comment>
                            <comment id="162457" author="pjones" created="Thu, 18 Aug 2016 21:32:32 +0000"  >&lt;p&gt;So this is confirmed as a duplicate of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8091&quot; title=&quot;server_lsi2mti() should return error when fail to get nid&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8091&quot;&gt;&lt;del&gt;LU-8091&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                        </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|hzyhk7:</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>