Puppet: System Administration Automated

Support

Ticket #800 (closed defect: fixed)

Opened 1 year ago

Last modified 10 months ago

Configurations that fail because of unresolved dependencies are cached anyway

Reported by: luke Assigned to: luke
Priority: high Milestone: misspiggy
Component: library Version: 0.23.2
Severity: major Keywords: configuration,cache
Cc: Triage Stage: Accepted
Attached Patches: None Complexity: Unknown

Description

The configuration caching is too early, in that configurations that are invalid because of unresolved dependencies are already cached. This basically works ok on normal clients, because they'll just run again in 30 minutes, but it requires manual intervention on servers if the servers update their own configurations (e.g., they do an svn update in the configuration directory).

The cache should not be created until the dependency graph is created and valid, so that we know we only ever write a valid configuration.

Change History

09/07/07 03:51:13 changed by luke

I created a test in [caad11a9d15210017f75918b50184bc12f2cc1d0], but I had to disable it, because I could not fix the problem. I don't think it's fixable until the switch to REST, because that will bring with it a complete redesign in how we handle configurations.

09/07/07 03:51:19 changed by luke

  • status changed from new to assigned.

11/13/07 05:41:24 changed by luke

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

Fixed in [72510bfaa65e97f4eaaf246ef8f1c155716967b6].