Bug 698219
| Summary: | Uninstalling ipa-client fails, if it joined replica when being installed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Namita Soman <nsoman> | ||||
| Component: | ipa | Assignee: | Rob Crittenden <rcritten> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Chandrasekar Kannan <ckannan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1 | CC: | benl, dpal, jgalipea | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ipa-2.1.0-1.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Cause: Apache needed to talk to 389-ds early during startup and if that communication failed then Apache would need to be restarted.
Consequence: This race condition could make a restarted IPA server unavailable.
Fix: Apache was trying to retrieve the LDAP schema a startup. This is now done as needed instead of at startup and it is also recoverable, so if it fails it will try again with the next request instead of simply not responding.
Result: The Apache server should be more robust and better handle LDAP availability issues.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-06 18:21:48 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Namita Soman
2011-04-20 13:04:51 UTC
Created attachment 493482 [details]
/var/log/httpd/error_log from replica
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. The replica wasn't actually accepting requests because it hadn't started up properly. It wasn't able to retrieve the LDAP schema: [Wed Apr 20 08:00:33 2011] [error] ipa: ERROR: Failed to start IPA: Unable to retrieve LDAP schema: Invalid credentials: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Permission denied) [Wed Apr 20 08:00:33 2011] [error] ipa: ERROR: Failed to start IPA: Unable to retrieve LDAP schema: Invalid credentials: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Permission denied) The bug is really: do not accept requests if the LDAP schema is not retrieved. Fixed in ticket https://fedorahosted.org/freeipa/ticket/583 master: 868d4e734ed0f22221f25a1067fbf57141b64c21 We now do lazy LDAP schema retrieval on a per-request basis if it hasn't yet been retrieved. This eliminates some of the timing problems we saw and removes the need to restart Apache to fix. Verified using steps above, and using ipa-client-2.1.2-2.el6.x86_64, ipa-server-2.1.2-2.el6.x86_64
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: Apache needed to talk to 389-ds early during startup and if that communication failed then Apache would need to be restarted.
Consequence: This race condition could make a restarted IPA server unavailable.
Fix: Apache was trying to retrieve the LDAP schema a startup. This is now done as needed instead of at startup and it is also recoverable, so if it fails it will try again with the next request instead of simply not responding.
Result: The Apache server should be more robust and better handle LDAP availability issues.
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-2011-1533.html |