Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 845251 - sssd does not try another server when unable to resolve hostname
sssd does not try another server when unable to resolve hostname
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd (Show other bugs)
6.4
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Jakub Hrozek
Kaushik Banerjee
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-08-02 09:16 EDT by Dmitri Pal
Modified: 2014-08-04 07:58 EDT (History)
4 users (show)

See Also:
Fixed In Version: sssd-1.9.1-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: When multiple servers are configured and SSSD is unable to resolve hostname of a server, it does not try next server in the list. Consequence: SSSD went offline, even when a working server was present in configuration file after the one with unresolvable hostname. Fix: SSSD tries next server. Result: Failover works as expected.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-21 04:27:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0508 normal SHIPPED_LIVE Low: sssd security, bug fix and enhancement update 2013-02-20 16:30:10 EST

  None (edit)
Description Dmitri Pal 2012-08-02 09:16:28 EDT 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1446

When SSSD is unable to resolve hostname of a server, it immediately goes to offline mode instead of trying next configured server.

Log file and sssd.conf are attached.
Comment 3 errata-xmlrpc 2013-02-21 04:27:34 EST 
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.

http://rhn.redhat.com/errata/RHSA-2013-0508.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.