Bug 1223661
| Summary: | Hangs when logging in on NFS4 /home | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Yongcheng Yang <yoyang> |
| Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED ERRATA | QA Contact: | Yongcheng Yang <yoyang> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.6 | CC: | bfields, coughlan, eguan, fs-qe, jiyin, jlayton, m.a.young, rh-bugzilla, salmy, ssorce, steved, yoyang |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-utils-1.2.3-66.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1056658 | Environment: | |
| Last Closed: | 2016-05-11 00:03:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1268411 | ||
|
Comment 6
Steve Dickson
2016-02-12 19:32:17 UTC
The reason you are seeing this failure is because
the the bad gss creds cause by the su
> [root@ibm-x3550m3-06 ~]# su testUser
> bash: /home/testUser/.bashrc: Permission denied
> bash-4.1$ ls -la /home/testUser
> ls: cannot access /home/testUser: Permission denied <<< failed before kinit
are cached and used by the kernel by the during the ls
[Note there is no upcalls happening]
So even when the user kinits valid creds, the old invalid (cached)
creds are being used for the ls.
Now if you exit out of the user shell and su back to
the valid creds will be used.
In a nut shell, you have to kinit before accessing the
directory.
(In reply to Steve Dickson from comment #11) > The reason you are seeing this failure is because > the the bad gss creds cause by the su > > > [root@ibm-x3550m3-06 ~]# su testUser > > bash: /home/testUser/.bashrc: Permission denied > > bash-4.1$ ls -la /home/testUser > > ls: cannot access /home/testUser: Permission denied <<< failed before kinit > > are cached and used by the kernel by the during the ls > [Note there is no upcalls happening] > > So even when the user kinits valid creds, the old invalid (cached) > creds are being used for the ls. > > Now if you exit out of the user shell and su back to > the valid creds will be used. > > In a nut shell, you have to kinit before accessing the > directory. Still got failed even kinit before accessing. [root@hp-dl388g8-16 ~]# mount -o rw,sec=krb5 $SERVERS:/home/testUser /home/testUser [root@hp-dl388g8-16 ~]# nfsstat -m /home/testUser from ibm-x3550m3-06.rhts.eng.pek2.redhat.com:/home/testUser Flags: rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=10.73.194.81,minorversion=0,local_lock=none,addr=10.73.4.149 [root@hp-dl388g8-16 ~]# su testUser -c "echo redhat | kinit" <<<< kinit before Password for testUser: [root@hp-dl388g8-16 ~]# su testUser bash: /home/testUser/.bashrc: Permission denied bash-4.1$ bash-4.1$ kinit Password for testUser: bash-4.1$ echo $? 0 bash-4.1$ bash-4.1$ exit exit [root@hp-dl388g8-16 ~]# su testUser <<<<<<<<<< exit out and su back again bash: /home/testUser/.bashrc: Permission denied bash-4.1$ ls /home/testUser/ ls: cannot open directory /home/testUser/: Permission denied bash-4.1$ kinit Password for testUser: bash-4.1$ ls /home/testUser/ ls: cannot open directory /home/testUser/: Permission denied bash-4.1$ exit exit [root@hp-dl388g8-16 ~]# su testUser bash: /home/testUser/.bashrc: Permission denied bash-4.1$ exit exit [root@hp-dl388g8-16 ~]# kadmin -p root/admin -w redhat -q "listprincs" | grep testUser testUser [root@hp-dl388g8-16 ~]# (In reply to Yongcheng Yang from comment #12) > (In reply to Steve Dickson from comment #11) > > [root@hp-dl388g8-16 ~]# mount -o rw,sec=krb5 $SERVERS:/home/testUser > /home/testUser > [root@hp-dl388g8-16 ~]# nfsstat -m > /home/testUser from ibm-x3550m3-06.rhts.eng.pek2.redhat.com:/home/testUser > Flags: > rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp, > port=0,timeo=600,retrans=2,sec=krb5,clientaddr=10.73.194.81,minorversion=0, > local_lock=none,addr=10.73.4.149 > > [root@hp-dl388g8-16 ~]# su testUser -c "echo redhat | kinit" <<<< kinit > before > Password for testUser: > [root@hp-dl388g8-16 ~]# su testUser > bash: /home/testUser/.bashrc: Permission denied Its still the same problem... How can the kinit work when the home directory can not be accessed? Is there a /tmp/krb5cc_XXX context being created? I'm guess not... The normal procedure is to get the krb5 ticket before accessing the file system. There is no Hang occurred now. And the "Permission denied" is my configuration's problem according to Comment 16 Move to VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0868.html |