[LU-18355] rolling-downgrade-client2 sanity test_56ei: Did not find any entries with expected projid 1234

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.16.0
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

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

This issue relates to the following test suite run:
https://testing.whamcloud.com/test_sets/0f26ee9e-e966-4059-83c1-873622ea7f36

test_56ei failed with the following error:

lfs: failed to set xattr for '/mnt/lustre/d56ei.sanity/file1234': Operation not supported
lfs: failed to set xattr for '/mnt/lustre/d56ei.sanity/link1234': Operation not supported
lfs: failed to set xattr for '/mnt/lustre/d56ei.sanity/char1234': Operation not supported
    0 - /mnt/lustre/d56ei.sanity//char1234
    0 - /mnt/lustre/d56ei.sanity//file0
    0 - /mnt/lustre/d56ei.sanity//link1234
    0 - /mnt/lustre/d56ei.sanity//file1234
Actual output:
0 /mnt/lustre/d56ei.sanity
0 /mnt/lustre/d56ei.sanity/char1234
0 /mnt/lustre/d56ei.sanity/file0
0 /mnt/lustre/d56ei.sanity/link1234
0 /mnt/lustre/d56ei.sanity/file1234
found_count: 0
 sanity test_56ei: @@@@@@ FAIL: Did not find any entries with expected projid 1234 

Test session details:
clients: https://build.whamcloud.com/job/lustre-master/4582 - 4.18.0-477.27.1.el8_8.x86_64
servers: https://build.whamcloud.com/job/lustre-master/4582 - 4.18.0-477.27.1.el8_lustre.x86_64

The full test session versions show that client2 is running 2.12.9, which is expected given the test session:

Nodes: 	

    onyx-78vm4 - Client 1 (2.16.0.RC1, x86_64)
    onyx-78vm5 - Client 2 (2.12.9, x86_64)
    onyx-78vm6 - OST 1, OST 2, OST 3, OST 4, OST 5, OST 6, OST 7 (2.16.0.RC1, x86_64)
    onyx-78vm12 - MDS 1 (2.16.0.RC1, x86_64)

It looks like rolling-downgrade-client2 is running the wrong test scripts for the Lustre version installed on the node? In this case, test_56ei is being run on the client, but this subtest was only added in v2_15_64-110-g501e5b2c8a and does not exist on 2.12.9 clients.

However, it looks like "lfs project -p" is trying to call an interface to set the xattr on a special file, but that doesn't exist in older clients?

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_56ei - Did not find any entries with expected projid 1234

Issue Links

• is related to: LU-18356 test-framework to fetch except list from server for interop testing
• is related to: LU-18027 lfs find with --printf prints incorrect projid on special files