In openshift-ansible-3.10.20-1 and later
Hi, Avesh I found those changes are only applied to nodes, masters are not applied. Is it expected? on master # sysctl -a | grep fs.inotify.max_user_ fs.inotify.max_user_instances = 128 fs.inotify.max_user_watches = 65536 on node: # sysctl -a | grep fs.inotify.max_user_ fs.inotify.max_user_instances = 8192 fs.inotify.max_user_watches = 65536 openshift-ansible-3.10.21-1.git.0.6446011.el7.noarch.rpm
Based on comment 3, change back to ASSIGNED status to let dev have a quick glance because it is very close to 3.10 release date.
(In reply to Weihua Meng from comment #3) > Hi, Avesh > > I found those changes are only applied to nodes, masters are not applied. > Is it expected? > > on master > # sysctl -a | grep fs.inotify.max_user_ > fs.inotify.max_user_instances = 128 > fs.inotify.max_user_watches = 65536 > > on node: > # sysctl -a | grep fs.inotify.max_user_ > fs.inotify.max_user_instances = 8192 > fs.inotify.max_user_watches = 65536 > > > openshift-ansible-3.10.21-1.git.0.6446011.el7.noarch.rpm This bug seems to be related to tailing log files on builds and builds should not run on masters so I think this is fine for now. I'll follow up with the performance and node teams to see if we should change this in the future though.
(In reply to Weihua Meng from comment #3) > Hi, Avesh > > I found those changes are only applied to nodes, masters are not applied. > Is it expected? Yes. > > on master > # sysctl -a | grep fs.inotify.max_user_ > fs.inotify.max_user_instances = 128 > fs.inotify.max_user_watches = 65536 > > on node: > # sysctl -a | grep fs.inotify.max_user_ > fs.inotify.max_user_instances = 8192 > fs.inotify.max_user_watches = 65536 > > > openshift-ansible-3.10.21-1.git.0.6446011.el7.noarch.rpm
Verified per comment 5 & comment 6
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:2263