Raise ResourceActionNotSupported when clearing the hooks undefined
Bug #1472515 reported by
huangtianhua
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
huangtianhua |
Bug Description
1. create a stack set pre-create hook for a resource
2. to clear the hook pre-update(not pre-create), return null
expected: raise a exception such as the resource has no the hook: pre-update to user
actual: we can find Raise ResourceActionN
for resource in engine's log, but user do not know what happended
3. Also there are some checks for resource signal and raise exceptions if fail, but the exceptions are not show to user.
Changed in heat: | |
assignee: | nobody → huangtianhua (huangtianhua) |
description: | updated |
Changed in heat: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in heat: | |
milestone: | none → liberty-3 |
Changed in heat: | |
milestone: | liberty-3 → liberty-rc1 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | liberty-rc1 → 5.0.0 |
To post a comment you must log in.
Could we also use this bug to handle the following situation?
Description of problem:
You can run the command "heat hook-clear" on any resource in the stack, even if there is no hook defined on it, and no error or warning message is returned.
How reproducible:
100%
Steps to Reproduce: PostDeployment PostDeployment
1. heat hook-clear --pre-create overcloud ControllerNodes
2. heat hook-clear --pre-create overcloud ControllerNodes
Actual results:
No error or warning
Expected results:
I should have gotten at least 1 error because I cleared the breakpoint twice. In this case, the breakpoint never existed in the first place so I was expecting 2 errors.