[LU-8298] enabling gss causes possibly misleading warnings from tgt_init_sec_level()

• Status: Resolved
• Project: Lustre
• Fix Version/s: Lustre 2.9.0
• Type: Bug
• Priority: Minor
• Reporter: John Hammond
• Assignee: nasf (Inactive)
• Resolution: Fixed
• Severity: 3

Description

When connecting to a GSS-ized target we see the following warnings on the console

[80648.003579] Lustre: 1666:0:(tgt_handler.c:894:tgt_init_sec_level()) client 192.168.122.162@tcp -> target lustre-MDT0000 uses old version, run under security level 0.

These are likely misleading/unhelpful to the admin.

Issue Links

• is related to: LU-6971 Remove obsolete remote client and "lf...

Comments

[John Hammond]

After Fan Yong's patch for LU-6971 has landed the I think the "sec_level" functionality will be obsolete. If so then tgt_init_sec_level() can be removed completely and this message will go away.

[nasf (Inactive)]

After Fan Yong's patch for LU-6971 has landed the I think the "sec_level" functionality will be obsolete. If so then tgt_init_sec_level() can be removed completely and this message will go away.

With LU-6971 patch applied, you will NOT see the misguided message again. So we can close this ticket.

[nasf (Inactive)]

It will be disappear after LU-6971 patch (http://review.whamcloud.com/#/c/19789/) applied.

[John Hammond]

Still seeing this after http://review.whamcloud.com/#/c/19789/ landed. I think we can remove the sec_level parameter entirely. Fan Yong do you see any reason to keep it?

[Gerrit Updater]

John L. Hammond ([e-mail]) uploaded a new patch: http://review.whamcloud.com/20879
Subject: LU-8298 sec: remove obsolete sec_level parameter
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 9e6bb7777541c02a8ceb9e5634bf1f58544916b9

[nasf (Inactive)]

Still seeing this after http://review.whamcloud.com/#/c/19789/ landed. I think we can remove the sec_level parameter entirely. Fan Yong do you see any reason to keep it?

Currently, the sec_level is almost meaningless. I am fine to cleanup related code, just one concern about the interoperability issue when upgrade. If some customer has ever specified sec_level as conf parameter, then removing such interface may cause the new server does not recognise the old configuration after upgrading: either confused waring message or start failure. So please verify that, if happened, we can:
1) simply the interface as empty stub there for some time, or
2) add some special handling in class_process_proc_param().

[nasf (Inactive)]

I have verified the upgrading case, and updated the class_process_proc_param() in the patch to handle sec_level specially.

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/20879/
Subject: LU-8298 sec: remove obsolete sec_level parameter
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 881e4d68346be5623c4045dad0d6a50d4954f6fb

[nasf (Inactive)]

The patch has been landed to master.