> > If we support this functionality and there is a failure during the catalog > run after a reboot at the end has been requested, what would be your > expectation for the system. >
> Would you expect it to: > > A) still reboot > B) not reboot > C) something else (please comment) I vote A. As I understand it, skipping the reboot means throwing it into the oblivion; there's no way for the next puppet run to pick the reboot up because the event triggering it probably won't occur again. I've had plenty of small, inconsequential failures and wouldn't want them affecting other (reboot requiring) things. It may be in a state that won't boot cleanly due to the failing half run > catalog. I would think that a sequence of steps that may result in an unbootable system should be ordered such that the last item is the reboot, which would get around that issue. Eric > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To post to this group, send email to puppet-dev@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
