nova_libvirt container "cannot fork child process: Resource temporarily unavailable"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Cédric Jeanneret |
Bug Description
First reported on Red Hat bugzilla: https:/
Description of problem:
OSP 16.1 latest
Running into the following issue with launching instances:
2020-08-19 21:14:42.722+0000: 34000: error : virFork:274 : cannot fork child process: Resource temporarily unavailable
2020-08-19 21:14:42.724+0000: 34000: error : virFork:274 : cannot fork child process: Resource temporarily unavailable
This is with 184 instances:
# sudo podman exec -ti nova_libvirt virsh list --all |wc -l
184
Seems to be hitting PID limit with the nova_libvirt container. Perhaps:
# sudo podman inspect nova_libvirt |grep PidsLimit
How is this config managed?
Version-Release number of selected component (if applicable):
16.1 current
How reproducible:
Unknown
Steps to Reproduce:
1. Launch a significant # of instances.
2.
3.
Additional info:
I'll provide additional libvirtd and nova logs to show the issue.
Fix proposed to branch: master /review. opendev. org/747830
Review: https:/