I disagree with the proposed fix in
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/comments/46
Due to the reason behind this patch -
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/comments/11
On the other-hand not many people have clustered vgs setup, and if they
do we can require dmeventd running.
Thus i'll propose a patch for precise to read monitoring value from
/etc/lvm/lvm.conf if vg_is_clustered are detected.
I'll first test these assumptions with juju using precise machines to
make sure it solves this bug and doesn't change lvm behaviour for non-
clustered case.
Regards,
Dmitrijs.
** Changed in: lvm2 (Ubuntu Precise)
Assignee: Louis Bouchard (louis-bouchard) => Dmitrijs Ledkovs (xnox)
** Changed in: lvm2 (Ubuntu Precise)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/833368
Title:
clustered lvm commands fail with "activation/monitoring=0 is
incompatible with clustered Volume Group" error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
