Instance quota exceeded with many self.driver.spawn errors
Bug #900939 reported by
Nachi Ueno
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Medium
|
Guangyu Suo |
Bug Description
When we do the long running test, we got instance quota exceeded with many self.driver.spawn errors.
Because nova didn't cleanup db record when nova get self.driver.spawn error, then the number of instance reaches to the Quota value with no actual instance.
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → yugsuo (yugsuo) |
Changed in openstack-qa: | |
status: | New → Confirmed |
no longer affects: | openstack-qa |
To post a comment you must log in.
Hello, I want to ask a question about this issue:
I added "raise Exception" before self.driver.spawn() to find this error, like follows:
raise Exception spawn(context, instance, image_meta,
injected_ files, admin_password,
self. _legacy_ nw_info( network_ info),
block_ device_ info)
self.driver.
then, I booted a new instance, and got the following result:
$nova list ------- ------- ------- ------- ----+-- -----+- ------- +------ ----+ ------- ------- ------- ------- ----+-- -----+- ------- +------ ----+ 4a45-46e6- a80a-519bf43a05 0a | test1 | ERROR | | ------- ------- ------- ------- ----+-- -----+- ------- +------ ----+
+------
| ID | Name | Status | Networks |
+------
| 3da5acb5-
+------
$ mysql> select resource,in_use from quota_usages; -----+- ------- + -----+- ------- + -----+- ------- +
+------
| resource | in_use |
+------
| instances | 1 |
| ram | 512 |
| cores | 1 |
+------
then, I deleted this instance: 4a45-46e6- a80a-519bf43a05 0a
$ nova delete 3da5acb5-
and the quota_usages is reset to 0 like normally: -----+- ------- + -----+- ------- + -----+- ------- +
$ mysql> select resource,in_use from quota_usages;
+------
| resource | in_use |
+------
| instances | 0 |
| ram | 0 |
| cores | 0 |
+------
What I want to ask is that it is a bug ? Even if we got an error instance, but it is still an instance. After you delete it, the resources belonging to it will be released, and quota_usages table will be normal too.
Am I right ?