Comment 2 for bug 1227450

Does that assumes it wasn't some transient error on the provider end that
was out of user care or control. ie the cloud just barf'd.. Does the user
need to be responsible for that? ie. we do eventually consistent aws ops
because of eventual consistency.. which are effectively guards against
transient conditions at a provider, seems sane to extend.

On Thu, Sep 19, 2013 at 5:39 AM, John A Meinel <email address hidden>wrote:

> I believe the intent was that we could add a "juju resolved" command
> that would let you indicate to Juju that the error has been resolved and
> Juju should try again.
>
>
> ** Changed in: juju-core
> Importance: Undecided => Medium
>
> ** Changed in: juju-core
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1227450
>
> Title:
> juju does not retry provisioning against transient provider errors
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1227450/+subscriptions
>