[LU-10199] sanity test_56xb: hard links individually migrated (12 != 11) Created: 06/Nov/17 Updated: 09/Apr/18 Resolved: 26/Mar/18 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.11.0 |
| Fix Version/s: | Lustre 2.11.0, Lustre 2.10.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Maloo | Assignee: | Steve Guminski (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
This issue was created by maloo for Bob Glossman <bob.glossman@intel.com> This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/740cdf26-c31d-11e7-88ab-52540065bddc. The sub-test test_56xb failed with the following error: hard links individually migrated (12 != 11) strongly suspect this is due to the very recently landed " Info required for matching: sanity 56xb |
| Comments |
| Comment by Gerrit Updater [ 06/Nov/17 ] |
|
Steve Guminski (stephenx.guminski@intel.com) uploaded a new patch: https://review.whamcloud.com/29954 |
| Comment by Andreas Dilger [ 06/Nov/17 ] |
|
Do we have any idea why this is failing? I'd prefer a patch that fixes a problem vs. reverting it. Next best would be a patch to skip just the failing test for SLES, so that we keep the patch landed and testing under RHEL, and give us some time to fix the SLES issue. |
| Comment by Steve Guminski (Inactive) [ 07/Nov/17 ] |
|
I just reran the sanity test on my local RHEL system, and it fails there, too. So I'm not sure what has changed between the time that the patch was originally submitted and now that would cause this change in behavior. I'll submit a new patch that disables the test instead of reverting. |
| Comment by Bob Glossman (Inactive) [ 07/Nov/17 ] |
|
Here is an instance of it failing on el7 too: Is it possible that it originally passed test on el7.3 and is now failing on el7.4? |
| Comment by Steve Guminski (Inactive) [ 07/Nov/17 ] |
|
Yes, that's possible. My local CentOS test system was upgraded during that period. |
| Comment by Gerrit Updater [ 07/Nov/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/29954/ |
| Comment by Gerrit Updater [ 09/Nov/17 ] |
|
Steve Guminski (stephenx.guminski@intel.com) uploaded a new patch: https://review.whamcloud.com/30013 |
| Comment by Andreas Dilger [ 11/Nov/17 ] |
|
It would be good to have some examples of how this is broken, since I can't imagine how "lfs fid2path" is generating a non-absolute pathnames. |
| Comment by Gerrit Updater [ 14/Nov/17 ] |
|
Ben Evans (bevans@cray.com) uploaded a new patch: https://review.whamcloud.com/30078 |
| Comment by Gerrit Updater [ 22/Nov/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/30078/ |
| Comment by Peter Jones [ 22/Nov/17 ] |
|
Landed for 2.11 |
| Comment by Gerrit Updater [ 20/Dec/17 ] |
|
Steve Guminski (stephenx.guminski@intel.com) uploaded a new patch: https://review.whamcloud.com/30616 |
| Comment by Andreas Dilger [ 03/Jan/18 ] |
|
The patch to re-enable this test was not landed, and it is still being skipped. |
| Comment by Gerrit Updater [ 09/Jan/18 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/30616/ |
| Comment by Bob Glossman (Inactive) [ 24/Mar/18 ] |
|
more seen on b2_10: |
| Comment by Andreas Dilger [ 25/Mar/18 ] |
|
This problem is not fixed, only the test is in ALWAYS_EXCEPT on master. As a general rule, any ticket with the always_except label should not be closed. This label should be removed when the patch that re-enables the test is landed. I've often found, as in this case, that a ticket is marked resolved, but the reason the test is no longer failing is because the test has been disabled. |
| Comment by Bob Glossman (Inactive) [ 25/Mar/18 ] |
|
this test was fixed on master (probably) by https://review.whamcloud.com/30078 and then reenabled by https://review.whamcloud.com/30616. |
| Comment by Andreas Dilger [ 26/Mar/18 ] |
|
Sorry, I was looking at an old branch that still showed 56xb as being in ALWAYS_EXCEPT. |
| Comment by Gerrit Updater [ 26/Mar/18 ] |
|
Bob Glossman (bob.glossman@intel.com) uploaded a new patch: https://review.whamcloud.com/31775 |
| Comment by Gerrit Updater [ 05/Apr/18 ] |
|
John L. Hammond (john.hammond@intel.com) merged in patch https://review.whamcloud.com/31775/ |