corosync fails to start in unprivileged containers - autopkgtest failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
Invalid
|
Undecided
|
Unassigned | ||
corosync (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
pacemaker (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
pcs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Currently pacemaker v2 fails to start in armhf containers (and by extension corosync too).
I found that it is reproducible locally, and that I had to bump a few limits to get it going.
Specifically I did:
1) bump memlock limits
2) bump rmem_max limits
= 1) Bump memlock limits =
I have no idea, which one of these finally worked, and/or is sufficient. A bit of a whack-a-mole.
cat >>/etc/
* soft memlock unlimited
* hard memlock unlimited
EOF
lxc config set nice-mako limits.
mkdir -p /etc/systemd/
cat >/etc/systemd/
[Service]
LimitMEMLOCK=
EOF
systemctl daemon-reload
systemctl restart snap.lxd.
= 2) Bump rmem_max values =
Observed:
# strace -s99999 -f /usr/sbin/corosync 2>&1 | grep sockop
[pid 447] setsockopt(12, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
[pid 447] getsockopt(12, SOL_SOCKET, SO_RCVBUF, [425984], [4]) = 0
[pid 447] setsockopt(12, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted)
Bumped mem_max using:
sudo sysctl -w net.core.
sudo sysctl -w net.core.
(Not sure if the desired sized depends on the machine/container I am running on)
Can we check the values for above things on our armhf containers and/or bump them? or like can we mark pacemaker v2.0 autopkgtest as ignored on armhf?
Related branches
- Bryce Harrington (community): Approve
- Canonical Server Core Reviewers: Pending requested
-
Diff: 689 lines (+377/-32)12 files modifieddebian/changelog (+355/-0)
debian/control (+5/-3)
debian/patches/Enable-redirecting-etc-init.d-script-calls-to-system.patch (+0/-4)
debian/patches/Enable-the-init-scripts-on-multi-user-runlevels.patch (+0/-4)
debian/patches/Fix-typo-evalute-evaluate.patch (+1/-3)
debian/patches/Make-the-asciidoc-documentation-reproducible.patch (+1/-3)
debian/patches/Shipping-the-CTS-is-not-useful.patch (+3/-9)
debian/patches/alerts-make-the-scripts-executable.patch (+0/-2)
debian/patches/libpacemaker-calls-into-libstonithd-directly.patch (+1/-3)
debian/rules (+4/-0)
debian/tests/control (+1/-1)
debian/tests/pacemaker (+6/-0)
- Rafael David Tinoco (community): Disapprove
- Andreas Hasenack (community): Needs Information
-
Diff: 226 lines (+120/-5)9 files modifieddebian/changelog (+13/-0)
debian/control (+4/-2)
debian/patches/Fix-python-tornado-5.patch (+75/-0)
debian/patches/series (+1/-0)
debian/tests/control (+3/-3)
debian/tests/setup (+6/-0)
debian/tests/snmp (+6/-0)
debian/tests/status (+6/-0)
debian/tests/testsuite-python (+6/-0)
tags: | added: ubuntu-ha |
Changed in corosync (Ubuntu): | |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
Changed in pacemaker (Ubuntu): | |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
Changed in corosync (Ubuntu): | |
assignee: | Rafael David Tinoco (rafaeldtinoco) → nobody |
Changed in pacemaker (Ubuntu): | |
assignee: | Rafael David Tinoco (rafaeldtinoco) → nobody |
tags: | removed: ubuntu-ha |
Changed in corosync (Ubuntu): | |
status: | In Progress → Invalid |
Changed in corosync-qdevice (Ubuntu): | |
status: | In Progress → Invalid |
Changed in corosync (Ubuntu): | |
status: | Triaged → In Progress |
summary: |
- corosync fails to start in container (armhf) bump some limits + corosync fails to start in unprivileged containers - autopkgtest failure |
Changed in pacemaker (Ubuntu): | |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
Changed in corosync (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in pcs (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
tags: | added: update-excuse |
Changed in pcs (Ubuntu): | |
assignee: | Rafael David Tinoco (rafaeldtinoco) → nobody |
Changed in pacemaker (Ubuntu): | |
assignee: | Rafael David Tinoco (rafaeldtinoco) → nobody |
Changed in corosync (Ubuntu): | |
assignee: | Rafael David Tinoco (rafaeldtinoco) → nobody |
Am I right in thinking that the limits being too low are causing false positives in autopkgtests?
If so, we could check the limits in the test themselves and skip (exit 77 and declare "skippable") if on armhf and the limits aren't high enough. That's a reasonable action for the packages, I think.