mcollective init file hardcoded to old mcollective confdir

[bhasterix]

Init file created for mcollective server or client with either

class { '::mcollective':
      middleware_hosts => [ $::activemq_server ],
}

Or

class { '::mcollective':
  client           => true,
  middleware_hosts => [ $::activemq_server ],
}

on RHEL 6.7:
contains the following line:

      daemon ${daemonopts} ${mcollectived} --pid=${pidfile} --config="/etc/puppetlabs/mcollective/server.cfg" --daemonize

Note the "/etc/pupplabs/mcollective/..."

In "mcollective/init.pp" the confidr is set as:

  $confdir          = '/etc/mcollective',

The result of this is that my config is correctly created in /etc/mcollective/ but when the mcollective service starts it is using an incorrect default configuration created in /etc/puppetlabs/mcollective/.

If I can get a chance to dig into this myself I will, but just in case I wanted this issue logged in case anyone else comes across it.

[bhasterix]

A workaround is to reset the conf dir in your manifest:

class { '::mcollective':
  middleware_hosts => [ $::activemq_server ],
  confdir          => '/etc/puppetlabs/mcollective',
}

or of course edit the init file, but that's even more work.

[rhoml]

I think the approach should be to manage the init file with the puppet module

[jyaworski]

What's the status of this?