On Wed, Jan 20, 2016 at 09:31:32PM +0100, William Reade wrote: > But: if there are times it's inconvenient and not just surprising, we > should surely be able to disable it. Gabriel/Bogdan, would you be able to > address this?
I'm +1 on the feature if it can be turned off, especially in a dev/test environment. It certainly does cross the line onto the inconvenient side when it can cover over race conditions. For production cases, like deploying openstack in a customer data center, a sensible retry limit with backoff makes sense to me, mostly agreeing with what William has already said. As long as it's discoverable what happened and when -- referencing #1530840, we should be able to satisfy both use cases (dev & production). -- David Britton <[email protected]> -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
