-T option fails if environment not bootstrapped

Bug #1177867 reported by Sidnei da Silva on 2013-05-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

2013-05-08 16:25:11,583 Resetting environment...
2013-05-08 16:25:21,571 Error getting status, is it bootstrapped?
2013-05-08 16:25:21,572 Command (juju status) Output:

 error: failed to GET object provider-state from container juju-Enoh1eesaihahyeXeeCaht7ooHio7j
caused by: Resource at https://swift.canonistack.canonical.com/v1/AUTH_7794ec53254a47c899bc811bf33b68e3/juju-Enoh1eesaihahyeXeeCaht7ooHio7j/provider-state not found
caused by: request (https://swift.canonistack.canonical.com/v1/AUTH_7794ec53254a47c899bc811bf33b68e3/juju-Enoh1eesaihahyeXeeCaht7ooHio7j/provider-state) returned unexpected status: 404; error info: 404 Not Found

The resource could not be found.

2013-05-08 16:25:21,572 Deployment stopped. run time: 9.99315404892

Ideally it should be a noop and exit 0.

Kapil Thangavelu (hazmat) wrote :

I'm a little wary of masking errors from the juju cli at this early stage, the env could be broken/unavailable for a few different reasons (invalid perms/account, bootstrap node not responding, etc).

Changed in juju-deployer:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers