Seems we're running into the memlock limit. A test of disabling the MEMLOCKALL option for ovs allows the ovs-vswitchd service to no longer crash.
As Dmitrii pointed out to me, this might be related to the issue and commentary in https://patchwork<email address hidden>/.
However, the LimitSTACK=2M change in the systemd service file patch proposed was not low enough for this environment. I had to set it to 1M to actually get the service to start.
Another option might be to increase the memlock available to the containers, but I'm not sure if that's something that can easily be set in the juju lxd profiles.
Seems we're running into the memlock limit. A test of disabling the MEMLOCKALL option for ovs allows the ovs-vswitchd service to no longer crash.
As Dmitrii pointed out to me, this might be related to the issue and commentary in https:/ /patchwork<email address hidden>/.
However, the LimitSTACK=2M change in the systemd service file patch proposed was not low enough for this environment. I had to set it to 1M to actually get the service to start.
Another option might be to increase the memlock available to the containers, but I'm not sure if that's something that can easily be set in the juju lxd profiles.