> Doesn't seem to be fixed in Focal
> Continuing regardless, as the handle is not privileged. Expect poor
performance!
that is fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918735
Title:
fa
Doesn't seem to be fixed in Focal (deploying Masakari Charm on Openstack
with Juju 2.9.5) :
Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync notice [MAIN ] Corosync
Cluster Engine 3.0.3 starting up
Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync info[MAIN ] Corosync
built-in feat
** Changed in: corosync (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918735
Title:
fails to start in unprivileged container
To manage notifications abo
This bug was fixed in the package corosync - 3.0.3-2ubuntu2.1
---
corosync (3.0.3-2ubuntu2.1) focal; urgency=medium
* d/p/lp1911904-Don-t-lock-all-current-and-future-memory-if-can-t-in.patch:
- Don't mlockall() if setrlimit() fails (LP: #1911904)
* d/p/lp1918735-try-unprivileg
This bug was fixed in the package corosync - 3.0.3-2ubuntu3.1
---
corosync (3.0.3-2ubuntu3.1) groovy; urgency=medium
* d/p/lp1911904-Don-t-lock-all-current-and-future-memory-if-can-t-in.patch:
- Don't mlockall() if setrlimit() fails (LP: #1911904)
* d/p/lp1918735-try-unprivile
root@lp1918735-f:~# dpkg -l | grep corosync
ii corosync 3.0.3-2ubuntu2amd64
cluster engine daemon and utilities
ii libcorosync-common4:amd643.0.3-2ubuntu2amd64
cluster engine common library
root@lp1918735-f:~#
root@lp1918735-g:~# dpkg -l|grep corosync
ii corosync 3.0.3-2ubuntu3amd64
cluster engine daemon and utilities
ii libcorosync-common4:amd64 3.0.3-2ubuntu3amd64
cluster engine common library
root@lp1918735-g:~# syste
Hello Dan, or anyone else affected,
Accepted corosync into groovy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/corosync/3.0.3-2ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
This bug was fixed in the package corosync - 3.1.0-2ubuntu2
---
corosync (3.1.0-2ubuntu2) hirsute; urgency=medium
* d/p/lp1911904-Don-t-lock-all-current-and-future-memory-if-can-t-in.patch:
- Don't mlockall() if setrlimit() fails (LP: #1911904)
* d/p/lp1918735-try-unprivileged
** Changed in: corosync (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918735
Title:
fails to start in unprivileged container
To manage notifications about th
** Bug watch added: Debian Bug tracker #985070
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985070
** Also affects: corosync (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985070
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
** Description changed:
[impact]
fails to start in container
[test case]
install corosync in container and check status
root@corosync-f:~# systemctl status corosync
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; ena
** Description changed:
[impact]
fails to start in container
[test case]
install corosync in container and check status
root@corosync-f:~# systemctl status corosync
● corosync.service - Corosync Cluster Engine
- Loaded: loaded (/lib/systemd/system/corosync.service; ena
> Also FYI this seems to be a bit of a re-surface of bug 1828228
yes, and that was unfortunately 'fixed' by just ignoring the error :(
> are you intending to work-on/fix this
yep, already fixed bug 1911904 upstream and will include this with sru
for that
** Also affects: corosync (Ubuntu Hirsut
I can confirm the issue comparing LXD to VM guest.
But given that the errors are about corosync being unable to set some device
options - and not having an obvious "container mode" switch I wonder if that
will end up needing upstream work.
Also FYI this seems to be a bit of a re-surface of bug 1
15 matches
Mail list logo
