'puppet apply' should make no changes on an installed system
Bug #1087627 reported by
Ian Wells
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cisco Openstack |
Confirmed
|
Undecided
|
Unassigned | ||
| Folsom |
Incomplete
|
Medium
|
Unassigned | ||
Bug Description
When a system is running a puppet client, it effectively runs 'puppet apply' every 10 minutes or so. When this happens, if the puppet script is not carefully written, it will try and do things.
Common causes:
- 'exec' without a 'creates' or 'unless'
- exec { 'service restart xxx': } when a service {'xxx': } would be more appropriate
Commonly seen issues:
- restart of Openstack services every few minutes (Openstack nodes)
- repeated reinstallation of cobbler nodes followed by a cobbler sync (not as harmful, but it can fill up the log disk with the cobbler log file over the space of a week or two) (boot server)
We should target a no-op for all second and folllowing 'puppet apply's, both on Openstack nodes and the boot server.
| Changed in openstack-cisco: | |
| status: | New → Confirmed |
Revision history for this message
| Mark T. Voelker (mvoelker) wrote | #1 |
To post a comment you must log in.
I'm setting this to incomplete for the moment as this description lacks specifics as to what execs are problematic and/or services are getting restarted. We need to know what needs fixing in order to progress.