[LU-3617] configure incorrectly finds no for RDMA events 14 and 15 on latest RHEL5

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Fix Version/s: Lustre 1.8.9
• Affects Version/s: Lustre 1.8.9
• Labels: mn8 patch
• Severity: 3
• Assignee: Amir Shehata (Inactive)
• Reporter: Kit Westneat (Inactive)

Description

We ran into an issue at Yale recently where the Lustre servers all got RDMA_CM_EVENT_TIMEWAIT_EXIT, which the servers didn't recognize and LBUGed on. There are two problems here. The first is that configure clearly doesn't do the right thing anymore, and the second is that Lustre shouldn't LBUG if it gets those events, even if configure doesn't find them.

I double checked on your build systems to make sure it wasn't just ours:
http://build.whamcloud.com/job/lustre-b1_8/arch=x86_64,build_type=server,distro=el5,ib_stack=inkernel/258/consoleFull

That's the official 1.8.9 build console if I'm not mistaken, and you can see:
checking if OFED has RDMA_CM_EVENT_ADDR_CHANGE... no
checking if OFED has RDMA_CM_EVENT_TIMEWAIT_EXIT... no