Comment 2 for bug 1489237

Deployer was using Ali before status was there and used the watch Api.. To
reconstruct status.. Apparently the sla on that has degraded with larger
delta delays to reflect current reality. Deployed should move to the
current status Api to avoid issues. Also would effect the gui i suspect,
but not clear anyone uses that.
On Thu, Aug 27, 2015 at 1:50 AM Stuart Bishop <email address hidden>
wrote:

> I get the same issue if I I wait for 'juju-deployer -f service' to
> return an error code for each service before continuing. I get this a
> lot with the local provider, but the traceback in the description is
> from a joyent deploy.
>
> --
> You received this bug notification because you are subscribed to juju-
> deployer.
> Matching subscriptions: deployer
> https://bugs.launchpad.net/bugs/1489237
>
> Title:
> Race where recently destroyed service is not redeployed causing
> tracebacks
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-deployer/+bug/1489237/+subscriptions
>