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-13999 Lustre <p>This issue was created by maloo for wangshilong &lt;wshilong@ddn.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.whamcloud.com/test_sets/80d98472-3223-4cd2-b009-4c3d6dce5639" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/80d98472-3223-4cd2-b009-4c3d6dce5639</a></p> <p>test_54 failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>fscrypt encrypt failed </pre> </div></div> <p>&lt;&lt;Please provide additional information about the failure here&gt;&gt;</p> <p>VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV<br/> sanity-sec test_54 - fscrypt encrypt failed</p> LU-13999

sanity-sec test_54: fscrypt encrypt: user keyring not linked into session keyring

Bug Minor Open Unresolved Sebastien Buisson Maloo Tue, 29 Sep 2020 01:04:24 +0000 Wed, 15 Jun 2022 12:28:46 +0000 Lustre 2.15.0 0 4 <p>Problem stems from the fscrypt version installed on Ubuntu client nodes. It is too old, and is not able to handle encryption policies v2, required for proper Lustre operation.</p> <p>Hit the same error in interop testing between master and 2.14 client<br/> <a href="https://testing.whamcloud.com/test_sets/09838ea8-8c85-4a92-ba12-775d8994ed12" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/09838ea8-8c85-4a92-ba12-775d8994ed12</a></p> <p>Just update with more details. I can reproduce this error with AlmaLinux 8.6. Ubuntu 20.04 does not show such issue. <br/> Error: <span class="error">&#91;ERROR&#93;</span> fscrypt encrypt: user keyring for "runas" is not linked into the session keyring</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> This is usually the result of a bad PAM configuration. Either correct the problem in your PAM stack, enable pam_keyinit.so, or run <span class="code-quote">"keyctl link @u @s"</span>. 2022/06/15 11:59:49 creating policy <span class="code-keyword">for</span> <span class="code-quote">"/lustre/es01a/client/userenc"</span> 2022/06/15 11:59:49 keyringID(_uid.500) = 703180163, &lt;nil&gt; 2022/06/15 11:59:49 KeyctlLink(703180163, -1) = &lt;nil&gt; 2022/06/15 11:59:49 keyringID(session) = 55270648, &lt;nil&gt; 2022/06/15 11:59:49 KeyctlSearch(55270648, keyring, _uid.500) = -1, required key not available </pre> </div></div> <p>Tested fscrypt version was v0.2.9<br/> Also this error can be related to issues<br/> <a href="https://github.com/google/fscrypt/issues/194" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/google/fscrypt/issues/194</a> <br/> <a href="https://github.com/google/fscrypt/issues/34" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/google/fscrypt/issues/34</a> </p> <p>as workaround suggested command was started "keyctl link @u @s" . After that fscrypt encrypt completed successfully. </p> Related LU-14401 Development Rank 1|i01ay7: Rank (Obsolete) 9223372036854775807 Severity