Feature #5954
Updated by Dan Mick almost 11 years ago
Loïc Löic discovered that teuthology (specifically the task runners) depend on changes to /etc/security to allow adjust-ulimits to run and set unlimited core and 16K open files. These are currently hacked by our ceph-qa-chef code: <pre> cookbooks/ceph-qa/recipes/default.rb:file '/etc/security/limits.d/ubuntu.conf' </pre> sets up <pre> ubuntu hard nofile 16384 </pre> and fedora, centos, redhat edit /etc/security/limits.conf to allow soft coresize limits: <pre> sed -i 's/^#\*.*soft.*core.*0/\* soft core unlimited/g' /etc/security/limits.conf </pre> as well as <pre> sed -i 's/ requiretty/ !requiretty/g' /etc/sudoers sed -i 's/ !visiblepw/ visiblepw/g' /etc/sudoers </pre> and also set up /etc/security/limits.d/remote.conf to contain <pre> * hard core unlimited </pre> (and actually those last two seem redundant, or at least weird that they exist in two totally different places). It seems like it would be cleaner if we just require the test user to be passwordless-sudo (which I think we already do) and add appropriate sudo calls in the right places. Sage thinks this might involve separating the ulimit calls in adjust-ulimits to "those that need unl core" and "those that need nofile". Should probably also straighten out who needs the hard vs soft core limit.