Bug 1410110
| Summary: | cluster recovery takes too long after network failure | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | michal novacek <mnovacek> | ||||||
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 6.9 | CC: | abeekhof, cfeist, cluster-maint, kgaillot, mnovacek, tlavigne | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | 6.9 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | pacemaker-1.1.15-5.el6 | Doc Type: | No Doc Update | ||||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-03-21 09:51:09 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
michal novacek
2017-01-04 13:39:34 UTC
if it is always reproducable, very Created attachment 1241679 [details]
virt-056:/var/log/cluster/corosync.log for Jan 4
I have backported upstream commits 31db95be, df497ff, de5c6c73, 64c77a7, and 3a94d53c, which at least partially resolve this issue. I am not certain this is a full solution, but given the current deadlines for 6.9, I think it is important to get these in the release. We will consider this the fix for this bz; if the problem recurs with the new packages, please open a new bz. Documentation: Since this has not been reported by a customer, and only affects recovery time rather than data integrity, I do not think we need a release note for this. I have verified that the recovery of the cluster in switch failure scenario will take less than five minutes with pacemaker-1.1.15-5.el6 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/RHEA-2017-0629.html |