https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-8298 Lustre <p>When connecting to a GSS-ized target we see the following warnings on the console</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[80648.003579] Lustre: 1666:0:(tgt_handler.c:894:tgt_init_sec_level()) client 192.168.122.162@tcp -&gt; target lustre-MDT0000 uses old version, run under security level 0. </pre> </div></div> <p>These are likely misleading/unhelpful to the admin.</p> LU-8298

enabling gss causes possibly misleading warnings from tgt_init_sec_level()

Bug Minor Resolved Fixed nasf John Hammond Fri, 17 Jun 2016 15:42:42 +0000 Tue, 12 Jul 2016 01:09:50 +0000 Tue, 12 Jul 2016 01:09:50 +0000 Lustre 2.9.0 0 3 <p>After Fan Yong's patch for <a href="https://jira.whamcloud.com/browse/LU-6971" title="Remove obsolete remote client and &quot;lfs cp|ls|getacl|setacl&quot; commands" class="issue-link" data-issue-key="LU-6971"><del>LU-6971</del></a> has landed the I think the "sec_level" functionality will be obsolete. If so then tgt_init_sec_level() can be removed completely and this message will go away.</p> <blockquote> <p>After Fan Yong's patch for <a href="https://jira.whamcloud.com/browse/LU-6971" title="Remove obsolete remote client and &quot;lfs cp|ls|getacl|setacl&quot; commands" class="issue-link" data-issue-key="LU-6971"><del>LU-6971</del></a> has landed the I think the "sec_level" functionality will be obsolete. If so then tgt_init_sec_level() can be removed completely and this message will go away.</p></blockquote> <p>With <a href="https://jira.whamcloud.com/browse/LU-6971" title="Remove obsolete remote client and &quot;lfs cp|ls|getacl|setacl&quot; commands" class="issue-link" data-issue-key="LU-6971"><del>LU-6971</del></a> patch applied, you will NOT see the misguided message again. So we can close this ticket.</p> <p>It will be disappear after <a href="https://jira.whamcloud.com/browse/LU-6971" title="Remove obsolete remote client and &quot;lfs cp|ls|getacl|setacl&quot; commands" class="issue-link" data-issue-key="LU-6971"><del>LU-6971</del></a> patch (<a href="http://review.whamcloud.com/#/c/19789/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/19789/</a>) applied.</p> <p>Still seeing this after <a href="http://review.whamcloud.com/#/c/19789/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/19789/</a> landed. I think we can remove the sec_level parameter entirely. Fan Yong do you see any reason to keep it?</p> <p>John L. Hammond (john.hammond@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/20879" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/20879</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8298" title="enabling gss causes possibly misleading warnings from tgt_init_sec_level()" class="issue-link" data-issue-key="LU-8298"><del>LU-8298</del></a> sec: remove obsolete sec_level parameter<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 9e6bb7777541c02a8ceb9e5634bf1f58544916b9</p> <blockquote> <p>Still seeing this after <a href="http://review.whamcloud.com/#/c/19789/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/19789/</a> landed. I think we can remove the sec_level parameter entirely. Fan Yong do you see any reason to keep it?</p></blockquote> <p>Currently, the sec_level is almost meaningless. I am fine to cleanup related code, just one concern about the interoperability issue when upgrade. If some customer has ever specified sec_level as conf parameter, then removing such interface may cause the new server does not recognise the old configuration after upgrading: either confused waring message or start failure. So please verify that, if happened, we can:<br/> 1) simply the interface as empty stub there for some time, or<br/> 2) add some special handling in class_process_proc_param().</p> <p>I have verified the upgrading case, and updated the class_process_proc_param() in the patch to handle sec_level specially.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/20879/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/20879/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8298" title="enabling gss causes possibly misleading warnings from tgt_init_sec_level()" class="issue-link" data-issue-key="LU-8298"><del>LU-8298</del></a> sec: remove obsolete sec_level parameter<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 881e4d68346be5623c4045dad0d6a50d4954f6fb</p> <p>The patch has been landed to master.</p> Related LU-6971 Development Rank 1|hzyexj: Rank (Obsolete) 9223372036854775807 Severity