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-9086 Lustre <p>Secure RPC rules are being ignored due to an issue introduced by commit 0308951e8bba1663bc9495eee2f6ae631e6bcbd0 for <a href="https://jira.whamcloud.com/browse/LU-9034" title="Separate the config logs between different MGCs" class="issue-link" data-issue-key="LU-9034"><del>LU-9034</del></a>. When mounting Lustre resources, clients and servers log the following messages when secure RPC rules are set:</p> <p>{{LustreError: 2696:0:(obd_config.c:1258:class_process_config()) no device for: lustre-ffff880078dd9e70<br/> Lustre: 2696:0:(obd_config.c:1311:class_process_config()) Ignoring error -22 on optional command 0xce016}}</p> <p>For my tests I set the following rules:<br/> lustre.srpc.flavor.tcp.cli2mdt=ski<br/> lustre.srpc.flavor.tcp.cli2ost=ski</p> <p>then:</p> <p>lustre.srpc.flavor.tcp.cli2mdt=krb5p<br/> lustre.srpc.flavor.tcp.cli2ost=krb5p</p> <p>All resources mount fine but cli2mdt and cli2ost connections aren't secured, they default to <em>null</em>.</p> CentOS 7.3 LU-9086

obd_config.c:1258:class_process_config()) no device for:

Bug Minor Resolved Fixed James A Simmons Nathan Lavender Wed, 8 Feb 2017 14:42:59 +0000 Sat, 21 Apr 2018 18:43:20 +0000 Sun, 23 Apr 2017 03:55:25 +0000 Lustre 2.10.0 Lustre 2.10.0 0 4 <p>This bug is preventing me for fixing <a href="https://jira.whamcloud.com/browse/LU-9073" title="SSK: lgss_sk generates keys with invalid HMAC and Crypto algorithms" class="issue-link" data-issue-key="LU-9073"><del>LU-9073</del></a></p> <p>James Simmons (uja.ornl@yahoo.com) uploaded a new patch: <a href="https://review.whamcloud.com/25959" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/25959</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-9086" title="obd_config.c:1258:class_process_config()) no device for:" class="issue-link" data-issue-key="LU-9086"><del>LU-9086</del></a> gss: handle specific mgc binding<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 4fc1de3721191d30658ef8f1830bae3a982a06f7</p> <p>The patch appears to fix this problem. Have you tried it?</p> <p><span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/26015/26015_krb5p_multinode_llmount.tgz" title="krb5p_multinode_llmount.tgz attached to LU-9086">krb5p_multinode_llmount.tgz^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p>The following error is logged multiple times on each of the nodes:</p> <p>mgc_request.c:2143:mgc_process_log()) MGC172.18.0.18@tcp: configuration from log 'lustre-sptlrpc' failed (-2).</p> <p> </p> <p>when SEC=krb5p and executing llmount.sh. Perhaps these logs will provide some clues as to why the rules are being ignored.</p> <p>So the question is now are the sptlrpc configurations per filesystem or per obd device. John asked the question about the case if we have two MGTs each with a filesystem named 'lustre' (and the client mounts both).</p> <p>It seems that sptlrpc rules are per filesystem. Setting a rule on one MGT affects the client's connection(s) to the other filesystem named 'lustre':</p> <p> </p> <p>client# lctl get_param <b>.</b>.srpc_* | grep -A2 mdc.lustre<br/> mdc.lustre-MDT0000-mdc-ffff88007884d800.srpc_info=<br/> rpc flavor: null<br/> bulk flavor: null<br/> &#8211;<br/> mdc.lustre-MDT0000-mdc-ffff88007a334000.srpc_info=<br/> rpc flavor: null<br/> bulk flavor: null</p> <p>mgs1# lctl conf_param lustre.srpc.flavor.default.cli2mdt=krb5p</p> <p>client# lctl get_param <b>.</b>.srpc_* | grep -A2 mdc.lustre<br/> mdc.lustre-MDT0000-mdc-ffff88007884d800.srpc_info=<br/> rpc flavor: krb5p<br/> bulk flavor: krb5p<br/> &#8211;<br/> mdc.lustre-MDT0000-mdc-ffff88007a334000.srpc_info=<br/> rpc flavor: krb5p<br/> bulk flavor: krb5p</p> <p> </p> <p>This test was conducted with Lustre v.2.9.0</p> <p><span class="error">&#91;root@ninja11 live&#93;</span># cat lustre<br/> fsname: lustre<br/> flags: 0x20 gen: 24<br/> lustre-MDT0000<br/> lustre-OST0000</p> <p>Secure RPC Config Rules:<br/> lustre.srpc.flavor.o2ib1.cli2mdt=skpi</p> <p>imperative_recovery_state:<br/> state: startup<br/> nonir_clients: 0<br/> nidtbl_version: 4<br/> notify_duration_total: 0.000527674<br/> notify_duation_max: 0.000306105<br/> notify_count: 2</p> <p>It lives!!!! Will push now.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="https://review.whamcloud.com/25959/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/25959/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-9086" title="obd_config.c:1258:class_process_config()) no device for:" class="issue-link" data-issue-key="LU-9086"><del>LU-9086</del></a> gss: handle specific mgc binding<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 1b22b5141a22d471f70339320ea156c26db0ed37</p> <p>Landed for 2.10</p> Related LU-9073 LU-9567 LU-10937 LU-9823 Development Rank 1|hzz2zr: Rank (Obsolete) 9223372036854775807 Severity