Bug 590527 - SSSD: Document use of SRV records in failover
SSSD: Document use of SRV records in failover
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Deployment_Guide (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: ---
Assigned To: David O'Brien
ecs-bugs
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-10 00:49 EDT by David O'Brien
Modified: 2010-11-11 10:28 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-11 10:28:23 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)

  None (edit)
Description David O'Brien 2010-05-10 00:49:58 EDT
Description of problem:
Refer to email "[PATCH] Support SRV servers in failover" on sssd-devel list for details.

Need to add to Configuring Failover section in Deployment Guide.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 David O'Brien 2010-05-10 00:52:35 EDT
Draft is done. Adding details of how SRV records work, and how SSSD, failover, and SRV records all work together.
Comment 3 RHEL Product and Program Management 2010-05-10 02:00:03 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 4 David O'Brien 2010-05-10 23:29:59 EDT
Created commit dc208c0: updated failover with how to use SRV records
Comment 8 releng-rhel@redhat.com 2010-11-11 10:28:23 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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