voxpupuli / puppet-rabbitmq

RabbitMQ Puppet Module
http://forge.puppetlabs.com/puppet/rabbitmq
Apache License 2.0
172 stars 503 forks source link

parameter 'service_entry' unrecognized key 'LimitNOFILE' #1021

Closed alphamonkey79 closed 2 weeks ago

alphamonkey79 commented 2 weeks ago

Affected Puppet, Ruby, OS and module versions/distributions

How to reproduce (e.g Puppet code you use)

module block:

  if $facts['kernel'] == 'Linux' {
    systemd::manage_dropin { 'service-90-limits.conf':
      unit                    => "${service_name}.service",
      selinux_ignore_defaults => ($facts['os']['family'] == 'RedHat'),
      service_entry           => {
        'LimitNOFILE'    => $file_limit,
        'OOMScoreAdjust' => $oom_score_adj,
      },
    }
  }

What are you seeing

when attempting to upgrade to module v13.7.0 we are encountering the following in puppet run:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Systemd::Manage_dropin[service-90-limits.conf]: parameter 'service_entry' unrecognized key 'LimitNOFILE'

What behaviour did you expect instead

Output log

Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Systemd::Manage_dropin[service-90-limits.conf]: parameter 'service_entry' unrecognized key 'LimitNOFILE'

Any additional information you'd like to impart

wyardley commented 2 weeks ago

What version were you updating from? Is it possible that this is an issue with it pulling in a newer version of https://github.com/voxpupuli/puppet-systemd

alphamonkey79 commented 2 weeks ago

That is in fact the exact issue. We are using an unsupported puppet module for systemd. We will update this and retry. Case closed. Thank you