Avahi is not covered by field sla, so unsubscribing field-high
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1792978
Title:
initscript avahi-daemon, action "start" failed
** Changed in: systemd
Status: New => Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647485
Title:
NVMe symlinks broken by devices with spaces in model or
The check for corosync running doesn't work properly and prevents the
clvm service from properly starting.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I was not able to reproduce the problem using trusty + 3.19 kernel and
libvirt alone. I was able to scale appropriately to 63 domains using
VFs.
I guess next step is to test the OpenStack instructions identified, but
then it may be a problem lying elsewhere.
--
You received this bug
Ah thanks Brian for the corrections. Here's an updated patch with the
changelog indicating the change to the openais / dlm change. Hopefully
its clear. In trusty the cman and openais packages were removed. Instead
to setup clustered LVM one can use the distributed lock manager and
corosync to
** Patch added: "trusty patch"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4557921/+files/lp1089013_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Patch removed: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4552897/+files/xenial_lp1089013.debdiff
** Patch removed: "wily debdiff"
** Description changed:
while clvm in precise can support corosync, init script won't start
because issues a cman status command
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: clvm 2.02.66-4ubuntu7.1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux
** Patch added: "debdiff for trusty"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4552899/+files/trusty_lp1089013.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Description changed:
while clvm in precise can support corosync, init script won't start
because issues a cman status command
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: clvm 2.02.66-4ubuntu7.1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux
** Patch added: "wily debdiff"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4552898/+files/wily_lp1089013.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Billy Olsen (billy-olsen)
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
It appears that the cman tooling isn't available in Trusty even, so this
means the clvm is really broken. On >= Trusty this can be fixed by
checking the corosync status (corosync-quorumtool -s) to ensure that the
clustering (corosync) services are up.
--
You received this bug notification
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1089013
Title:
clvm startup script requires cman
Status in lvm2 package in Ubuntu:
Confirmed
Bug
Serge,
I did double check that the pacemaker processes were running under
hacluster/haclient uid/gid. I will double check for my own sanity (I may
have seen one running as root). However, according to the pacemaker docs
that I referenced above, root and hacluster users should always have
full
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1439649/+attachment/4457039/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Looking at logs from bug 1491228, it would appear that the first time
that pacemaker goes to talk to the corosync daemon it gets denied. Per
upstream docs [0], if the enable-acl property isn't explicitly enabled,
then any user in the haclient group should have access. Since the
hacluster charm
17 matches
Mail list logo
