Comment 18 for bug 1906280

Thank you so much Billy, I really appreciate it!

I implemented your suggestion by updating the ovs-vswitchd.service file
with the *--no-mlockall *flag for the start/stop/restart of the service.
After a systemctl daemon-reload and starting the ovs-vswitchd service
again, I was able to get things working as expected.

I can confirm that the containers that were having the problem in the 9
node cloud did indeed have *systemd/bionic-updates,now 237-3ubuntu10.43
amd64 [installed,automatic] *without the *--no-mlockall* flag.
However, the strange thing is that one of their larger clouds (39 node
cloud) that was recently rebuilt (on December 9th or 10th) also has
*systemd/bionic-updates,now
237-3ubuntu10.43 amd64 [installed,automatic] *without the *--no-mlockall*
flag but it worked from the beginning without it so I am not sure why it
worked in one cloud and not the other (the hardware, specs, and charm
config are the same in both clouds). The other 2 large clouds (39 nodes)
have *systemd/now 237-3ubuntu10.39 amd64 [installed,upgradable to:
237-3ubuntu10.43]* so it makes sense why they never hit this as they were
built a 6-12 months ago.

On Monday, I will try restarting the ovs-vswitchd service and also the
containers to see if that reveals anything on the 39 node cloud that worked
from the start.

Thanks again!