2014-06-12 16:03 GMT+02:00 Stephen Gallagher <sgallagh@redhat.com>:
On 06/11/2014 10:16 PM, Simo Sorce wrote:
> Btw, I am not sure I understand why a crash would be resolved by a
> deploy, there is quite a difference between an error in deploying
> and a runtime error a while after successfully deployed.

That's a case where resetError() is the more likely answer (or a
package update fixing the crash bug). I can add a separate Crashed
state if you really want it, but it seems superfluous to me.

I’d rather not; by my yardstick of “would the user treat the system differently in the two states?”, there is no difference between {crashed,failed with an error message} {while starting {for the first time, for the $Nth time}, after successful start and running fo some time}: the next thing to do is to review any logs applicable, and the ways to remedy are to either change the configuration (resetError()), to update to a fixed version (vaguely ~deploy), or to repair a truly broken system (e.g. lost/corrupted files) by manual action we aren‘t making easier.