Bug 1195295
| Summary: | DNS errors after IPA upgrade due to broken ReplSync | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
| Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.1 | CC: | drieden, ipa-maint, jbiao, jgalipea, jkurik, lkrispen, mbasti, mkosek, nhosoi, nkinder, pm-eus, pspacek, pvoborni, rcritten, rmeggins, spoore, sramling, tbordaz |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.3.1-14.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Prior to this update, under certain circumstances, the "systemctl stop dirsrv.target" command, which 389-ds-base issues before starting the upgrade scripts, did not stop all installed servers. Consequently, if the servers were not completely stopped before the upgrade scripts started to run, the upgrade failed. With this update, 389-ds-base issues the "systemctl stop" command for each server instance, which ensures that all installed servers are shut down before the upgrade scripts start. As a result, the upgrade no longer fails in the described situation.
|
Story Points: | --- |
| Clone Of: | 1189154 | Environment: | |
| Last Closed: | 2015-03-05 14:09:57 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: | |||
| Bug Depends On: | 1189154 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2015-02-23 14:53:15 UTC
Verified. Version :: 389-ds-base-1.3.3.1-15.el7_1.x86_64 Results :: 10 jobs run and did not see this DNS error. Considering this and that I had previous patch testing covered a large number of test runs, this appears to be fixed. 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. https://rhn.redhat.com/errata/RHBA-2015-0626.html |