Bug 652275 - Unable to mount nfs4 krb5p shares exported by a fedora12 server
Summary: Unable to mount nfs4 krb5p shares exported by a fedora12 server
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-11 14:17 UTC by Thomas Sailer
Modified: 2012-08-16 22:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 22:01:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 652273 0 low CLOSED Unable to mount nfs4 krb5p shares exported by a fedora12 server 2021-02-22 00:41:40 UTC

Internal Links: 652273

Description Thomas Sailer 2010-11-11 14:17:15 UTC
Description of problem:
After upgrading a fully up-to-date and working fedora13 client to fedora14 two days ago, I am no longer able to mount nfs4 krb5p shares exported by a fedora12 freeipa server.

Version-Release number of selected component (if applicable):
kernel-2.6.35.6-48.fc14.x86_64

How reproducible:
always, on two different clients

Steps to Reproduce:
mount -t nfs4 -o soft,intr,rsize=8192,wsize=8192,rw,sec=krb5p server.xxxx.xxx:/some/path/exported /tmp/x
  
Actual results:
mount fails

Expected results:
mount succeeds

Additional info:

rpc.gssd on the client reports the following:

beginning poll
dir_notify_handler: sig 37 si 0x7fff99e83030 data 0x7fff99e82f00
dir_notify_handler: sig 37 si 0x7fff99e7f930 data 0x7fff99e7f800
dir_notify_handler: sig 37 si 0x7fff99e82ef0 data 0x7fff99e82dc0
handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt38)
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 '
handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt38)
process_krb5_upcall: service is '<null>'
Full hostname for 'server.xxxx.xxx' is 'server.xxxx.xxx'
Full hostname for 'clnt.xxxx.xxx' is 'clnt.xxxx.xxx'
Key table entry not found while getting keytab entry for 'root/clnt.xxxx.xxx'
Success getting keytab entry for 'nfs/clnt.xxxx.xxx'
Successfully obtained machine credentials for principal 'nfs/clnt.xxxx.xxx' stored in ccache 'FILE:/tmp/krb5cc_machine_XXXX.XXX'
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_XXXX.XXX' are good until 1289651734
using FILE:/tmp/krb5cc_machine_XXXX.XXX as credentials cache for machine creds
using environment variable to select krb5 ccache FILE:/tmp/krb5cc_machine_XXXX.XXX
creating context using fsuid 0 (save_uid 0)
creating tcp client for server server.xxxx.xxx
DEBUG: port already set to 2049
creating context with server nfs.xxx
WARNING: Failed to create krb5 context for user with uid 0 for server server.xxxx.xxx
WARNING: Failed to create machine krb5 context with credentials cache FILE:/tmp/krb5cc_machine_XXXX.XXX for server server.xxxx.xxx
WARNING: Machine cache is prematurely expired or corrupted trying to recreate cache for server server.xxxx.xxx
Full hostname for 'server.xxxx.xxx' is 'server.xxxx.xxx'
Full hostname for 'clnt.xxxx.xxx' is 'clnt.xxxx.xxx'
Key table entry not found while getting keytab entry for 'root/clnt.xxxx.xxx'
Success getting keytab entry for 'nfs/clnt.xxxx.xxx'
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_XXXX.XXX' are good until 1289651734
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_XXXX.XXX' are good until 1289651734
using FILE:/tmp/krb5cc_machine_XXXX.XXX as credentials cache for machine creds
using environment variable to select krb5 ccache FILE:/tmp/krb5cc_machine_XXXX.XXX
creating context using fsuid 0 (save_uid 0)
creating tcp client for server server.xxxx.xxx
DEBUG: port already set to 2049
creating context with server nfs.xxx
WARNING: Failed to create krb5 context for user with uid 0 for server server.xxxx.xxx
WARNING: Failed to create machine krb5 context with credentials cache FILE:/tmp/krb5cc_machine_XXXX.XXX for server server.xxxx.xxx
WARNING: Failed to create machine krb5 context with any credentials cache for server server.xxxx.xxx
doing error downcall
dir_notify_handler: sig 37 si 0x7fff99e83030 data 0x7fff99e82f00
dir_notify_handler: sig 37 si 0x7fff99e83030 data 0x7fff99e82f00
dir_notify_handler: sig 37 si 0x7fff99e82f30 data 0x7fff99e82e00
dir_notify_handler: sig 37 si 0x7fff99e7dfb0 data 0x7fff99e7de80
dir_notify_handler: sig 37 si 0x7fff99e7dfb0 data 0x7fff99e7de80
dir_notify_handler: sig 37 si 0x7fff99e7dfb0 data 0x7fff99e7de80
dir_notify_handler: sig 37 si 0x7fff99e7dfb0 data 0x7fff99e7de80
destroying client /var/lib/nfs/rpc_pipefs/nfs/clnt39
destroying client /var/lib/nfs/rpc_pipefs/nfs/clnt38

I need to downgrade the kernel and krb5* to the Fedora13 version to get
nfs4 working again.

Comment 1 Thomas Sailer 2010-11-11 14:19:22 UTC

*** This bug has been marked as a duplicate of bug 652273 ***

Comment 2 Fedora End Of Life 2012-08-16 22:01:05 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.