Bug 1460070
Summary: | 1.3.5.10-20 replication halt - pending list first CSN not committed, pending list increasing | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Marc Sauton <msauton> | |
Component: | 389-ds-base | Assignee: | mreynolds | |
Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 7.3 | CC: | gparente, nkinder, rmeggins, tbordaz, tmihinto, toneata | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | 389-ds-base-1.3.7.5-4.el7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1476161 (view as bug list) | Environment: | ||
Last Closed: | 2018-04-10 14:16:50 UTC | Type: | Bug | |
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: | ||||
Bug Blocks: | 1420851, 1472344, 1476161 |
Description
Marc Sauton
2017-06-09 01:01:51 UTC
Upstream ticket https://pagure.io/389-ds-base/issue/49287 There has been a great collaboration for a patch in upstream ticket https://pagure.io/389-ds-base/issue/49287 (Thank Ludwig, Thierry, William !) for a sosreport provide in the salesforce case number 01717173 , the customer's consumer system is with 420-sosreport-EVAIN.01717173-20170607105939-consumer.tar.xz 389-ds-base-1.3.5.10-20.el7_3.x86_64 redhat-release-server-7.2-9.el7.x86_64 the patch 0001-Ticket-49287-v3-extend-csnpl-handling-to-multiple-ba.patch from https://pagure.io/389-ds-base/issue/raw/6d855f63e2e6968692eb06332c322aedbdc3e528232e63881344077864be75ec-0001-Ticket-49287-v3-extend-csnpl-handling-to-multiple-ba.patch seem quite seriosu and "invasive", so: is it "ok" to provide a hotfix? I do not know how often this condition happened at the customer's site, but do we want to consider a 7.4.z ? Fixed upstream 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://access.redhat.com/errata/RHBA-2018:0811 |