Bug 1440411

Summary:	[REGRESSION] gssproxy update 0.5.1-3.fc25 -> 0.7.0-3.fc25 broke NFS server
Product:	[Fedora] Fedora	Reporter:	James <james>
Component:	gssproxy	Assignee:	Robbie Harwood <rharwood>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	25	CC:	gdeschner, rharwood, ssorce
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-09 10:14:17 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:

Description James 2017-04-08 16:11:16 UTC

Description of problem:
I'm using a Kerberised NFSv4 server backed by FreeIPA (the same machine). Upgrading to gssproxy-0.7.0-3.fc25 breaks my setup with permissions denied and autofs mounts hanging on clients.

Going back to 0.5.1-3.fc25 resolves this.

Version-Release number of selected component (if applicable):
gssproxy-0.7.0-3.fc25

How reproducible:
Always.

Steps to Reproduce:
1. Update gssproxy.

Actual results:
Inaccessible NFS export.

Expected results:
Things work as before.

Comment 1 James 2017-04-09 10:14:17 UTC


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