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

Service Provider for Suse tries enable false to true even if its already ON

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: PUP 3.7.3
    • Fix Version/s: None
    • Component/s: None
    • Environment:

      Suse Sles 11 sp2 and sp3

    • Template:
    • Team:
      Platform OS
    • UX Priority:
      Normal

      Description

      After upgrading from puppet 3.5.1 to 3.7.1 and also with puppet 3.7.3 the service provider redhat.rb for Suse is broken. At every Puppet run puppet tries to enable from "false" to "true" the Services even if they are already ON and running. I could reproduce this, when you set only runlevel 3 and 5 ON, then the next run does not try to re-enable the service. But if you have for a service runlevel 2 or 4 set, then it tries at every puppet run to enable it.

      Notice: /Stage[main]/Puppet::Client/Service[puppet]/enable: enable changed 'false' to 'true'

      Setting the provider/service/redhat.rb (enabled?) part back as it was in puppet 3.5.1 then everything is working as it should.

      So please fix this or maybe setup a suse.rb if this is causing problem in the redhat.rb.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                Aedu Adrian Raemy
                QA Contact:
                Erik Dasher
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: