[LU-635] conf-sanity test_29: @@@@@@ FAIL: test_29 failed with 5 Created: 25/Aug/11 Updated: 27/Mar/12 Resolved: 04/Jan/12 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.2.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | James A Simmons | Assignee: | Minh Diep |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
| Severity: | 3 |
| Rank (Obsolete): | 4235 |
| Description |
|
Starting client: spoon01: -o user_xattr,acl,flock 10.37.248.61@o2ib1:/lustre /lustre/barry error: get_param: /proc/{fs,sys} / {lnet,lustre}/osc/lustre-OST0001-osc-[^M]*/ost_server_uuid: Found no match |
| Comments |
| Comment by Peter Jones [ 13/Dec/11 ] |
|
James Are you still seeing this issue with the latest code? Peter |
| Comment by James A Simmons [ 13/Dec/11 ] |
|
Yes it still fails but for a different reason. This is due to the MDS and MGS being different servers now. |
| Comment by Peter Jones [ 13/Dec/11 ] |
|
Hi Minh Please can you look into this reported test failure? Thanks Peter |
| Comment by Minh Diep [ 13/Dec/11 ] |
|
Hi James, Could you post the config or local.sh file? |
| Comment by James A Simmons [ 15/Dec/11 ] |
|
Okay I actually tracked down what was causing the failure. Several other test were failing for the same reason. I posted a patch at http://review.whamcloud.com/#change,1869 which make all my test pass. |
| Comment by Peter Jones [ 15/Dec/11 ] |
|
Duplicate of |
| Comment by James A Simmons [ 15/Dec/11 ] |
|
No this one is different then |
| Comment by Peter Jones [ 15/Dec/11 ] |
|
ok sorry about that - reopening |
| Comment by Minh Diep [ 15/Dec/11 ] |
|
James, I want to reproduce this issue in the lab. Please describe in details your config or send me the local.sh file |
| Comment by James A Simmons [ 15/Dec/11 ] |
|
Here is my configuration. |
| Comment by Minh Diep [ 30/Dec/11 ] |
|
Thanks James, I would be nice if you can upload your test log to maloo |
| Comment by James A Simmons [ 30/Dec/11 ] |
|
I agree. Just need to set it up on our end. |
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 03/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Build Master (Inactive) [ 04/Jan/12 ] |
|
Integrated in Result = SUCCESS
|
| Comment by Peter Jones [ 04/Jan/12 ] |
|
ok, so it looks like we can really mark this as resolved now as this fix has been landed for 2.2 |