Bug 1216917

Summary: Clearing non-existing hooks yields no error message
Product: [Community] RDO Reporter: Udi Kalifon <ukalifon>
Component: openstack-heatAssignee: Zane Bitter <zbitter>
Status: CLOSED CURRENTRELEASE QA Contact: Amit Ugol <augol>
Severity: medium Docs Contact:
Priority: unspecified    
Version: trunkCC: jpeeler, srevivo
Target Milestone: ---   
Target Release: Kilo   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 16:05:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Udi Kalifon 2015-04-29 08:16:56 UTC 
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:
1. heat hook-clear --pre-create overcloud ControllerNodesPostDeployment
2. heat hook-clear --pre-create overcloud ControllerNodesPostDeployment


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.
Comment 1 Chandan Kumar 2016-05-19 16:05:20 UTC 
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.
Comment 2 Zane Bitter 2016-05-19 23:18:43 UTC 
This was fixed in Liberty.