| 2013-09-04 23:53:16 |
Auston McReynolds |
description |
When reddwarf fails to create security group for a instance create action, it fails to perform clean rollback (either turn the instance to error state or delete the entry of the instance from the instances table). As the side effect of this, there is one instance added in BUILD state to the instances table, which never changes its state (and user cannot delete it).
Steps to reproduce:
1. Whatever quota for security groups on nova, create those many security groups under user's account on nova.
2. Now try to create a new instance through reddwarf API.
3. Instance creation will fail and API will return an error:
{"badRequest": {"message": "SecurityGroupLimitExceeded: Quota exceeded, too many security groups. (HTTP 413)
4. Now try to list the instances. You will see a new instance added to your account which is in BUILD state.
The possibility of somebody running into this issues is very less, but if for some reason security groups don't get deleted on instance DELETE then this error will pop up or if use is using the same account for reddwarf instances and nova instances then possibility of seeing this issue is higher. |
When trove fails to create security group (or its default rule) for a instance create action, it fails to perform clean rollback (either turn the instance to error state or delete the entry of the instance from the instances table). As the side effect of this, there is one instance added in BUILD state to the instances table, which never changes its state (and user cannot delete it).
Steps to reproduce:
1. Whatever quota for security groups on nova, create those many security groups under user's account on nova.
2. Now try to create a new instance through reddwarf API.
3. Instance creation will fail and API will return an error:
{"badRequest": {"message": "SecurityGroupLimitExceeded: Quota exceeded, too many security groups. (HTTP 413)
4. Now try to list the instances. You will see a new instance added to your account which is in BUILD state.
The possibility of somebody running into this issues is very less, but if for some reason security groups don't get deleted on instance DELETE then this error will pop up or if use is using the same account for trove instances and nova instances then possibility of seeing this issue is higher. |
|
