[Bug 1869622] [NEW] [focal] corosync v3.0.3 last upstream fixes
Public bug reported: Apart from fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = coverity fix -> ca320bea votequorum: set wfa status only on startup = fix for corner case -> 5f543465 quorumtool: exit on invalid expected votes = fix -> 0c16442f votequorum: Change check of expected_votes = fix -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix -> 89b0d62f stats: Check return code of stats_map_get = fix -> 56ee8503 quorumtool: Assert copied string length = assert (better support) -> 1fb095b0 notifyd: Check cmap_track_add result = assert (better support) -> 8ff7760c cmapctl: Free bin_value on error (fix) -> 35c312f8 votequorum: Assert copied strings length = assert (better support) -> 29109683 totemknet: Assert strcpy length assert (better support) -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call -> a24cbad5 totemconfig: Initialize warnings variable = build fix -> 74eed54a sync: Assert sync_callbacks.name length = assert (better support) -> 380b744e totemknet: Don't mix corosync and knet error codes = fix -> 624b6a47 stats: Assert value_len when value is needed = assert (bet support) -> 09f6d34a logconfig: Remove double free of value = fix -> efe48120 totemconfig: Free leaks found by coverity = fix ** Affects: corosync (Ubuntu) Importance: High Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: corosync (Ubuntu) Status: New => Confirmed ** Changed in: corosync (Ubuntu) Importance: Undecided => High ** Changed in: corosync (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+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
[Bug 1869622] Re: [focal] corosync v3.0.3 last upstream fixes
** Description changed: - Apart from fixes for: + Together with fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = coverity fix -> ca320bea votequorum: set wfa status only on startup = fix for corner case -> 5f543465 quorumtool: exit on invalid expected votes = fix -> 0c16442f votequorum: Change check of expected_votes = fix -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix -> 89b0d62f stats: Check return code of stats_map_get = fix -> 56ee8503 quorumtool: Assert copied string length = assert (better support) -> 1fb095b0 notifyd: Check cmap_track_add result = assert (better support) -> 8ff7760c cmapctl: Free bin_value on error (fix) -> 35c312f8 votequorum: Assert copied strings length = assert (better support) -> 29109683 totemknet: Assert strcpy length assert (better support) -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call -> a24cbad5 totemconfig: Initialize warnings variable = build fix -> 74eed54a sync: Assert sync_callbacks.name length = assert (better support) -> 380b744e totemknet: Don't mix corosync and knet error codes = fix -> 624b6a47 stats: Assert value_len when value is needed = assert (bet support) -> 09f6d34a logconfig: Remove double free of value = fix -> efe48120 totemconfig: Free leaks found by coverity = fix -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+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
[Bug 1869622] Re: [focal] corosync v3.0.3 last upstream fixes
** Description changed: Together with fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: - -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = coverity fix - -> ca320bea votequorum: set wfa status only on startup = fix for corner case - -> 5f543465 quorumtool: exit on invalid expected votes = fix - -> 0c16442f votequorum: Change check of expected_votes = fix - -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix - -> 89b0d62f stats: Check return code of stats_map_get = fix - -> 56ee8503 quorumtool: Assert copied string length = assert (better support) - -> 1fb095b0 notifyd: Check cmap_track_add result = assert (better support) - -> 8ff7760c cmapctl: Free bin_value on error (fix) - -> 35c312f8 votequorum: Assert copied strings length = assert (better support) - -> 29109683 totemknet: Assert strcpy length assert (better support) - -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call - -> a24cbad5 totemconfig: Initialize warnings variable = build fix - -> 74eed54a sync: Assert sync_callbacks.name length = assert (better support) - -> 380b744e totemknet: Don't mix corosync and knet error codes = fix - -> 624b6a47 stats: Assert value_len when value is needed = assert (bet support) - -> 09f6d34a logconfig: Remove double free of value = fix - -> efe48120 totemconfig: Free leaks found by coverity = fix + -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = fix + -> ca320bea votequorum: set wfa status only on startup = fix + -> 5f543465 quorumtool: exit on invalid expected votes = fix + -> 0c16442f votequorum: Change check of expected_votes = fix + -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix + -> 89b0d62f stats: Check return code of stats_map_get = fix + -> 56ee8503 quorumtool: Assert copied string length= assert + -> 1fb095b0 notifyd: Check cmap_track_add result = assert + -> 8ff7760c cmapctl: Free bin_value on error = fix + -> 35c312f8 votequorum: Assert copied strings length = assert + -> 29109683 totemknet: Assert strcpy length assert = assert + -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call = assert + -> a24cbad5 totemconfig: Initialize warnings variable = build fix + -> 74eed54a sync: Assert sync_callbacks.name length= assert + -> 380b744e totemknet: Don't mix corosync and knet error codes = fix + -> 624b6a47 stats: Assert value_len when value is needed = assert + -> 09f6d34a logconfig: Remove double free of value = fix + -> efe48120 totemconfig: Free leaks found by coverity = fix -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+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
[Bug 1869622] Re: [focal] corosync v3.0.3 last upstream fixes
For the 2 fixes: LP: #1437359 LP: #1677684 I have submitted to upstream the following merge request: https://salsa.debian.org/ha-team/corosync/-/merge_requests/2 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+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
[Bug 1866385] Re: [focal] kronosnet need fixes from just released upstream version
** No longer affects: kronosnet (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1866385 Title: [focal] kronosnet need fixes from just released upstream version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/1866385/+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
[Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found
BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622 PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging ** Changed in: corosync (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1677684 Title: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb- blackbox: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+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
[Bug 1869622] Re: [focal] corosync v3.0.3 last upstream fixes
** Changed in: corosync (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+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
[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622 PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+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
[Bug 1866385] Re: [focal] kronosnet need fixes from just released upstream version
PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging MERGE: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/kronosnet/+git/kronosnet/+merge/381356 ** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/kronosnet/+git/kronosnet/+merge/381356 ** Changed in: kronosnet (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1866385 Title: [focal] kronosnet need fixes from just released upstream version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/1866385/+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
[Bug 580277] Re: pacemaker fails to install/upgrade if the user hacluster already exists and is not a system user.
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. 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'. ** Changed in: pacemaker (Ubuntu) Status: Triaged => Incomplete ** Also affects: pacemaker (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Precise) Status: New => Incomplete ** Changed in: pacemaker (Ubuntu) Status: Incomplete => Fix Released -- 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/580277 Title: pacemaker fails to install/upgrade if the user hacluster already exists and is not a system user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/580277/+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
[Bug 955164] Re: PostgreSQL resource agent has wrong default paths
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. 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'. Observation: The correct affected package for this bug is resource-agents: (k)rafaeldtinoco@clufocal01:~$ dpkg -L resource-agents | grep -i pgsql /usr/lib/ocf/resource.d/heartbeat/pgsql and I'm opening a generic bug to check ALL resource agents paths existence. ** Also affects: resource-agents (Ubuntu) Importance: Undecided Status: New ** No longer affects: pacemaker (Ubuntu) ** Also affects: resource-agents (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: resource-agents (Ubuntu Precise) Status: New => Incomplete ** Changed in: resource-agents (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/955164 Title: PostgreSQL resource agent has wrong default paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/955164/+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
[Bug 1869643] [NEW] check PATH for all binaries called by all agents
Public bug reported: Taking LP: #955164 by example... all resource agents should have resolvable binary PATHs by default. This bug is opened so all resources can be checked and fixed appropriately. Examples: $ crm_resource --list-standards ocf lsb - /etc/init.d/* service - (sysv + systemd) services systemd - systemd services stonith - agents from "fence-agents" $ crm_resource --list-ocf-providers heartbeat pacemaker redhat ocf:heartbeat:* ocf:pacemaker:* ocf:redhat:* Example: crm_resource --show-metadata=ocf:heartbeat:pgsql | more And also to make sure that all dependencies are satisfied by either: - resource-agents or - fence-agents ** Affects: fence-agents (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Affects: resource-agents (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: resource-agents (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: resource-agents (Ubuntu) Importance: Undecided => Medium ** Changed in: resource-agents (Ubuntu) Status: New => Confirmed ** Also affects: fence-agents (Ubuntu) Importance: Undecided Status: New ** Changed in: fence-agents (Ubuntu) Status: New => Confirmed ** Changed in: fence-agents (Ubuntu) Importance: Undecided => Medium ** Changed in: fence-agents (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to resource-agents in Ubuntu. https://bugs.launchpad.net/bugs/1869643 Title: check PATH for all binaries called by all agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1869643/+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
[Bug 1049037] Re: Pacemaker 1.1.6 VirtualDomain OCF wrong timeout handle on shutdown
Fix was already included in current pacemaker version by patch: commit fcfe6fe522138343e4138248829926700fac213e Author: Yan Gao Date: Mon Oct 17 11:19:01 2011 +0800 Medium: crmd: Send out all of the meta parameters to lrmd for stop actions So I'm flagging this as "Fix Released" as it does not affect current supported versions of pacemaker. ** Changed in: pacemaker (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1049037 Title: Pacemaker 1.1.6 VirtualDomain OCF wrong timeout handle on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1049037/+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
[Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts
I'm marking Precise and Trusty as affected. The suggested fix is currently implemented by Xenial already: mcp/pacemaker.in: ... # Required-Start: $network corosync # Should-Start: $syslog # Required-Stop:$network corosync ... ** Also affects: pacemaker (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Xenial) Status: New => Fix Released ** Changed in: pacemaker (Ubuntu Trusty) Status: New => Confirmed ** Changed in: pacemaker (Ubuntu Precise) Status: New => Confirmed ** Changed in: pacemaker (Ubuntu) Status: Triaged => Fix Released ** Changed in: pacemaker (Ubuntu) Importance: High => Undecided ** Changed in: pacemaker (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: pacemaker (Ubuntu Precise) Status: Confirmed => Triaged -- 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/1052449 Title: corosync hangs due to missing pacemaker shutdown scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+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
[Bug 1227580] Re: Monitoring in Master state doesn't always work
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. 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'. ** Changed in: pacemaker (Ubuntu Precise) Status: New => Incomplete ** Changed in: pacemaker (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1227580 Title: Monitoring in Master state doesn't always work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1227580/+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
[Bug 1227580] Re: Monitoring in Master state doesn't always work
The mentioned patch is the following one: commit fc03be02bf3a045babfe8233cbc99227da71d024 Author: David Vossel Date: Fri Jun 29 11:24:52 2012 -0500 High: pengine: cl#5072 - Fixes monitor op stopping after rsc promotion. and was supposed to be applied to Precise. ** Also affects: pacemaker (Ubuntu Precise) Importance: Undecided Status: New -- 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/1227580 Title: Monitoring in Master state doesn't always work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1227580/+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
[Bug 1322899] Re: pacemaker init script links aren't created on upgrade
*** This bug is a duplicate of bug 1052449 *** https://bugs.launchpad.net/bugs/1052449 ** This bug has been marked a duplicate of bug 1052449 corosync hangs due to missing pacemaker shutdown scripts -- 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/1322899 Title: pacemaker init script links aren't created on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1322899/+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
[Bug 1412831] Re: crm_mon crashed with SIGABRT in g_return_if_fail_warning()
** 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) Importance: Medium => Undecided ** Changed in: pacemaker (Ubuntu Trusty) Importance: Undecided => Medium -- 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/1412831 Title: crm_mon crashed with SIGABRT in g_return_if_fail_warning() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1412831/+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
[Bug 1425431] Re: Pacemaker [SIGSEGV - Segmentation violation] using with Heartbeat 3.x
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
