| 2015-10-08 07:57:16 |
Md Nadeem |
bug |
|
|
added bug |
| 2015-10-08 07:57:53 |
Md Nadeem |
zaqar: assignee |
|
MD NADEEM (mail2nadeem92) |
|
| 2015-10-13 02:04:32 |
Victoria Martinez de la Cruz |
zaqar: status |
New |
Confirmed |
|
| 2015-10-13 02:04:39 |
Victoria Martinez de la Cruz |
zaqar: importance |
Undecided |
Medium |
|
| 2015-10-21 11:24:21 |
Md Nadeem |
summary |
Creating a pool or flavor with an existing name should through an Exception |
Creating a pool with an existing name should through an Exception |
|
| 2015-10-21 11:38:42 |
Md Nadeem |
description |
zaqar allow to create a pool or flavor with the name of which a pool or flavor is already exist. The create command simply update the existing pool or flavor. So there is a chance that some parameters like group name of the existing pool get updated.
So to avoid this zaqar server should through an exception that point to the error name already exists. |
As of now creating a new pool with the name, of which a pool is already exist in the Env, will update the existing pool.
Prob: A user has to first check all existing pool name before choosing a name for the new pool, otherwise there is a probability that the user will update an existing pool unintentionally.
Solution: create api should through "name exists" exception in case of duplicate name.
Suggestion: Always use patch api to update an existing pool. |
|
| 2015-10-21 11:48:30 |
Md Nadeem |
description |
As of now creating a new pool with the name, of which a pool is already exist in the Env, will update the existing pool.
Prob: A user has to first check all existing pool name before choosing a name for the new pool, otherwise there is a probability that the user will update an existing pool unintentionally.
Solution: create api should through "name exists" exception in case of duplicate name.
Suggestion: Always use patch api to update an existing pool. |
As of now creating a new pool with the name, of which a pool is already exist in the Env, will update the existing pool.
Prob: A user has to first check all existing pool name before choosing a name for the new pool, otherwise there is a probability that the user will update an existing pool unintentionally.
Solution: pool create api should through "PoolNameExist" exception in case of duplicate pool name.
Suggestion: Always use patch api to update an existing pool. |
|
| 2015-10-21 11:55:50 |
OpenStack Infra |
zaqar: status |
Confirmed |
In Progress |
|
| 2015-12-03 06:06:27 |
Reedip |
summary |
Creating a pool with an existing name should through an Exception |
Creating a pool with an existing name should thow an Exception |
|
| 2016-04-13 06:16:26 |
Md Nadeem |
zaqar: status |
In Progress |
Invalid |
|
| 2016-04-13 06:16:32 |
Md Nadeem |
zaqar: assignee |
MD NADEEM (mail2nadeem92) |
|
|
