Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1356383

Summary:	SSH authentication for gluster servers no longer using the gnome prompt for password.
Product:	[Community] GlusterFS	Reporter:	Nigel Babu <nigelb>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, mscherer
Target Milestone:	---	Keywords:	Triaged
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:	2016-08-02 04:01:23 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 Nigel Babu 2016-07-14 03:20:37 UTC

I've noticed this in the logs

debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
Server krbtgt/GLUSTER.ORG not found in Kerberos database

debug1: Unspecified GSS failure.  Minor code may provide more information
Server krbtgt/GLUSTER.ORG not found in Kerberos database

debug1: Unspecified GSS failure.  Minor code may provide more information


debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: publickey


Is this because of freeipa? Considering it's no longer required, can we turn it off?

Comment 1 M. Scherer 2016-07-14 10:50:58 UTC

That's not a very helpful bug report. You do not tell what you do or how you do that, or what logs do trigger this. 


And no, we will not turn freeipa off.

Comment 2 Nigel Babu 2016-07-14 11:05:43 UTC

All I did was `ssh root.org`. To get this logs though, I did `ssh -v root.org`.

Comment 3 M. Scherer 2016-07-14 15:15:29 UTC

Well, the log is harmless so I am inclined to keep it this way, unless this result in a slowdown or a problem ?

Comment 4 Nigel Babu 2016-08-02 04:01:23 UTC

This works fine now. I think it was a problem on my computer?