canmove, Confirmed users
2,850
edits
ReleaseEngineering/Puppet/Usage: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
ChrisCooper (talk | contribs) No edit summary |
||
| Line 231: | Line 231: | ||
<p>If you're encountering errors or weird behaviour and the normal output isn't sufficient for debugging you can enhance it with --evaltrace and --debug. Together, they will print out every command that Puppet runs, including things which are used to determine whether a file or package needs updating.</p> | <p>If you're encountering errors or weird behaviour and the normal output isn't sufficient for debugging you can enhance it with --evaltrace and --debug. Together, they will print out every command that Puppet runs, including things which are used to determine whether a file or package needs updating.</p> | ||
=== Forcing a package re-install === | |||
Especially when testing, you may have to iterate on a single package install to get it right. If you need to re-install an existing package, you'll need to remove the package contents and/or the marker file that flags that package as installed. | |||
* Linux: packages installed as rpms should be removed as one normally would for an rpm, i.e. <code>rpm -e rpmname</code>, which will delete all of the files and remove the package from the db, or <code>rpm -e --justdb rpmname</code>, which will leave all of the files and remove the package from the db | |||
* Mac: manually cleanup the installed files, and remove the marker file for your package. The marker file lives under <code>/var/db/</code> and will be named <code>.puppet_pkgdmg_installed_pkgname.dmg</code>. | |||
You can now re-test your package install with [[ReleaseEngineering:Puppet:Usage#Testing_a_slave|the command above]], i.e. <code>puppetd --test ...</code>. | |||
=== Cleaning up === | === Cleaning up === | ||