hitting nova RAM quota results in over-general error
Bug #1501084 reported by
Neale Pickett
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Go OpenStack Exchange |
Triaged
|
Medium
|
Unassigned | ||
| juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
A new deploy was failing with the following in "juju status":
caused by: Resource limit exeeded at URL http://
The corresponding log message in nova logs was:
INFO nova.api.
I was expecting "juju status" to report which resource limit was exceeded (namely: ram). Since my role doesn't allow me permission to view the nova logs, I was at a loss as to what resource limit I had exceeded.
Revision history for this message
| Martin Packman (gz) wrote | #1 |
| Changed in goose: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in juju-core: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: openstack-provider usability |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
sendRateLimited