SoftwareDeployment does not invoke all actions defined in SoftwareComponent
Bug #1416994 reported by
Thomas Spatzier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Thomas Spatzier |
Bug Description
A SoftwareComponent may define a list of configs to applied to a server for different lifecycle events. According to the design of SoftwareComponent, those configs define that actions to which they apply and this overrides the 'actions' property of the associated SoftwareDeployment resource.
When a SoftwareDeployment is associated to a SoftwareComponent, it should always invoke the in-instance hook and let the in-instance hook decide whether to do something or not. Currently, however, the special handling for SoftwareComponent seems to be missing in places in the SoftwareDeployment resource.
See also this review for reference:
https:/
Changed in heat: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
I can look into this but will probably not have the chance to look into it this week (traveling). If anyone wants to grab it, feel free. Otherwise, I will provide a fix next week.