You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2012/10/03 19:44:07 UTC
[jira] [Created] (CLOUDSTACK-249) Add host id to failed VM deploy
alerts
Andrew Bayer created CLOUDSTACK-249:
---------------------------------------
Summary: 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
Components: Management Server
Affects Versions: 4.0.0
Reporter: Andrew Bayer
Priority: Minor
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
[jira] [Updated] (CLOUDSTACK-249) Add host id to failed VM deploy
alerts
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Bayer updated CLOUDSTACK-249:
------------------------------------
Attachment: CLOUDSTACK-249.diff
The patch adds the host ID to the call to updateVmStateForFailedVmCreation and includes it in the alert message.
> 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
> Components: Management Server
> Affects Versions: 4.0.0
> Reporter: Andrew Bayer
> Priority: Minor
> 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
[jira] [Updated] (CLOUDSTACK-249) Add host id to failed VM deploy
alerts
Posted by "Alex Huang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Huang updated CLOUDSTACK-249:
----------------------------------
Fix Version/s: 4.1.0
> 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
> Components: Management Server
> Affects Versions: 4.0.0
> Reporter: Andrew Bayer
> 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