Public bug reported:
When create resource class using placement API, and at the DB layer, we have a
retry
logic for 100 loop, and error will raise when the retry limit exceed, currently
a log
about limit exceed is generated but a ResourceClassExists Error is raised,
which is a
little bit wired and might confusing the users.
We'd better add a particular Exception for this kind of scenario and it could
be used
in other places also.
** Affects: nova
Importance: Undecided
Assignee: Zhenyu Zheng (zhengzhenyu)
Status: New
** Changed in: nova
Assignee: (unassigned) => Zhenyu Zheng (zhengzhenyu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1658868
Title:
Should raise retry limit exceed error instead of class exist in
Placement API
Status in OpenStack Compute (nova):
New
Bug description:
When create resource class using placement API, and at the DB layer, we have
a retry
logic for 100 loop, and error will raise when the retry limit exceed,
currently a log
about limit exceed is generated but a ResourceClassExists Error is raised,
which is a
little bit wired and might confusing the users.
We'd better add a particular Exception for this kind of scenario and it could
be used
in other places also.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1658868/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
