hitting nova RAM quota results in over-general error

Bug #1501084 reported by Neale Pickett
18
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://10.24.0.135:8774/v2/$BIGNUM/servers

The corresponding log message in nova logs was:

    INFO nova.api.openstack.wsgi [req-$UUID $BIGNUM2 $BIGNUM3] HTTP exception thrown: Quota exceeded for ram: Requested 8192, but already used 147456 of 153600 ram

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 :

sendRateLimitedRequest in goose needs to propogate the body of the http response.

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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.