[LU-4234] Failure on test suite sanity-scrub test_4: fail to stop client Created: 08/Nov/13 Updated: 18/Nov/13 Resolved: 18/Nov/13 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | nasf (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
server and client: lustre-master build # 1751 RHEL6 ldiskfs |
||
| Severity: | 3 |
| Rank (Obsolete): | 11531 |
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/adbd0d60-47e6-11e3-a445-52540035b04c. The sub-test test_4 failed with the following error:
pdsh@client-26vm6: gethostbyname("client-26vm5") failed
sanity-scrub test_4: @@@@@@ FAIL: Fail to stop client!
|
| Comments |
| Comment by nasf (Inactive) [ 18/Nov/13 ] |
|
The test nodes are: The test scripts were running on the Client1 (client-26vm6). When the client1 try to stop the system, it failed to stop the client2 (client-26vm5) as following: pdsh@client-26vm6: gethostbyname("client-26vm5") failed
sanity-scrub test_4: @@@@@@ FAIL: Fail to stop client!
But the test has nothing related with the client2. I do not think it is Lustre issue, instead, it looks more like DNS related issue. |
| Comment by nasf (Inactive) [ 18/Nov/13 ] |
|
LU-1817 |