Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sssd failover leads to delayed and failed logins #5075

Closed
sssd-bot opened this issue May 2, 2020 · 1 comment
Closed

sssd failover leads to delayed and failed logins #5075

sssd-bot opened this issue May 2, 2020 · 1 comment
Assignees
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/4114


Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1769755

Description of problem:
During testing IPA deployment in my customers environment and running various
fail over test scenarios, we recognized that under some circumstances, fail
over didn't work as expected and resulted in failed or delayed (~ 60 - 70
seconds) logins.

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


How reproducible: Always.


Steps to Reproduce:
1. Client connected to two IPA servers (A and B)
2. Cut connection to server A
3. Login to client
4. Allow connection to server A
5. Cut connection to server B

If you keep doing this repeatedly, at some point the fail back from B to A
doesn't work; SSSD takes a very long time to recognize the connection to server
A is restored and uses it again.

Actual results: Logins delayed or not working at all


Expected results: Fail over + fail back work smoothly


Additional info:
* This was already analysed by Sumit Bose and he has a fix for it available.
* Customer case will be linked.
* Exception set to ?
* We'll need this fix in 7.7 z-stream (for EUS) later as well
* It also applies to RHEL 8 AFAIK

Comments


Comment from sbose at 2019-11-07 13:27:41

Metadata Update from @sbose:


Comment from sbose at 2019-11-07 17:13:53

Metadata Update from @sbose:

  • Issue assigned to sbose

Comment from sbose at 2019-11-15 16:31:37

PR: #941


Comment from sbose at 2019-11-15 16:31:59

Metadata Update from @sbose:

  • Custom field patch adjusted to on

Comment from pbrezina at 2019-11-29 11:26:10

Commit 707fdf04 relates to this ticket


Comment from pbrezina at 2019-11-29 11:26:10

Commit b9a53cfc relates to this ticket


Comment from pbrezina at 2019-11-29 11:26:11

  • master
    • 707fdf0 - ipa: add failover to access checks
    • b9a53cf - ipa: add failover to override lookups

Comment from pbrezina at 2019-11-29 11:26:11

Metadata Update from @pbrezina:

  • Issue close_status updated to: Fixed
  • Issue status updated to: Closed (was: Open)

Comment from pbrezina at 2019-11-29 12:16:02

  • sssd-1-16
    • 4897063 - ipa: add failover to override lookups
    • a4dd1eb - ipa: add failover to access checks
@sssd-bot sssd-bot added Bugzilla Closed: Fixed Issue was closed as fixed. labels May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
sumit-bose added a commit to sumit-bose/sssd that referenced this issue Jun 5, 2020
In the ipa_subdomain_account request failover handling was missing.

Related to SSSD#5075
      (was https://pagure.io/SSSD/sssd/issue/4114)
pbrezina pushed a commit that referenced this issue Jun 18, 2020
In the ipa_subdomain_account request failover handling was missing.

Related to #5075
      (was https://pagure.io/SSSD/sssd/issue/4114)

Reviewed-by: Pawel Polawski <ppolawsk@redhat.com>
pbrezina pushed a commit that referenced this issue Jun 18, 2020
In the ipa_subdomain_account request failover handling was missing.

Related to #5075
      (was https://pagure.io/SSSD/sssd/issue/4114)

Reviewed-by: Pawel Polawski <ppolawsk@redhat.com>
(cherry picked from commit df632ee)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

3 participants