B! If I had a catalog that ended with a reboot and there was an issue I would be very surprised (and probably upset) if my machine rebooted. It may be in a state that won't boot cleanly due to the failing half run catalog.
On Mon, Sep 16, 2013 at 2:52 PM, Rob Reynolds <[email protected]> wrote: > We are discussing a feature for the initial reboot provider where we apply > the rest of the catalog resources and then reboot. Right now the behavior > is that we would stop applying the rest of the catalog and reboot once the > catalog run is finished (with those resources after the reboot skipped). > > We've also discussed the idea where we would finish applying the catalog > and then reboot at the end. > > 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) > > -- > Rob Reynolds > Developer, Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/puppet-dev. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
