Static units cannot be enabled

[TwizzyDizzy]

Description

systemd version: 219
module version: 2.12.0

definition of worker.target

root@tst-api01 ~ # systemctl cat worker.target
# /etc/systemd/system/worker.target
[Unit]
Description=Queue Workers
Wants=rabbitmq-server.service api-default-queue@1.service api-default-queue

[Install]
WantedBy=multi-user.target

Definition of api-default-queue.service (instantiated from template) in hiera:

systemd::manage::unit_file:
  api-default-queue@.service:
    content: |
      [Unit]
      Description=default-queue-%i
      BindsTo=worker.target

      [Service]
      Type=simple
      ExecStart=FOO
      SyslogIdentifier=default-queue-%i
      Group=FOO
      User=FOO
      Restart=on-failure
      RestartSec=10
      TimeoutStartSec=10
  api-default-queue@1.service:
    enable: true
    active: true

Expected behaviour:

Puppet tries to enables that unit but realizes that it's a static unit and does nothing.

Actual behaviour

Puppet restarts the unit

Debug: Executing: '/bin/systemctl is-enabled -- api-default-queue@1.service'
Debug: Executing: '/bin/systemctl unmask -- api-default-queue@1.service'
Debug: Executing: '/bin/systemctl enable -- api-default-queue@1.service'
Debug: Executing: '/bin/systemctl is-enabled -- api-default-queue@1.service'
Debug: Unable to enable or disable static service api-default-queue@1.service
Notice: /Stage[main]/Systemd::Manage/Systemd::Unit_file[api-default-queue@1.service]/Service[api-default-queue@1.service]/enable: enable changed 'false' to 'true'

leads to

Feb 20 19:18:28 prd-api01 systemd[1]: Stopped api-default-queue-1.
Feb 20 19:18:28 prd-api01 systemd[1]: Started api-default-queue-1.

Suggested behaviour:

It's eventually a clash of responsibilites between systemd and puppet. Meaning: "who is, in the end, reponsible for managing the state of that unit". With harder dependencies, it seems to rather be within system`s jurisdiction, on the other hand though, when there are no hard bindings between units, it makes sense for puppet to manage that unit.

Since it obviously does not make sense for the module to try to understand the interdependency between defined units (in order to not allow enable: true for static units), I'd suggest that this module accepts "static" as a valid return-value (instead of only "enable" now, probably - not verified) for systemctl is-enabled $UNIT.

[TwizzyDizzy]

Turns out I have misused the module. I tried to manage instantiated units via systemd::manage::unit_file while I should have been managing those with systemd::manage::services.

Sorry for the irritation.

Cheers
Thomas