Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6759

systemd provider does not understand "indirect" status / tries to turn off service on each run

    Details

    • Template:
    • Acceptance Criteria:
      Hide

      The rpcbind service on RedHat 7 should show up as enabled => false when puppet is run with puppet resource service rpcbind.

      Show
      The rpcbind service on RedHat 7 should show up as enabled => false when puppet is run with puppet resource service rpcbind .
    • Team:
      Puppet Developer Experience
    • Story Points:
      1
    • Sprint:
      PDS 2016-11-30
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      The systemd provider now considers services with the 'indirect' enabled state to be disabled.
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      annoyance. covered well by mocked unit tests

      Description

      Following occurs with each puppet run, which causes annoyance:
      Service[rpcbind]/enable: enable changed 'true' to 'false'

      The rpcbind service returns "indirect" as a status to is-enabled
      _*/bin/systemctl is-enabled rpcbind
      indirect*_

      This presumably causes puppet to constantly think it's not turned off (standard output should be enabled/disabled

      Additional info from systemctl
      _*/bin/systemctl status rpcbind.service
      รข rpcbind.service - RPC bind service
      Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
      Active: inactive (dead)*
      _

      Note that a workaround is to set enable to "true" and ensure to "stopped" to keep it stopped, BUT that requires the hosts to have rpcbind installed - if it is not then it produces an error in the puppet run.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  alpha Robert Rosengren
                  QA Contact:
                  Eric Thompson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: