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-14181 Lustre <p>This issue was created by maloo for S Buisson &lt;sbuisson@ddn.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.whamcloud.com/test_sets/2e038072-2f42-4dca-bb3d-ce025d30fbaa" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/2e038072-2f42-4dca-bb3d-ce025d30fbaa</a></p> <p>test_64e failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>init grants: grants mismatch: 0, expected 2146304 </pre> </div></div> <p>This happens with any SSK flavor when client runs on RHEL/CentOS 8.2.</p> <p>VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV<br/> sanity test_64e - init grants: grants mismatch: 0, expected 2146304</p> LU-14181

sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2

Bug Minor Reopened Unresolved Sebastien Buisson Maloo always_except Fri, 4 Dec 2020 08:14:20 +0000 Mon, 28 Aug 2023 06:43:19 +0000 0 4 <p>Sebastien Buisson (sbuisson@ddn.com) uploaded a new patch: <a href="https://review.whamcloud.com/40865" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/40865</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14181" title="sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2" class="issue-link" data-issue-key="LU-14181">LU-14181</a> tests: except sanity test_64e 64f with SHARED_KEY<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: f819cce3ed0fa11e4d2e6a071dcc90b3a1f49ca2</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/40865/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/40865/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14181" title="sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2" class="issue-link" data-issue-key="LU-14181">LU-14181</a> tests: except sanity test_64e 64f with SHARED_KEY<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: aa3bdbc23bc86bae565e78b38946f4ac8fcbeacb</p> <p>Landed for 2.14</p> <p>Sebastien Buisson (sbuisson@ddn.com) uploaded a new patch: <a href="https://review.whamcloud.com/40999" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/40999</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14181" title="sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2" class="issue-link" data-issue-key="LU-14181">LU-14181</a> tests: except sanity test_64e 64f with SHARED_KEY<br/> Project: fs/lustre-release<br/> Branch: b2_12<br/> Current Patch Set: 1<br/> Commit: 23a43d24e2a87f1a3b580bdff979461c7b4c0b9a</p> <p>ALWAYS_EXCEPT isn't really meant to be a permanent place to skip tests. It is meant as a place to "temporarily" disable subtests that <em>should</em> be passing, but are consistently failing for some reason. That is why we don't allow bugs to be closed with the <tt>always_except</tt> marker on them.</p> <p>If these tests are <b>never</b> expected to work with SSK, then there should be a check in the test itself, and the test skipped with a short explanation of why it is skipped.</p> <p>It isn't clear to me <b>why</b> SSK would cause the OST grant to be incorrect? There wasn't any explanation in patch <a href="https://review.whamcloud.com/40865" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/40865</a> "<tt><a href="https://jira.whamcloud.com/browse/LU-14181" title="sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2" class="issue-link" data-issue-key="LU-14181">LU-14181</a> tests: except sanity test_64e 64f with SHARED_KEY</tt>", and there isn't any explanation in this ticket except that these tests are disabled.</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/40999/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/40999/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14181" title="sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2" class="issue-link" data-issue-key="LU-14181">LU-14181</a> tests: except sanity test_64e 64f with SHARED_KEY<br/> Project: fs/lustre-release<br/> Branch: b2_12<br/> Current Patch Set: <br/> Commit: 5bc9f3aa054c944435f56dcafc41ca97702888b6</p> <p>I wonder if this isn't just a timing thing and is perhaps fixed with <a href="https://jira.whamcloud.com/browse/LU-16541" title="sanity test_64f: buffered io, not write rpc: grants mismatch: 12656640, expected 4218880 " class="issue-link" data-issue-key="LU-16541"><del>LU-16541</del></a>?  Sebastien, are you able to check?</p> <p>"Sebastien Buisson &lt;sbuisson@ddn.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/52123" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/52123</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14181" title="sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2" class="issue-link" data-issue-key="LU-14181">LU-14181</a> tests: re-enable sanity test_64f with SHARED_KEY<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 2af4f9b51f15ffe2f235db52b23e7f125d3d2cad</p> <p>"Sebastien Buisson &lt;sbuisson@ddn.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/52124" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/52124</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14181" title="sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2" class="issue-link" data-issue-key="LU-14181">LU-14181</a> dbg: run sanity test_64f on SSK without <a href="https://jira.whamcloud.com/browse/LU-16541" title="sanity test_64f: buffered io, not write rpc: grants mismatch: 12656640, expected 4218880 " class="issue-link" data-issue-key="LU-16541"><del>LU-16541</del></a><br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 828fcf93f1ed89f60256904ca2c20795cf82c27b</p> <p>I have pushed test patches to see how it goes with sanity test_64f and SSK now that <a href="https://jira.whamcloud.com/browse/LU-16541" title="sanity test_64f: buffered io, not write rpc: grants mismatch: 12656640, expected 4218880 " class="issue-link" data-issue-key="LU-16541"><del>LU-16541</del></a> has landed. But initially the problem was also seen with sanity test_64e. Do you think the same timing thing could be addressed in test_64e?</p> <p>Unfortunately, sanity test_64f still fails with SSK:<br/> <a href="https://testing.whamcloud.com/test_sessions/66a85858-4ea7-4bd2-8aff-106d6c7dadf6" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sessions/66a85858-4ea7-4bd2-8aff-106d6c7dadf6</a></p> Development Rank 1|i01gcv: Rank (Obsolete) 9223372036854775807 Severity