[LU-151] Test cases fail if the $RUNAS_ID does not have executable permissions Created: 22/Mar/11 Updated: 04/Mar/14 Resolved: 04/Mar/14 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.1.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Prakash Surya (Inactive) | Assignee: | Chris Gearing (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 10193 |
| Description |
|
If the $RUNAS_ID user does not have executable permissions on the lustre source tree, certain tests cases will fail with obscure error messages. For example, with a user id of 0, runas id of 99, and a umask of 0077.. sanity.sh test 33a fails because the $LUSTRE_SRC/lustre/tests/openfile is not executable by user 99. Although, if our umask if 0000, then of course user 99 has executable permissions on the openfile binary and the test passes. To top it off, the tests will fail without reporting the permissions issue. From the outside, it appears that Lustre is failing these specific test cases when that is not the real problem at all. Perhaps, there needs to be a way to check the permissions and then skip the tests it cannot run based on this check? Also, displaying a human readable message explaining to the user why these tests are being skipped could provide useful. |
| Comments |
| Comment by Peter Jones [ 23/Mar/11 ] |
|
Prakash I spoke with Chris Gearing, who is leading the efforts to revamp the whole Lustre test infrastructure. It sounds like this specific instance - and other similar instances which you alluded to in yesterday's meeting - should be tackled as part of the larger clean up plans. Regards Peter |
| Comment by Prakash Surya (Inactive) [ 23/Mar/11 ] |
|
Thanks Peter. On a related note, as more issues with the test suite are uncovered, is opening individual JIRA tickets for each issue the accepted way to go about reporting them? Prakash |
| Comment by Peter Jones [ 15/Dec/11 ] |
|
Prakash Sorry I missed your question previously. I would say that opening a new ticket is the best way to go. It can always be closed as a duplicate if it is addressed as part of a larger cleanup exercise Peter |
| Comment by John Fuchs-Chesney (Inactive) [ 04/Mar/14 ] |
|
JIRA cleanup project. |