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-17450 Lustre <p>This issue was created by maloo for Andreas Dilger &lt;adilger@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.whamcloud.com/test_sets/dc77145c-b7d3-4010-a7a2-f8435f9353ff" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/dc77145c-b7d3-4010-a7a2-f8435f9353ff</a></p> <p>Test session details:<br/> clients: <a href="https://build.whamcloud.com/job/lustre-reviews/101478" class="external-link" target="_blank" rel="nofollow noopener">https://build.whamcloud.com/job/lustre-reviews/101478</a> - 4.18.0-477.27.1.el8_8.x86_64<br/> servers: <a href="https://build.whamcloud.com/job/lustre-b2_15/81" class="external-link" target="_blank" rel="nofollow noopener">https://build.whamcloud.com/job/lustre-b2_15/81</a> - 4.18.0-513.9.1.el8_lustre.x86_64</p> <p>there are a number of sanity interop test failures with 2.15.4 servers</p> <p>Please review the test failures to determine for each one:</p> <ul class="alternate" type="square"> <li>when did the failure first start happening?</li> <li>is this a new test added since 2.15.50 was forked from b2_15?</li> <li>should the test be skipped because of an older MDS or OSS version?</li> <li>is this a legitimate regression?</li> <li>if not a clear case of new test with old server, ensure an LU ticket is open for it with details and add to always_except</li> </ul> LU-17450

sanity: interop test failures with master+2.15

Bug Critical Open Unresolved WC Triage Maloo Sat, 20 Jan 2024 19:36:40 +0000 Tue, 23 Jan 2024 02:34:12 +0000 Lustre 2.16.0 0 5 <p>Make this a blocker for 2.16.0 since we can't release it until we are sure it is not introducing any interop issues, which would be much harder to fix afterward. </p> <p>It looks at a minimum that there is something wrong with file migrate, but I haven't looked at all of the failures in this interop session yet. There is a small chance that one or two subtest failures relate to the patch that was being tested (which is why I requested interop testing in the first place), but many of the failures have been present for weeks and are not isolated to a single subtest. </p> <p>test_56x, test_56xa, test_56xc - not sure (they are old tests)<br/> test_65p - from <a href="https://review.whamcloud.com/48684" class="external-link" target="_blank" rel="nofollow noopener">LU-16194 lod: define negative extent offset as invalid</a><br/> test_70a - from <a href="https://review.whamcloud.com/52782" class="external-link" target="_blank" rel="nofollow noopener">LU-17216 ofd: make enable_health_write tunable</a>, requested interop check there<br/> test_119h, test_119i, test_398d, test_398o - from <a href="https://review.whamcloud.com/45616" class="external-link" target="_blank" rel="nofollow noopener">LU-13805 clio: bounce buffer for unaligned DIO</a> <br/> test_123g, test_123h, test_123i - from <a href="https://review.whamcloud.com/51730" class="external-link" target="_blank" rel="nofollow noopener">LU-14361 statahead: Add test for statahead advise</a></p> <p>I've requested patches to add interop checks for the identified source patches, but not sure why test_56x is failing. Those tests look related to lfs_migrate, but needs some more investigation why it is failing.</p> Related LU-13805 LU-14361 LU-17216 LU-16194 Development Rank 1|i048en: Rank (Obsolete) 9223372036854775807 Severity