[LU-5076] Test failure on test suite conf-sanity, subtest test_46a test failed to respond and timed out

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Severity: 3
• Assignee: Minh Diep
• Reporter: Maloo

Description

This issue was created by maloo for wangdi <[e-mail]>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/0638f47c-dd56-11e3-8e9b-52540035b04c.

The sub-test test_46a failed with the following error:

Lustre: ctl-lustre-MDT0000: super-sequence allocation rc = 0 [0x0000000240000400-0x0000000280000400):1:ost
Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected
Lustre: Skipped 3 previous similar messages
Lustre: ctl-lustre-MDT0000: super-sequence allocation rc = 0 [0x0000000300000400-0x0000000340000400):4:ost
Lustre: Skipped 2 previous similar messages
Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected
Lustre: Skipped 6 previous similar messages
Lustre: lustre-MDT0000: already connected client lustre-MDT0000-lwp-OST0000_UUID (at 10.10.4.199@tcp) with handle 0x2fb538c53b7cc26b. Rejecting client with the same UUID trying to reconnect with handle 0x4f578b0725086d9c
Lustre: Skipped 62 previous similar messages
Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected
Lustre: Skipped 12 previous similar messages
Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected
Lustre: Skipped 24 previous similar messages
LustreError: 11-0: lustre-OST0006-osc-MDT0000: Communicating with 10.10.4.199@tcp, operation ost_connect failed with -11.
LustreError: Skipped 94 previous similar messages
Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected
Lustre: Skipped 50 previous similar messages
Lustre: lustre-MDT0000: already connected client lustre-MDT0000-lwp-OST0001_UUID (at 10.10.4.199@tcp) with handle 0x2fb538c53b7cc33d. Rejecting client with the same UUID trying to reconnect with handle 0x4f578b0725086f01
Lustre: Skipped 306 previous similar messages
Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected
Lustre: Skipped 102 previous similar messages
LustreError: 11-0: lustre-OST0006-osc-MDT0000: Communicating with 10.10.4.199@tcp, operation ost_connect failed with -11.
LustreError: Skipped 120 previous similar messages
Lustre: lustre-MDT0000: already connected client lustre-MDT0000-lwp-OST0000_UUID (at 10.10.4.199@tcp) with handle 0x2fb538c53b7cc26b. Rejecting client with the same UUID trying to reconnect with handle 0x4f578b0725086d9c
Lustre: Skipped 364 previous similar messages
Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected
Lustre: Skipped 120 previous similar messages
LustreError: 11-0: lustre-OST0006-osc-MDT0000: Communicating with 10.10.4.199@tcp, operation ost_connect failed with -11.
test failed to respond and timed out

This failure is a bit strange, according to the syslog on MDS0

Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected

But the ip of OSS should be on 10.10.4.199, I do not know where this 10.10.4.203 comes from. So I am not sure this is a TEI ticket. If some one confirm this is a TEI ticket, please close this one. Thanks.

Info required for matching: conf-sanity 46a

Issue Links

• is related to: LU-5064 sanity-scrub test_13: ls should fail