Bug 749351

Summary:	krb5-auth-dialog caches negative DNS response, It shouldn't
Product:	[Fedora] Fedora	Reporter:	Trever Adams <trever>
Component:	krb5-auth-dialog	Assignee:	Itamar Reis Peixoto <itamar>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	18	CC:	itamar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-05 11:51:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Trever Adams 2011-10-26 19:02:57 UTC

Description of problem:
On laptops and the like where wireless is used, krb5-auth-dialog frequently starts with no network connection. It caches the inability to look up the krb server. It keeps this for a LONG time.

This causes it to be useless for getting/renewing credentials. kinit works fine.

The solution is for krb5-auth-dialog to either have a short time out on the caching of the failed lookup, or better, to not cache it at all.

Version-Release number of selected component (if applicable):
krb5-auth-dialog-3.2.1-1.fc16.x86_64

Steps to Reproduce:
1. Have network off
2. Start krb5-auth-dialog w/ expired credentials
3. Start network
4. Try to renew
  
Actual results:
Continues to complain about not being able to find the server

Expected results:
Should work fine

Comment 1 Trever Adams 2012-06-24 07:22:04 UTC

Still a problem in F17 with krb5-auth-dialog-3.2.1-3.fc17.x86_64

Comment 2 Trever Adams 2013-01-17 04:44:44 UTC

This is still present in F18. Annoyingly, krb5-auth-dialog doesn't start now and I cannot find where to force it to start.

Comment 3 Fedora End Of Life 2013-12-21 08:29:52 UTC

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 4 Fedora End Of Life 2014-02-05 11:51:18 UTC

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.