** Changed in: pacemaker (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1312156
Title:
[Precise] Potential for data corruption
To
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1312156
Title:
[Precise] Potential
Here is the patch fixing corosync misbehavior described above.
Description: Remove buggy logic to prevent secondary dc fencing
On logic before commit 82aa2d8d17 the node responsible for fencing
(executioner) the dc was responsible also for updating cib. If this
update failed (due to a
** Description changed:
+ [Impact]
+
+ * Pacemaker designated controller can make wrong decisions based on
+ uncleared node status on a rare specific situation. This situation can
+ make the same resource starts on two nodes at the same time, resulting
+ in data corruption.
+
+ [Test Case]
+
- version 5.0.7 - dd66c61a - file
descriptor leak when reloading automount daemon. Tested with the same
test case fix the error and not changing any other behavior.
[Other Info ]
-
** Affects: autofs5 (Ubuntu)
Importance: Undecided
Assignee: Rafael David Tinoco (inaddy)
Status
Attaching patch for affected versions.
This one is for Saucy.
** Patch added: saucy_autofs5_5.0.7-3ubuntu2.diff
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1316125/+attachment/4105694/+files/saucy_autofs5_5.0.7-3ubuntu2.diff
--
You received this bug notification because you are a
Attaching patch for affected versions.
This one if for Precise.
** Patch added: precise_autofs5_5.0.6-0ubuntu5.2.diff
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1316125/+attachment/4105693/+files/precise_autofs5_5.0.6-0ubuntu5.2.diff
--
You received this bug notification
Public bug reported:
If node detects itself not able to receive message it asserts the number of
failed members considering itself and dies.
I'll write more information (and the fix) in a few minutes.
** Affects: corosync (Ubuntu)
Importance: Undecided
Assignee: Rafael David Tinoco
** Description changed:
- If node detects itself not able to receive message it asserts the number of
failed members considering itself and dies.
- I'll write more information (and the fix) in a few minutes.
+ If node detects itself not able to receive message it asserts the number
+ of failed
Attaching patch.
** Patch added: corosync_1.4.2-2ubuntu0.2.diff
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1318441/+attachment/4110673/+files/corosync_1.4.2-2ubuntu0.2.diff
** Description changed:
[Impact]
- * On certain conditions corosync daemon may quit if it detects
Tests before the patch:
#
# NODE 1
#
--- MARKER --- ./failed-to-receive-crash.sh at 2014-05-09-17:33:04 --- MARKER
---
May 09 17:33:04 corosync [MAIN]: ] Corosync Cluster Engine ('1.4.2'): started
and ready to provide service.
May 09 17:33:04 corosync [MAIN]: ] Corosync built-in
)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: autofs5 (Ubuntu Trusty)
Status: New = In Progress
** Changed in: autofs (Ubuntu)
Status: New = In Progress
** Changed in: autofs (Ubuntu Precise)
Status: New = In Progress
** Changed in: autofs
/trusty_autofs_5.0.7-3ubuntu4.diff
** Changed in: autofs5 (Ubuntu Trusty)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: autofs (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: autofs (Ubuntu Saucy)
Assignee: (unassigned) = Rafael David Tinoco
** Project changed: nova = nova (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1219658
Title:
Wrong image size using rbd backend for libvirt
To manage notifications about
** Description changed:
[Impact]
- * [2cebfd2] libvirt: convert cpu features attribute from list to
-a set (LP: #1267191)
-
- cpu features list which is being sent to libvirt,
- when creating a domain or calling compareCPU, must contain only
-
Brian,
I've made several tests on this and everything works like expected.
Changing tag.
Thanks
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in
Brian,
I've made several tests on this and everything works like expected.
Changing tag.
Thanks
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in
** Changed in: pacemaker (Ubuntu Precise)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1312156
Title:
[Precise
** Changed in: corosync (Ubuntu Precise)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1318441
Title:
Precise corosync
** Description changed:
- Description of problem
- ---
+ [Impact]
+
+ * cpu features list which is being sent to libvirt,
+ when creating a domain or calling compareCPU, must contain only
+ unique entries. Multiple issues arise when we are updating the
+ features
** Description changed:
[Impact]
- * [2cebfd2] libvirt: convert cpu features attribute from list to
- a set (LP: #1267191)
-
- cpu features list which is being sent to libvirt,
- when creating a domain or calling compareCPU, must contain only
- unique entries.
** Description changed:
[Impact]
* cpu features list which is being sent to libvirt,
when creating a domain or calling compareCPU, must contain only
unique entries. Multiple issues arise when we are updating the
features attribute in LibvirtConfigCPU class (for example during
** Description changed:
[Impact]
* The original fix for bug 1219658 introduced a factor of 1024 error
in the resulting rbd image size. Big impact.
[Test Case]
- * To be provided.
+ * To have icehouse openstack using rbd image backend for libvirt:
+
+ Images seem to be 1024
| b146349 ||| Medium: cibconf:
repair configure load update
So I'm assuming this will fix the issue... Opening the public bug for
the fix.
** Affects: crmsh (Ubuntu)
Importance: Undecided
Assignee: Rafael David Tinoco (inaddy)
Status: Confirmed
** Tags: crmsh pacemaker trusty
** Description changed:
It was brought to me (~inaddy) the following situation:
* Environment
Ubuntu 14.04 LTS
Pacemaker 1.1.10+git20130802-1ubuntu2
* Issue
I cannot use crm configure load update.
It cause an error as below.
# crm configure load update settings.crm
## After applying the fix I could successfully load my previous cluster
configuration:
root@trustycluster01:~# crm configure load xml replace ./cluster.xml
root@trustycluster01:~# crm resource
crm(live)resource# list
p_fence_cluster01 (stonith:external/vcenter): Stopped
Created one public PPA so the SRU proposal can be tested before asking
for sponsorship:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1353011
# apt-add-repository ppa:inaddy/lp1353011
# apt-get update
# apt-get dist-upgrade
* attention: this will replace current trusty crmsh version:
Assignee: Rafael David Tinoco (inaddy)
Status: Confirmed
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: pacemaker (Ubuntu)
Status: New = Confirmed
** Description changed:
It was brought to me (~inaddy
Created one public PPA so the SRU proposal can be tested before asking
for sponsorship:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1353473
# apt-add-repository ppa:inaddy/lp1353473
# apt-get update
# apt-get dist-upgrade
* attention: this will replace current trusty pacemaker version:
## After applying the fix I could successfully put one node on standby.
Resources migrated correctly.
root@trustycluster02:~# crm_mon
Connection to the CIB terminated
Reconnecting...root@trustycluster02:~# crm_mon -1
Last updated: Wed Aug 6 10:27:35 2014
Last change: Tue Aug 5 15:42:11 2014 via
Changed this to verification-done because since this SRU proposal this
has been running in a big server farm without any issues or regressions.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server
Changed this to verification-done because since this SRU proposal this
has been running in a big server farm without any issues or regressions.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
It was brought to me (~inaddy) the following situation with multipathd:
#
Program terminated with signal 6, Aborted.
#0 0x7fbc6ae09445 in raise () from /lib/x86_64linuxgnu/
libc.so.6
(gdb) bt
#0 0x7fbc6ae09445 in raise () from /lib/x86_64linuxgnu/
libc.so.6
#1
Since I don't have specific steps how to reproduce this error (it can be
intermittent), but the fix is straight forward (using upstream fix), I'm
suggesting this to be SRUed.
A temporary PPA was created for those who wants to test before it gets
accepted into -proposed:
# sudo add-apt-repository
Attaching SRU proposal.
Description: [PATCH] libmultipath: update waiter handling
The current 'waiter' structure accesses fields which belong
to the main 'mpp' structure, which has a totally different
lifetime. With this patch most of these dependencies are
removed and the 'waiter' structure
precise_multipath-tools_0.4.9-3ubuntu5.2.debdiff
** Patch added: precise_multipath-tools_0.4.9-3ubuntu5.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+attachment/4172183/+files/precise_multipath-tools_0.4.9-3ubuntu5.2.debdiff
--
You received this bug
trusty_multipath-tools_0.4.9-3ubuntu8.debdiff
** Patch added: trusty_multipath-tools_0.4.9-3ubuntu8.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+attachment/4172184/+files/trusty_multipath-tools_0.4.9-3ubuntu8.debdiff
--
You received this bug notification
)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: multipath-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
+
+ [Impact]
+
+ * Multipath can cause segmentation fault due to wrong code and can
+possibly cause user to loose access to multipath devices.
+
+ [Test Case]
+
+ * Working on it.
+
+ [Regression Potential]
+
+ * Fix based on upstream code (96f8146) Tag 0.5.0
So probably to last commits touching libmultipath/waiter.c (and fixing
this issue) would be:
1)
commit e1fcc5933ac44683cdee1a02304e1115abec3ff5
Author: Benjamin Marzinski bmarz...@redhat.com
Date: Sat May 19 01:37:03 2012 -0500
multipath: clean up code for stopping the waiter threads
It looks like the fix above introduces regressions (actually other new
bugs):
commit 96f81469ff993b6063bb8829d9b336590510466d
Author: Hannes Reinecke h...@suse.de
Date: Mon May 4 16:46:58 2009 +0200
libmultipath: update waiter handling
The current 'waiter' structure accesses fields
And maybe this also:
Maybe this:
commit 03ec4efe8775f0ca076df3fb85b9defab4ffad30
Author: Benjamin Marzinski bmarz...@redhat.com
Date: Fri Feb 10 12:10:11 2012 -0600
multipath: fix shutdown crashes
A number of processes don't reach a pthread cancellation point
before they use the
And 2)
commit af4fd6d4efc5dbd13daaf4117c4a95fc7a99eafb
Author: Hannes Reinecke h...@suse.de
Date: Tue Jan 8 14:54:08 2013 +0100
Fix race condition in stop_waiter_thread()
The signal handler might run before we had a chance to
set the 'waiter' context to '0', so better do it
** Patch added: trusty_multipath-tools_0.4.9-3ubuntu8.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+attachment/4172258/+files/trusty_multipath-tools_0.4.9-3ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Patch added: utopic_multipath-tools_0.4.9-3ubuntu9.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+attachment/4172259/+files/utopic_multipath-tools_0.4.9-3ubuntu9.debdiff
** Description changed:
-
[Impact]
- * Multipath can cause segmentation fault
** Patch added: precise_multipath-tools_0.4.9-3ubuntu5.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+attachment/4172257/+files/precise_multipath-tools_0.4.9-3ubuntu5.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server
** Description changed:
[Impact]
* Multipath can cause segmentation fault due to wrong code and can
possibly cause user to loose access to multipath devices.
[Test Case]
- * Working on it.
+ * To use multipath and wait for the problem to occur sometime
+ (inevitable).
** Description changed:
+ [Impact]
+
+ *
+
+ [Test Case]
+
+ *
+ [Regression Potential]
+
+ *
+
+ [Other Info]
+
+ * Original bug description:
+
+
+
It was brought to me (~inaddy) the following situation:
* Environment
Ubuntu 14.04 LTS
Pacemaker
The upstream fix commit was introduced in 1.2.6-rc2.
inaddy@trusty.00070402:/bugs/00070402/sources/upstream/crmsh$ git tag
--contains b146349
1.2.6
1.2.6-rc2
1.2.6-rc3
2.0.0
2.1.0
And Utopic is using:
crmsh | 1.2.6+git+e77add-1.2ubuntu1 | utopic | source, all
So fix is already in Utopic.
**
Attaching fix for trusty.
** Patch added: trusty_crmsh_1.2.5+hg1034-1ubuntu4.debdiff
https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1353011/+attachment/4172954/+files/trusty_crmsh_1.2.5%2Bhg1034-1ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Attaching fix for trusty.
** Patch added: trusty_crmsh_1.2.5+hg1034-1ubuntu4.debdiff
https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1353011/+attachment/4172953/+files/trusty_crmsh_1.2.5%2Bhg1034-1ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
[Impact]
- *
+ * Whenever a user uses crm node standby the code can make lrmd still
+try to monitor resource put into stand-by and cause error messages.
[Test Case]
- *
+ * To use crm node standby and check lrmd does not stop monitoring
+not set
** Description changed:
[Impact]
* Whenever a user uses crm node standby the code can make lrmd still
-try to monitor resource put into stand-by and cause error messages.
+ try to monitor resource put into stand-by and cause error messages.
[Test Case]
* To use crm node
Uploading fix for Trusty.
** Description changed:
[Impact]
* Whenever a user uses crm node standby the code can make lrmd still
try to monitor resource put into stand-by and cause error messages.
[Test Case]
* To use crm node standby and check lrmd does not stop
Uploading fix for Trusty (corrected upstream commit #s).
** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu3.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1353473/+attachment/4172984/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu3.debdiff
--
You received
inaddy@trusty.00070403:/bugs/00070403/sources/upstream$ git tag --contains
48f90f6
inaddy@trusty.00070403:/bugs/00070403/sources/upstream$ git tag --contains
c29ab27
inaddy@trusty.00070403:/bugs/00070403/sources/upstream$ git tag --contains
348bb51
Pacemaker-1.1.12
Pacemaker-1.1.12-rc1
Attaching Trusty fix.
** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu3.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1353473/+attachment/4173016/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu3.debdiff
--
You received this bug notification because you are
Attaching Utopic fix.
** Patch added: utopic_pacemaker_1.1.10+git20130802-4ubuntu3.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1353473/+attachment/4173017/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu3.debdiff
--
You received this bug notification because you are
Proposed merge to Utopic:
https://code.launchpad.net/~inaddy/ubuntu/utopic/pacemaker/bug-1353473/+merge/230169
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1353473
Title:
Proposed merge:
https://code.launchpad.net/~inaddy/ubuntu/utopic/multipath-
tools/bug-1354114/+merge/230170
For Utopic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Submitted to debian bug tracking system:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757508
Waiting for merges/fixes.
** Bug watch added: Debian Bug tracker #757508
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757508
--
You received this bug notification because you are a member
** Summary changed:
- Trusty Pacemaker crm node standby stops resource successfully, but lrmd
still monitors it and causes Failed actions
+ Pacemaker crm node standby stops resource successfully, but lrmd still
monitors it and causes Failed actions
--
You received this bug notification
Submitted fix to Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757514
Waiting for fix/merge.
** Bug watch added: Debian Bug tracker #757514
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757514
--
You received this bug notification because you are a member of Ubuntu
Server
** Patch added: utopic_multipath-tools_0.4.9-3ubuntu9.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+attachment/4173053/+files/utopic_multipath-tools_0.4.9-3ubuntu9.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Proposed merge:
https://code.launchpad.net/~inaddy/ubuntu/utopic/multipath-
tools/bug-1354114/
For utopic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1354114
Title:
** Patch removed: utopic_multipath-tools_0.4.9-3ubuntu9.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+attachment/4172259/+files/utopic_multipath-tools_0.4.9-3ubuntu9.debdiff
** Patch removed: precise_multipath-tools_0.4.9-3ubuntu5.2.debdiff
** Patch added: trusty_multipath-tools_0.4.9-3ubuntu8.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+attachment/4173052/+files/trusty_multipath-tools_0.4.9-3ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Also affects: pacemaker (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757514
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
Thank you very much Brian.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1354114
Title:
multipath segmentation Fault (libmultipath: update waiter handling)
To manage
Does this need review for Precise Trusty for the SRUs to happen ?
Thanks in advance.
-Rafael
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1354114
Title:
multipath
Public bug reported:
It was brought to my attention the following situation:
[Issue]
lrmd process crashed when repeating crm node standby and crm node
online
# grep pacemakerd ha-log.k1pm101 | grep core
Aug 27 17:47:06 k1pm101 pacemakerd[49271]: error: child_waitpid:
* Fix: services: Do not allow duplicate recurring op entries - 1/3 (LP:
#1353473)
* High: lrmd: Merge duplicate recurring monitor operations - 2/3 (LP:
#1353473)
* Fix: lrmd: Cancel recurring operations before stop action is executed - 3/3
(LP: #1353473)
-- Rafael David Tinoco rafael.tin
** Changed in: multipath-tools (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: multipath-tools (Ubuntu Precise)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: multipath-tools (Ubuntu Precise)
Status: New = Confirmed
** Changed in: multipath-tools
** Tags removed: verification-needed
** Tags added: verification-node
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to crmsh in Ubuntu.
https://bugs.launchpad.net/bugs/1353011
Title:
Trusty's crm configure load fails to update
)
* Fix: services: Fix the executing of synchronous actions - 2/2 (LP: #1368737)
-- Rafael David Tinoco rafael.tin...@canonical.com Fri, 12 Sep 2014
15:52:14 -0300
pacemaker (1.1.10+git20130802-1ubuntu3) trusty; urgency=medium
* Fix: services: Do not allow duplicate recurring op entries - 1/3 (LP
I confirm this fixes the issue for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1316125
Title:
Autofs
# verification-trusty
inaddy@trusty.1315535:~$ cat /etc/auto.master
/- /etc/auto.direct
inaddy@trusty.1315535:~$ cat /etc/auto.direct
# cat /etc/auto.direct
# /nfs.client localhost:/nfs.server
/nfs.client/dir01 localhost:/nfs.server
/nfs.client/dir02 localhost:/nfs.server
# after changing
# verification-precise
inaddy@precise.1315535:~$ sudo mkdir /nfs.server
inaddy@precise.1315535:~$ sudo mkdir /nfs.client
inaddy@precise.1315535:~$ sudo vi /etc/exports
inaddy@precise.1315535:~$ sudo service nfs-kernel-server restart
inaddy@precise.1315535:~$ sudo vi /etc/auto.master
# verification-saucy
inaddy@saucy.1315535:~$ sudo mkdir /nfs.server/
mkdir: cannot create directory ‘/nfs.server/’: File exists
inaddy@saucy.1315535:~$ sudo mkdir /nfs.client
inaddy@saucy.1315535:~$ sudo vi /etc/exports
inaddy@saucy.1315535:~$ sudo vi /etc/exports
inaddy@saucy.1315535:~$ sudo
Starting verification for Trusty and Precise...
### Precise before using package in -proposed
root@trytrusty:~# multipath -ll
lun2 (1494554009feaa66a15201fac7bf681e6f5437e7d) dm-3 IET,VIRTUAL-DISK
size=5.0G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
### Precise multipath daemon restart
root@tryprecise:~# dpkg -l | grep multipath-tools
ii multipath-tools 0.4.9-3ubuntu5.3 maintain
multipath block device access
root@tryprecise:~# service multipath-tools restart
* Stopping multipath daemon multipathd
# Precise failover test - removed 1 path during writes. failover after
10 seconds (iscsi timeout)
root@tryprecise:~# dd if=/dev/zero of=/dev/mapper/2luns0 bs=1M count=2000
2000+0 records in
2000+0 records out
2097152000 bytes (2.1 GB) copied, 137.125 s, 15.3 MB/s
ct 14 16:46:01 tryprecise
# Trusty failover test - removed 1 path during writes. failover after 10
seconds (iscsi timeout)
root@trytrusty:~# dd if=/dev/zero of=/dev/mapper/2luns0 bs=1M count=2000
2000+0 records in
2000+0 records out
2097152000 bytes (2.1 GB) copied, 139.481 s, 15.0 MB/s
Oct 14 16:50:29 trytrusty
I'm confirming both: Precise and Trusty SRUs are operational and
multipath seems to be fine.
Changing tags to verification-done.
Thank you.
Rafael Tinoco
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
- 1 root root 443K Oct 30 01:21 _usr_lib_pacemaker_stonithd.0.crash
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Attachment added: cib.xml
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249543/+files/cib.xml
Analyzing the stacktrace for stonithd:
(gdb) bt
#0 0x7fed094febb9 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7fed09501fc8 in __GI_abort () at abort.c:89
#2 0x7fed0a15a6c9 in crm_abort (file=0x7fed0a17e4bb logging.c,
Trusty is affected and Precise is NOT.
libglib2.0-0 | 2.24.0-0ubuntu4 | lucid| amd64, armel, i386, ia64,
powerpc, sparc
libglib2.0-0 | 2.24.1-0ubuntu2 | lucid-updates| amd64, armel, i386, ia64,
powerpc, sparc
libglib2.0-0 | 2.32.1-0ubuntu2 | precise | amd64, armel,
Trusty Fix.
** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249612/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu2.2.debdiff
--
You received this bug notification because you are a
Utopic Fix.
** Patch added: utopic_pacemaker_1.1.10+git20130802-4ubuntu4.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249614/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu4.debdiff
--
You received this bug notification because you are a member
Running testcase for some time and couldn't get any core dump...
Services seem stable:
Every 1.0s: crm_mon -1
Fri Oct 31 00:52:57 2014
Last updated: Fri Oct 31 00:52:57 2014
Last change: Fri Oct 31 00:31:22 2014 via crm_attribute on clustertrusty04
Stack: corosync
Current DC: clustertrusty02
Vivid might also need a fix/update to proper handle this.
** Changed in: pacemaker (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
I'm asking for sponsorship for this...
Meanwhile I have created one PPA to be used:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1368737
# add-apt-repository ppa:inaddy/lp1368737
# apt-get update
# apt-get install pacemaker
The right package version, for now, will be:
** Description changed:
+ [IMPACT]
+
+ - Pacemaker seg fault on repeated crm node online/standy because:
+ - Newer glib versions uses hash_table to find GSources
+ - Glib can try to assert source being removed multiple times
+
+ [TEST CASE]
+
+ - Using same configuration as
** Changed in: pacemaker (Ubuntu Trusty)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: pacemaker (Ubuntu)
Status: New = In Progress
** Changed in: pacemaker (Ubuntu Trusty)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
Considering bug:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1382842
I'll have to fix dependencies together with this SRU.
Please hold while I fix this new debdiff (for this case), fixing lib
dependencies for pacemaker to be upgraded.
Thank you
Rafael Tinoco
--
You received
Since there is a new SRU proposal on the following case:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737
I'll provide the dependencies fix together with that new SRU proposal.
I'll inform here when that bug (1368737) and this one (1382842) are
addressed on that SRU proposal.
** Summary changed:
- Pacemaker can seg fault on crm node online/standy
+ Pacemaker can seg fault on crm node online/standby
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
It looks like the format chosen for SRU for this package :
pacemaker (1.1.10+git20130802-1ubuntu2.1) trusty
pacemaker (1.1.10+git20130802-1ubuntu2) trusty
pacemaker (1.1.10+git20130802-1ubuntu1) saucy
makes dh helpers not to calculate shlibs version properly:
$ fakeroot dh_makeshlibs -a -V
$
It looks like the format chosen for SRU for this package :
pacemaker (1.1.10+git20130802-1ubuntu2.1) trusty
pacemaker (1.1.10+git20130802-1ubuntu2) trusty
pacemaker (1.1.10+git20130802-1ubuntu1) saucy
makes dh helpers not to calculate shlibs version properly:
$ fakeroot dh_makeshlibs -a -V
$
1 - 100 of 689 matches
Mail list logo
