Red Hat Bugzilla – Bug 1508030
Bump default value of fs.inotify.max_user_instances
Last modified: 2018-03-07 06:39:56 EST
Description of problem: each dnsmasq process opens an inotify match, so the default value of fs.inotify.max_user_instances which is 128 is easily hit when creating subnets at scale. Version-Release number of selected component (if applicable): 10 How reproducible: 100% Steps to Reproduce: 1. Create large number of subnets (>128) 2. 3. Actual results: Subnet creation fails after a while Expected results: Subnets should be created Additional info: Upstream Gerrit: https://review.openstack.org/#/c/509521/
Merged to upstream Newton, moving to POST.
Verified on build 2018-02-02.1 [stack@undercloud-0 ~]$ rpm -q openstack-tripleo-heat-templates openstack-tripleo-heat-templates-5.3.8-1.el7ost.noarch [stack@undercloud-0 ~]$ cat $(locate kernel.yaml) | sed -n '25,28p' InotifyIntancesMax: default: 1024 description: Configures sysctl fs.inotify.max_user_instances key type: number [stack@undercloud-0 ~]$ cat $(locate kernel.yaml) | sed -n '65,67p' # set inotify value for neutron/dnsmasq scale fs.inotify.max_user_instances: value: {get_param: InotifyIntancesMax}
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0364