reporting an error from the environment isn't formatted well

[Richard Harding]

In testing watching a deployer process there are bundles with the default constraints that caused a Go EnvError. This came out of the watcher as

{
   "Response":{
      "Changes":[
         {
            "Status":"completed",
            "DeploymentId":1,
            "Error":"<Env Error - Details:\n { u'Error': u'json: cannot unmarshal string into Go value of type uint64',\n u'RequestId': 1,\n u'Response': { }}\n >",
            "Time":1384461205
         }
      ]
   },
   "RequestId":11
}

The Error should be in a better format to be able to be used. Either a nested object, or just a message.

[Richard Harding (rharding)]

In talking with Francesco, this is the string representation of the EnvError. We can try to hack around this by checking the error type and cleaning the error in this case, but maybe we should file this up to the client and have it update it's original representation.

[Brad Crittenden (bac)]

The error needs to be returned in a better format in the upstream, either the deployer or the juju-client.