Bug 1508030
| Summary: | Bump default value of fs.inotify.max_user_instances | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Sai Sindhur Malleni <smalleni> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Sai Sindhur Malleni <smalleni> |
| Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | jack.ottofaro, jlibosva, mburns, mlopes, nsantos, racedoro, rhel-osp-director-maint, sauchter |
| Target Milestone: | z7 | Keywords: | Triaged, ZStream |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | scale_lab | ||
| Fixed In Version: | openstack-tripleo-heat-templates-5.3.3-2.el7ost | Doc Type: | Enhancement |
| Doc Text: |
This update increases the default value of `fs.inotify.max_user_instances` to 1024. This update also allows you to manage the value through a heat template, using `InotifyIntancesMax`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-27 16:50:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sai Sindhur Malleni
2017-10-31 17:36:58 UTC
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 |