Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-8795

The user cannot access lustre even if they successfully authenticate by kinit

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Lustre 2.9.0
    • Fix Version/s: Lustre 2.9.0
    • Labels:
      None
    • Environment:
      Centos7.2 3.10.0-327.el7.x86_64
      Lustre 2.8.55_19_ga84250b
    • Epic/Theme:
    • Severity:
      3
    • Rank (Obsolete):
      9223372036854775807

      Description

      1. I find one problem for Kerberos in Lustre. I do not know whether it is a setting error or bug. When we activate the Kerberos function in all servers (MGS, MDS, and OSS) and clients mount lustre with krb5 option, root can access the lustre file system. However, the normal users can not access the lustre even if they have authenticated through Kerberos (kinit). The following error logs are messages when normal user wants to access lustre.
      lgss_keyring: [21277]:TRACE:main(): start parsing parameters
      lgss_keyring: [21277]:INFO:main(): key 698610133, desc 1002@2f, ugid 1002:1002, sring 44699816, coinfo 47:krb5:1002:1002::
      lgss_keyring: [21277]:ERROR:parse_callout_info(): short of components
      lgss_keyring: [21277]:ERROR:main(): can't extract callout info: 47:krb5:1002:1002::
      kernel: LustreError: 21275:0:(gss_keyring.c:846:gss_sec_lookup_ctx_kr()) failed request key: -126
      kernel: LustreError: 21275:0:(sec.c:452:sptlrpc_req_get_ctx()) req ffff881f4f703f00: fail to get context
      kernel: LustreError: 21275:0:(file.c:3332:ll_inode_revalidate_fini()) hpcfs: revalidate FID [0x200000bd0:0x1:0x0] error: rc = -111

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jfilizetti Jeremy Filizetti
                Reporter:
                sebg-crd-pm sebg-crd-pm (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: