[LU-16708] sanity-sec test_61: mount failed Created: 04/Apr/23  Updated: 07/Jun/23  Resolved: 18/Apr/23

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.16.0

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Sebastien Buisson
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for S Buisson <sbuisson@ddn.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/a91bf668-35ac-4eeb-af25-7b74c05c462f

test_61 failed with the following error:

mount '-o ro' failed

Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/93564 - 4.18.0-425.10.1.el8_7.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/93564 - 4.18.0-425.10.1.el8_lustre.x86_64

Problem stems from the fact that additional mount options are ignored when using SSK, under some circumstances.

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-sec test_61 - mount '-o ro' failed



 Comments   
Comment by Gerrit Updater [ 04/Apr/23 ]

"Sebastien Buisson <sbuisson@ddn.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50523
Subject: LU-16708 tests: fix zconf_mount_clients for SSK
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: bd0d4644467192f5272bcc483663060314aec05a

Comment by Gerrit Updater [ 18/Apr/23 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/50523/
Subject: LU-16708 tests: fix zconf_mount_clients for SSK
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 1f95f84ffe2e603d8011065b76b9c561c3e73565

Comment by Peter Jones [ 18/Apr/23 ]

Landed for 2.16

Comment by Sergey Cheremencev [ 07/Jun/23 ]

Looks similar on master https://testing.whamcloud.com/test_sets/3e9fd06f-590c-40f8-9a75-db1e6f61469a

But now it is with 'o -rw': 'mount '-o rw' failed'

Generated at Sat Feb 10 03:29:20 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.