Puppet: System Administration Automated

Support

Ticket #801 (closed defect: fixed)

Opened 1 year ago

Last modified 1 year ago

Noop causes resources not to get scheduled on the next run

Reported by: luke Assigned to: luke
Priority: normal Milestone: misspiggy
Component: transactions Version: 0.23.2
Severity: normal Keywords: transactions, noop, schedule
Cc: Triage Stage: Accepted
Attached Patches: None Complexity: Unknown

Description

If you have resources on a schedule and you run your configuration in noop mode, puppet marks the resources as having been run, which means that the next run does not apply the resource, even though it should.

Change History

09/07/07 17:58:29 changed by luke

  • status changed from new to closed.
  • resolution set to fixed.

Fixed in [ca57c793d4f1ad249f63f26609be2fa9208ca244].