After exhausing OpenStack quotas, juju status output polluted
Bug #1215670 reported by
Adam Gandelman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Trying to spin up many instances against an OpenStack provider, I hit my quota and the provider refuses to create my instances. juju status seems to relay the entire provider error message which includes the instance user-data. Resulting in huge blobs in output of juju status, see attachment.
Revision history for this message
| Adam Gandelman (gandelman-a) wrote | #1 |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
| Changed in juju-core: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| tags: | added: status |
| tags: | added: openstack |
| tags: |
added: openstack-provider removed: openstack |
| Changed in juju-core: | |
| importance: | High → Medium |
| Changed in juju-core: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
I don't think quotas is specifically required to trigger this. I would probably frame it more as "large error content should be trimmed in status output."
It would be great if we detected obvious things like "UserData" and just pull that out. However any given error message might get long and we shouldn't flood the terminal with it.