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

puppet apply --noop triggers services on file audit content changes

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: PUP 3.6.2
    • Fix Version/s: None
    • Component/s: Catalog Application
    • Labels:
    • Environment:

      CentOS 7
      puppet-3.6.2-3.el7.noarch

    • Template:

      Description

      To reproduce:
      site.pp:

      file { $myfile:
        ensure => present,
        audit => 'content';
      }
       
      File[$myfile] ~> Service[$myservice]
      

      # rm $myfile
      # puppet apply --noop --test site.pp
      

      Expected: the output would show what would be done, but nothing would be done

      Actual: the ensure is marked "noop", but the audit change is not. The service is triggered.

      Partial command output [redacted]:

      Notice: .../File[myfile]/ensure: current_value absent, should be file (noop)
      Notice: .../File[myfile]/content: audit change: previously recorded value  has been changed to absent
      Info: .../File[myfile]: Scheduling refresh of Service[myservice]
      Notice: ../Service[myservice]: Triggered 'refresh' from 2 events
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                BradRubenstein Brad Rubenstein
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support