Issue #21284 has been reported by Jason Birch. ---------------------------------------- Bug #21284: puppet apply --lastrunfile=/dev/null does bad things to special devices https://projects.puppetlabs.com/issues/21284
* Author: Jason Birch * Status: Unreviewed * Priority: Low * Assignee: * Category: * Target version: * Affected Puppet version: 3.1.1 * Keywords: * Branch: ---------------------------------------- I don't need puppet reports right now, and am working on a system with a limited /var partition. I thought I could work around this temporarily by doing something like: puppet apply --no-report --lastrunfile=/dev/null --lastrunreport=/dev/null --postrun_command='rm -rf /var/lib/puppet' .... Unfortunately, due to changes introduced at https://github.com/puppetlabs/puppet/commit/e40439196af14f90d8a321999b782f24a3fa59f6, my /dev/null is turned into a regular file. It would be good if puppet could fail fast in the case of options like lastrunfile taking parameters that don't make sense, or to not change permissions on that file if they are something else? I'm sure the real solution is more nuanced. Regards, JB -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
