DB: Ignore instances in ERROR state when initializing
Review Request #154 - Created March 31, 2015 and submitted
|mitr, sgallagh, simo, twoerner|
An instance that failed to deploy should not count as a pre- existing instance. This would prevent the database from being initialized properly.
Created a first instance in error state (no database name, so nothing happened on disk).
Created a second instance with correct input. Success.
If instances in NASCENT or ERROR are guarnteed to not cause a failure if first_instance is set to true, this looks good.
Not sure what kind of error state you'll get in if that is not the case, but I guess it will be ugly either way.