Issue #13220 has been updated by Chris Price. Status changed from Unreviewed to Accepted
I am not necessarily certain about the "best effort" approach--I'd be concerned that this would open the door to some data loss (although, one could certainly make the case that since it'd be a non-default option that needed to be explicitly overridden, that the user has accepted the risk). I think the "--nofilebucket" cli flag for the 'apply' command sounds perfectly reasonable, though... and probably wouldn't be terribly difficult to implement. I'm not sure when we might be able to devote resources to this, but we would definitely be open to a patch submission. ---------------------------------------- Feature #13220: option to ignore remote filebucket failures, or treat as non-blocking errors https://projects.puppetlabs.com/issues/13220#change-58644 Author: Jason Antman Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.6.12 Keywords: filebucket Branch: Currently, with file bucketing to the master enabled, i.e. in site.pp like: filebucket { "main": server => "puppet", path => false } File { backup => "main" } A failure to write to the filebucket causes the File resource content change on the node to fail. This prevents a configuration which would otherwise be capable of being run masterless via 'puppet apply' from being run in this way. My specific case in point - all of my configs are stored in SVN, and our puppetmaster is configured with Puppet. Our DR plan for the master is to install the puppet-server RPM and dependencies, check out SVN to /etc/puppet, and "puppet apply" site.pp. Unfortunately, as the master isn't up and running yet, the filebucket backup operation returns "Connection refused"... and there's no way to get the master up and running for the filebucket to succeed (aside from manually modifying the working copy of the configs, which is far from ideal). So, I propose either: 1. Add a setting to puppet.conf, or the File or Filebucket resources, to make remote filebucket backups a best-effort operation, and warn (but don't error out) if they fail (for cases where getting the config pushed is more important than getting backups). or 2. Adding a --nofilebucket flag to 'puppet apply' which will either do the above, or altogether prevent remote filebucket backups. -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
