Comment 14 for bug 1906280
Revision history for this message
| Dmitrii Shcherbakov (dmitriis) wrote Re: Charm stuck waiting for ovsdb 'no key "ovn-remote" in Open_vSwitch record' | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Frode,
OVS has the following checks:
1) a compile-time check for HAVE_MLOCKALL;
2) An attempt to make all future memory allocations locked via `mlockall(
https:/
As such, it gracefully enables locking *of all future memory allocations* (MCL_FUTURE) but the allocations themselves are not handled gracefully: mmap(2), sbrk(2), malloc(3) may fail when RLIMIT_MEMLOCK gets hit. In other works, memory locking is enabled once and then none of the memory allocations have to explicitly request locking which makes it hard to fail gracefully.
As a tactical fix, we can modify the LXD profiles shipped with our charms to set RLIMIT_MEMLOCK to "unlimited".
The rationale is described in the commit message:
https:/
Reviews:
https:/
https:/