Bug 1149190
| Summary: | pengine segfault with remote nodes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Iain Patterson <bugzilla.redhat> | ||||
| Component: | pacemaker | Assignee: | Andrew Beekhof <andrew> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | abeekhof, andrew, dvossel, fdinitto, lhh | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-30 01:39:44 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: |
|
||||||
This looks like it is directly related to this issue I fixed a few weeks ago. https://github.com/ClusterLabs/pacemaker/commit/4b63caca1f1e9190191ca16ece08036c96e05c02 Probably worth rolling some new packages for fedora then Preliminary testing with a build from commit 272814b, ie HEAD as of yesterday, is looking good. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 943714 [details] abrt stuff and corosync.conf Description of problem: pengine segfaults when KVM guests are added to cluster as remote nodes. Version-Release number of selected component (if applicable): pacemaker-1.1.11-1.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Create corosync/pacemaker cluster, eg using udpu votequorum. A suitable corosync.conf is attached to this bug. 2. Create remote node. pcs resource create lx218 VirtualDomain hypervisor=qemu:///system config=/etc/libvirt/qemu/lx218.xml meta remote-node=phillips-lx218 Here phillips-lx218 is the hostname of the KVM node defined as lx218. 3. Sync /etc/corosync/authkey to guest and start pacemaker_remote service. Verify that the host can connect to port 3121 on the guest. Actual results: pengine segfaults on the hypervisor. Sep 27 08:49:12 kvm210 kernel: pengine[18101]: segfault at 1 ip 0000003904c490cf sp 00007fffc97f59a0 error 4 in libc-2.18.so[3904c00000+1b4000] hypervisor node disconnects then rejoins the cluster. Remote node never joins the cluster. Expected results: Remote node joins the cluster and is available to host resources. Additional info: Stopping all guests on the hypervisor and creating a clean cluster works initially. If all remote-node resources are added when the corresponding guest is stopped and are allowed to be started by pacemaker, everything works until the pacemaker service is restarted. As soon as a guest is already running when the resource is added, the hypervisor node enters a restart/segfault loop. I have reproduced the bug on three different clusters on separate machines including on a trivial cluster with only one node (expected_votes set to 1). The bug persists with (self-compiled) pacemaker 1.1.12 packages. With the remote-node metadata removed from the KVM resources the guests are monitored and can be controlled by pacemaker as expected. Only configuring them as remote nodes fails.