failed to unmarshall 503 charmstore
Bug #1461954 reported by
Aaron Bentley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
juju-core |
Won't Fix
|
Low
|
Unassigned | ||
juju-quickstart |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When the charm store returns a 503, the body may be html, but juju doesn't handle that:
http://
description: | updated |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Low |
description: | updated |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
summary: |
- failed to unmarshall 503 + failed to unmarshall 503 charmstore |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
milestone: | none → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
To post a comment you must log in.
Quickstart is just reporting an error from juju-core. juju-gui- 21": cannot get archive: cannot unmarshal error response "<html> <body>< h1>503 Service Unavailable< /h1>\nNo server is available to handle this request. \n</body> </html> \n": invalid character '<' looking for beginning of value"
For instance:
"juju-quickstart: error: bad API response: cannot retrieve charm "cs:trusty/
The message above, starting from "cannot retrieve charm...", is the error returned by the ServiceDeploy API call to juju-core.
I don't think we can do much more in such cases, therefore marking as invalid.