puppet-forge-server service not showing up as 'enabled'

[danjng]

Is anyone else experiencing this? I am receiving the notification below each time I do a Puppet run (which results in a change showing up in the console):

Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for master
Info: Applying configuration version '1441138415'
Notice: /Stage[main]/Forge_server::Service/Service[puppet-forge-server]/enable: enable changed 'false' to 'true'
Notice: Applied catalog in 11.45 seconds

Doing a quick puppet resource service puppet-forge-server results in:

service { 'puppet-forge-server':
  ensure => 'running',
}

This is despite having the enable parameter set to true.

Running a systemctl puppet-forge-server enable results in:

[root@lab puppet-forge_server]# systemctl enable puppet-forge-server
puppet-forge-server.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig puppet-forge-server on
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
[root@lab puppet-forge_server]# 

Any ideas?

[i11]

Could be because of our init.d script isn't perfect and systemd doesn't want to play along. I'll have a look as soon as I can.

[i11]

https://github.com/unibet/puppet-forge_server/commit/cade0bc2433d00a41571aba70c7e1da91702175a should fix it. Let me know if it doesn't.

[danjng]

Awesome! No more notices. Things look to be working out nicely!