[LU-16133] sanity-lnet test_210 can fail with "Expected discovery to fail" Created: 01/Sep/22 Updated: 11/Sep/22 Resolved: 11/Sep/22 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Neil Brown | Assignee: | WC Triage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
sanity-lnet test_210 sometimes fails with "Expected discovery to fail". The "lnetctl discover" command runs lnet_discover() which clears LNET_PEER_NIDS_UPTODATE on the assumption that will cause a ping to be attempted. However if LNET_PEER_DATA_PRESENT is set, then lnet_peer_discovery() won't even test LNET_PEER_NIDS_UPTODATE but will call lnet_peer_data_present(), which will succeed.
|
| Comments |
| Comment by Neil Brown [ 11/Sep/22 ] |
|
This turned out to be a bug in a patch I was testing - sorry.
|