[
https://issues.apache.org/jira/browse/CLOUDSTACK-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav resolved CLOUDSTACK-249.
------------------------------------
Resolution: Fixed
The diff did not apply, fix it manually. Pl. use review board to submit patches.
Applied on master;
commit 71835018e53c4d60b228392535c2a04fce7a76aa
Author: Andrew Bayer <[email protected]>
Date: Mon Jan 28 15:27:09 2013 -0800
CLOUDSTACK-249: Add hostId to failed VM deploy alerts
Signed-off-by: Rohit Yadav <[email protected]>
> Add host id to failed VM deploy alerts
> --------------------------------------
>
> Key: CLOUDSTACK-249
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-249
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.0.0
> Reporter: Andrew Bayer
> Assignee: Rohit Yadav
> Priority: Minor
> Fix For: 4.1.0
>
> Attachments: CLOUDSTACK-249.diff
>
>
> When a VM fails to deploy, the alert message only includes the numeric ID of
> the VM itself, no additional identifying information. If we then want to
> figure out which host it failed on, we have to troll through the
> management-server.log. It'd be very handy if we at least had the numeric ID
> for the host in the alert message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
