kolla-ansible

dnsmasq out of inotify handles

Bug #1735176 reported by Ian Kumlien
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Invalid
Wishlist
Unassigned

Bug Description

We just struck this earlier today in our pike deployment:
https://bugs.launchpad.net/charm-neutron-gateway/+bug/1593041

And setting:
fs.inotify.max_user_instances=1024

In sysctl.conf fixed the issue for us (actually 256 was enough but...)

Working out how this should be done via the ansible scripts required more ansible knowledge than I currently posses =)

Eduardo Gonzalez (egonzalez90)
Changed in kolla-ansible:
importance: Undecided → Wishlist
Revision history for this message
Michal Nasiadka (mnasiadka) wrote :

Is this still valid for deployments with Yoga or later?

Changed in kolla-ansible:
status: New → Invalid
Revision history for this message
Ian Kumlien (pomac) wrote :

If you have more than 128 dnsmasq instances - since only 128 inotify handles are available by default

And afair this isn't change by ansible today.

Revision history for this message
Ian Kumlien (pomac) wrote :

isn't changed by kolla-ansible today*

(been running greps, can't find anything)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.