** 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; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-03-11 21:28:52 UTC; 17s ago Docs: man:corosync man:corosync.conf man:corosync_overview Main PID: 14552 (code=exited, status=15) Mar 11 21:28:51 corosync-f corosync[14552]: [TOTEM ] Initializing transport (Kronosnet). Mar 11 21:28:52 corosync-f corosync[14552]: [TOTEM ] knet_handle_new failed: File name too long (36) Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Failed to set socket buffer via force option 33: Operation not permitted Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Unable to set local socketpair receive buffer: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] handle: Unable to initialize internal hostsockpair: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Can't initialize TOTEM layer Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Corosync Cluster Engine exiting with status 15 at main.c:1531. Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Main process exited, code=exited, status=15/n/a Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Failed with result 'exit-code'. Mar 11 21:28:52 corosync-f systemd[1]: Failed to start Corosync Cluster Engine. [regression potential] any regression would likely result in failure to start, or reduced performance of corosync [scope] this is needed in f/g/h corosync starts in a bionic container + + opened upstream PR + https://github.com/corosync/corosync/pull/623
** 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; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-03-11 21:28:52 UTC; 17s ago Docs: man:corosync man:corosync.conf man:corosync_overview Main PID: 14552 (code=exited, status=15) Mar 11 21:28:51 corosync-f corosync[14552]: [TOTEM ] Initializing transport (Kronosnet). Mar 11 21:28:52 corosync-f corosync[14552]: [TOTEM ] knet_handle_new failed: File name too long (36) Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Failed to set socket buffer via force option 33: Operation not permitted Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Unable to set local socketpair receive buffer: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] handle: Unable to initialize internal hostsockpair: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Can't initialize TOTEM layer Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Corosync Cluster Engine exiting with status 15 at main.c:1531. Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Main process exited, code=exited, status=15/n/a Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Failed with result 'exit-code'. Mar 11 21:28:52 corosync-f systemd[1]: Failed to start Corosync Cluster Engine. [regression potential] any regression would likely result in failure to start, or reduced performance of corosync [scope] this is needed in f/g/h corosync starts in a bionic container opened upstream PR https://github.com/corosync/corosync/pull/623 + + this is also related to bug 1911904 and bug 1828228 -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1918735/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
