All errors about quotas should include a unit

Bug #681417 reported by Soren Hansen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Ricardo Carrillo Cruz

Bug Description

Just for clarity, all errors we emit to users about quotas should specify the unit of the quota. A user may think he's being blocked from creating a 1000 MB volume, but is really being blocked from creating a 1000 GB volume.

Related branches

Soren Hansen (soren)
Changed in nova:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Ricardo Carrillo Cruz (rcarrillocruz) wrote :

Hi guys

The only place I saw there's no unit for an exceeded quota error what you can find in my branch linked to this bug.
If there are more places let me know and I'll have a look.

Regards

Revision history for this message
Ricardo Carrillo Cruz (rcarrillocruz) wrote :

Oh, and ofc, nova.sh should also not drop the database every time is launched, otherwise the tables created "nova-manage db sync" will disappear.

description: updated
Revision history for this message
Ricardo Carrillo Cruz (rcarrillocruz) wrote :

Please disregard comment #2, it was meant for other bug and I can't seem to edit the comment or remove it.
Apologies.

Revision history for this message
Thierry Carrez (ttx) wrote :

rcc: try to ping soren on IRC to check if that covers everything he had in mind, then you can propose for merging. You'll have to sign CLA and add yourself to the Authors file in your branch before you do that. See HowToContribute on the wiki for details.

Changed in nova:
assignee: nobody → Ricardo Carrillo Cruz (rcc)
status: Triaged → In Progress
Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → 2011.1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
status: Fix Released → Fix Committed
milestone: 2011.1 → none
Thierry Carrez (ttx)
Changed in nova:
milestone: none → 2011.2
status: Fix Committed → Fix Released
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.