Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to set limits via systemd class #49

Closed
redcricket opened this issue Nov 20, 2017 · 2 comments
Closed

Not able to set limits via systemd class #49

redcricket opened this issue Nov 20, 2017 · 2 comments

Comments

@redcricket
Copy link

I want to setup some systemd limits for a service so I have included ...

    include ::systemd

... in my manifest. And I have this hiera data:

systemd::service_limits:
    'openstack-nova-compute.service':
        limits:
                LimitNOFILE: 32768

But when puppet on my node I get this error:

Error while evaluating a Function Call, Class[Systemd]: parameter 'service_limits' unrecognized key 'openstack-nova-compute.service' at ...

I have looked at the docs and they do not explain how to form the hash in hiera, they just give this example:

::systemd::service_limits { 'foo.service':
  limits => {
    'LimitNOFILE' => 8192,
    'LimitNPROC'  => 16384,
  }
}

So how would I do that in hiera/yaml?

@redcricket
Copy link
Author

I have posted a question about this on stackoverflow

@ekohl
Copy link
Member

ekohl commented Nov 22, 2017

The stackoverflow answer is right: it should be a different type. I think Hash[String, Hash[String, Any]] would make the most sense while changing the default to {}.

ekohl added a commit to ekohl/puppet-systemd that referenced this issue Nov 22, 2017
op-ct pushed a commit to op-ct/puppet-systemd that referenced this issue Jun 17, 2022
Versionlock release string may contain dots
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants