[LU-14181] sanity test_64e fails with SHARED_KEY on RHEL/CentOS 8.2

• Status: Reopened
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: Sebastien Buisson
• Resolution: Unresolved
• Labels: always_except
• Severity: 3

Description

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

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/2e038072-2f42-4dca-bb3d-ce025d30fbaa

test_64e failed with the following error:

init grants: grants mismatch: 0, expected 2146304

This happens with any SSK flavor when client runs on RHEL/CentOS 8.2.

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_64e - init grants: grants mismatch: 0, expected 2146304

Comments

[Gerrit Updater]

Sebastien Buisson ([e-mail]) uploaded a new patch: https://review.whamcloud.com/40865
Subject: LU-14181 tests: except sanity test_64e 64f with SHARED_KEY
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: f819cce3ed0fa11e4d2e6a071dcc90b3a1f49ca2

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/40865/
Subject: LU-14181 tests: except sanity test_64e 64f with SHARED_KEY
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: aa3bdbc23bc86bae565e78b38946f4ac8fcbeacb

[Peter Jones]

Landed for 2.14

[Gerrit Updater]

Sebastien Buisson ([e-mail]) uploaded a new patch: https://review.whamcloud.com/40999
Subject: LU-14181 tests: except sanity test_64e 64f with SHARED_KEY
Project: fs/lustre-release
Branch: b2_12
Current Patch Set: 1
Commit: 23a43d24e2a87f1a3b580bdff979461c7b4c0b9a

[Andreas Dilger]

ALWAYS_EXCEPT isn't really meant to be a permanent place to skip tests. It is meant as a place to "temporarily" disable subtests that should be passing, but are consistently failing for some reason. That is why we don't allow bugs to be closed with the always_except marker on them.

If these tests are never expected to work with SSK, then there should be a check in the test itself, and the test skipped with a short explanation of why it is skipped.

It isn't clear to me why SSK would cause the OST grant to be incorrect? There wasn't any explanation in patch https://review.whamcloud.com/40865 "LU-14181 tests: except sanity test_64e 64f with SHARED_KEY", and there isn't any explanation in this ticket except that these tests are disabled.

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/40999/
Subject: LU-14181 tests: except sanity test_64e 64f with SHARED_KEY
Project: fs/lustre-release
Branch: b2_12
Current Patch Set:
Commit: 5bc9f3aa054c944435f56dcafc41ca97702888b6

[Patrick Farrell]

I wonder if this isn't just a timing thing and is perhaps fixed with LU-16541?  Sebastien, are you able to check?

[Gerrit Updater]

"Sebastien Buisson <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/52123
Subject: LU-14181 tests: re-enable sanity test_64f with SHARED_KEY
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2af4f9b51f15ffe2f235db52b23e7f125d3d2cad

[Gerrit Updater]

"Sebastien Buisson <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/52124
Subject: LU-14181 dbg: run sanity test_64f on SSK without LU-16541
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 828fcf93f1ed89f60256904ca2c20795cf82c27b

[Sebastien Buisson]

I have pushed test patches to see how it goes with sanity test_64f and SSK now that LU-16541 has landed. But initially the problem was also seen with sanity test_64e. Do you think the same timing thing could be addressed in test_64e?

[Sebastien Buisson]

Unfortunately, sanity test_64f still fails with SSK:
https://testing.whamcloud.com/test_sessions/66a85858-4ea7-4bd2-8aff-106d6c7dadf6