[LU-5762] Interop 2.6.0<->2.7 sanity test_154a: create lov data thru .lustre should fail

• Status: Closed
• Project: Lustre
• Affects Version/s: Lustre 2.6.0, Lustre 2.5.3, Lustre 2.8.0, Lustre 2.5.4, Lustre 2.5.5
• Fix Version/s: Lustre 2.5.4
• Type: Bug
• Priority: Major
• Reporter: Maloo
• Assignee: Sarah Liu
• Resolution: Fixed

Environment

server: lustre-master build #2691
client: 2.6.0

• Severity: 3

Description

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

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/eeeafab8-5550-11e4-a570-5254006e85c2.

The sub-test test_154a failed with the following error:

create lov data thru .lustre should fail.

CMD: shadow-6vm12 /usr/sbin/lctl get_param -n version
change mode of /mnt/lustre/.lustre/fid to 777
restore mode of /mnt/lustre/.lustre/fid to 100
Succeed in opening file "/mnt/lustre/f154a.sanity-2"(flags=O_LOV_DELAY_CREATE)
cp /etc/passwd /mnt/lustre/.lustre/fid/[0x200002b11:0x23:0x0]
 sanity test_154a: @@@@@@ FAIL: create lov data thru .lustre should fail. 

Info required for matching: sanity 154a

Issue Links

• is related to: LU-5424 Test failuresanity test_154b: create ...

Comments

[Andreas Dilger]

The behaviour of this code changed in LU-5424 patch http://review.whamcloud.com/11248 "mdt: allow open by FID to create striping". The check in dot_lustre_fid_permission_check() that is failing was disabled in master for server versions older than 2.6.50:

        if [ $(lustre_version_code $SINGLEMDS) -ge $(version_code 2.6.50) ]
        then # LU-5424
                echo "cp /etc/passwd $MOUNT/.lustre/fid/$fid"
                cp /etc/passwd $MOUNT/.lustre/fid/$fid ||
                        error "create lov data thru .lustre failed"
        fi

We need a patch the old client in order to disable this test for server versions newer than 2.6.50. Also, for interop testing we don't run the b2_6 branch, but only the 2.6.0 release so we would also have to make a 2.6.1 release for this, which will likely not happen.

We can fix this test on b2_5, and that should be done to avoid this spurious test failure.

[Saurabh Tandan (Inactive)]

Another instance for following interop config
Server: Master, Build# 3266, Tag 2.7.64
Client: 2.5.5, b2_5_fe/62
https://testing.hpdd.intel.com/test_sets/ac332386-9fcc-11e5-a33d-5254006e85c2

[Saurabh Tandan (Inactive)]

Server: Master, Build# 3266, Tag 2.7.64 , RHEL 7
Client: 2.5.5, b2_5_fe/62
https://testing.hpdd.intel.com/test_sets/e4f27f18-9fff-11e5-a33d-5254006e85c2

[Saurabh Tandan (Inactive)]

Another instance found for interop : EL6.7 Server/2.5.5 Client
Server: master, build# 3303, RHEL 6.7
Client: 2.5.5, b2_5_fe/62
https://testing.hpdd.intel.com/test_sets/24b4b54e-bad6-11e5-9137-5254006e85c2

[Saurabh Tandan (Inactive)]

Another instance found for interop tag 2.7.66 - EL6.7 Server/2.5.5 Client, build# 3316
https://testing.hpdd.intel.com/test_sets/9ed7c1d8-cc9f-11e5-963e-5254006e85c2

Another instance found for interop tag 2.7.66 - EL7 Server/2.5.5 Client, build# 3316
https://testing.hpdd.intel.com/test_sets/5ea975e2-cc46-11e5-901d-5254006e85c2

[Saurabh Tandan (Inactive)]

Another instance found for interop - EL6.7 Server/2.5.5 Client, tag 2.7.90.
https://testing.hpdd.intel.com/test_sessions/f99a2d60-d567-11e5-bc47-5254006e85c2
Another instance found for interop - EL7 Server/2.5.5 Client, tag 2.7.90.
https://testing.hpdd.intel.com/test_sessions/93baffee-d2ae-11e5-8697-5254006e85c2

[Andreas Dilger]

Saurabh, would it be possible for you to submit a patch for b2_5_fe and b_ieel2_0 to skip this test for servers newer than 2.6.50.

[Saurabh Tandan (Inactive)]

Yeah sure. Thanks