Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
Judging by the existing comments, other related bugs and the pointed
upstream discussion thread, it appears that the wrong lrmd was being
set after upgrade and that led existing cluster to confusion when
connecting to the local resource manager daemon.
It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.
** Also affects: pacemaker (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu Trusty)
Status: New => Triaged
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: pacemaker (Ubuntu Trusty)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1425431
Title:
Pacemaker [SIGSEGV - Segmentation violation] using with Heartbeat 3.x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1425431/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
