Quota exceeded for instances

Bug #1187368 reported by Dolph Mathews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Triaged
Low
Unassigned

Bug Description

Log: http://logs.openstack.org/31559/2/check/gate-tempest-devstack-vm-quantum/27194/

There are a lot of failed tempest tests in this log, but the ones that stand out are regarding instance quota:

======================================================================
ERROR: test suite for <class 'tempest.api.volume.test_volumes_actions.VolumesActionsTest'>
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 208, in run
    self.setUp()
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 291, in setUp
    self.setupContext(ancestor)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 314, in setupContext
    try_run(context, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 478, in try_run
    return func()
  File "/opt/stack/new/tempest/tempest/api/volume/test_volumes_actions.py", line 37, in setUpClass
    cls.flavor_ref)
  File "/opt/stack/new/tempest/tempest/services/compute/json/servers_client.py", line 81, in create_server
    resp, body = self.post('servers', post_body, self.headers)
  File "/opt/stack/new/tempest/tempest/common/rest_client.py", line 266, in post
    return self.request('POST', url, headers, body)
  File "/opt/stack/new/tempest/tempest/common/rest_client.py", line 394, in request
    resp, resp_body)
  File "/opt/stack/new/tempest/tempest/common/rest_client.py", line 455, in _error_checker
    raise exceptions.OverLimit(resp_body)
OverLimit: Quota exceeded
Details: Quota exceeded
Details: {u'overLimit': {u'message': u'Quota exceeded for instances: Requested 1, but already used 10 of 10 instances', u'code': 413, u'retryAfter': u'0'}}

Revision history for this message
Sean Dague (sdague) wrote :

So I thought we fixed that in cinder. This is really a cinder issue, not a tempest issue. So assigning there.

no longer affects: tempest
no longer affects: cinder
Changed in tempest:
status: New → Triaged
importance: Undecided → High
milestone: none → havana-2
Revision history for this message
Sean Dague (sdague) wrote :

It looks like we are blowing past our servers quota, which is kind of amazing if true. It would be good for someone to dig through the logs to figure out where we are leaking servers.

Revision history for this message
Attila Fazekas (afazekas) wrote :

Looks like all server creation is failed.

https://bugs.launchpad.net/nova/+bug/1185834 is the root cause of the server boot issues.
I see many Similar KeyErrors in the log.

Revision history for this message
Dolph Mathews (dolph) wrote :

Agree with Attila- this is definitely at least a partial dupe of bug 1185834, but I hadn't seen the quota errors in my experience with bug 1185834.

Revision history for this message
Attila Fazekas (afazekas) wrote :

The quota issues has two possible sources:

If the server creation failes in setUpClass it not always be deleted.
If the creation fails in other cases does not a waited for deletion in every case.

I decrease the priority to low, the fail code path is less important at the moment.

Changed in tempest:
importance: High → Low
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.