event list not showing proper message for deployment signal
Bug #1300679 reported by
Qiming Teng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Qiming Teng | ||
Icehouse |
Fix Released
|
Medium
|
Steve Baker |
Bug Description
The event list for a stack that contains SoftwareDeployment resource with signal_transport set to values other than 'NO_SIGNAL', we will (hopefully) get a signal from a VM server.
When the signal is processed at the engine/resource level, it cannot process the 'details' sent with the signal that contains {deploy_stdout: xxx, deploy_stderr: yyy, deploy_status_code: <n> }. So when a user tries 'heat event-list', the resource_
Changed in heat: | |
assignee: | nobody → Qiming Teng (tengqim) |
Changed in heat: | |
status: | New → In Progress |
Changed in heat: | |
milestone: | none → juno-1 |
importance: | Undecided → Medium |
tags: | added: icehouse-backport-potential |
tags: | removed: icehouse-backport-potential |
tags: | removed: in-stable-icehouse |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/84665 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=5df976875f8 dbdd0ada5a66e53 4547e764a30231
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5df976875f8dbdd 0ada5a66e534547 e764a30231
Author: tengqm <email address hidden>
Date: Thu Apr 3 04:44:40 2014 +0800
Fix status reason in events for deployment signals
When a signal is received and processed by a Resource, there could be an
event generated automatically. For such an event, Heat is supposed to
provide some useful message (including status_reason). But currently,
the resource code can only process ceilometer alarms and watch rules,
for signals sent for a SoftwareDeployment resource, the signal is only
providing an string 'Unknown' as the status change reason. This is
confusing when a user performs 'heat event-list stack'.
This patch adds an additional check (guess) whether the signal comes
from a SoftwareDeployment. If that is the case, fill in the status
reason as 'deployment succeeded', or 'deployment failed (n)', where n is
the deploy_status_code that comes with the signal.
Closes-Bug: #1300679 fdcdd365983df58 f4d338de849
Change-Id: Ic970a5dac923ff