You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/10/30 08:59:35 UTC
[jira] [Commented] (CLOUDSTACK-7767) [Events] All events are not
generated for snapshot creation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189773#comment-14189773 ]
ASF GitHub Bot commented on CLOUDSTACK-7767:
--------------------------------------------
GitHub user anshul1886 opened a pull request:
https://github.com/apache/cloudstack/pull/27
CLOUDSTACK-7767: fixed events are not generated for snapshot creation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-7767
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/27.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #27
----
commit d8b46b81b946672ab6836f13ea0389cee63321d8
Author: Anshul Gangwar <an...@citrix.com>
Date: 2014-10-28T06:19:30Z
CLOUDSTACK-7767: fixed events are not generated for snapshot creation
----
> [Events] All events are not generated for snapshot creation
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-7767
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7767
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Snapshot
> Affects Versions: 4.5.0
> Environment: Latest build from 4.5 with commit [root@BPKxDmS ~]# cloudstack-sccs
> 562c89544e80dcd61ae5fd179eb8546de2598b33
> Reporter: Sanjeev N
> Assignee: Anshul Gangwar
> Priority: Critical
> Fix For: 4.5.0
>
> Attachments: cloud.dmp, management-server.rar
>
>
> [Events] All events are not generated for snapshot creation
> Steps to Reproduce:
> ===============
> 1.Bring up CS with latest build from 4.5
> 2.Deploy a vm using cent os template
> 3.Take a snapshot on the root disk of the vm
> 4.Verify the cloud.events table for the snapshot events
> We could see events with states "created,sheduled,started and completed" for vm,volume and template whereas there is only one event with state "scheduled" for snapshot creation.
> So by looking at the events user will not be able to find out whether the snaphot creation is completed of not.
> Following is the DB snippet:
> mysql> select id,uuid,type,state,description from event where type in ("SNAPSHOT.CREATE","VM.CREATE","VOLUME.CREATE","TEMPLATE.CREATE");
> +-----+--------------------------------------+-----------------+-----------+--------------------------------------------------------------------------------+
> | id | uuid | type | state | description |
> +-----+--------------------------------------+-----------------+-----------+--------------------------------------------------------------------------------+
> | 189 | 1f48cbef-648e-4728-9eb1-5178bea3b4fd | SNAPSHOT.CREATE | Scheduled | creating snapshot for volume: 10 |
> | 207 | 9162ed93-bd6c-4e78-8f4a-1836859f5009 | SNAPSHOT.CREATE | Scheduled | creating snapshot for volume: 15 |
> | 208 | 261b95a7-0a4d-45cd-9922-3cde8640ab02 | SNAPSHOT.CREATE | Scheduled | creating snapshot for volume: 15 |
> | 212 | e80e1383-944b-4ac9-bc86-70511de86c94 | SNAPSHOT.CREATE | Scheduled | creating snapshot for volume: 15 |
> | 168 | 518e4ae7-e506-4b93-a8b5-696777b91706 | TEMPLATE.CREATE | Completed | Successfully completed creating template. Id: 202 name: cent53 |
> | 193 | 3d20409e-a9e5-438a-9a00-2deb23ee87fe | TEMPLATE.CREATE | Created | Successfully created entity for creating template |
> | 194 | 528f823e-b817-4b9a-8935-2f57ac5a4c9b | TEMPLATE.CREATE | Scheduled | creating template: fromSnapRoot10 |
> | 195 | 9ab1d914-9f30-4a3d-8070-1fdce6827f6d | TEMPLATE.CREATE | Started | creating template. Template Id: 203 from snapshot Id: 1 |
> | 196 | d2676d55-84c8-4486-9aca-0f3eda74a4a7 | TEMPLATE.CREATE | Completed | Successfully completed creating template. Template Id: 203 from snapshot Id: 1 |
> | 154 | 3b9207d6-d120-4762-b9e3-423f849870d6 | VM.CREATE | Created | Successfully created entity for deploying Vm. Vm Id: 8 |
> | 155 | 7c47beb2-e105-478f-9575-e3ab1b2709ec | VM.CREATE | Scheduled | starting Vm. Vm Id: 8 |
> | 156 | 27718b57-b679-412b-b983-0f9cf7757930 | VM.CREATE | Started | starting Vm. Vm Id: 8 |
> | 159 | 6b5bece5-bfab-41c0-906e-8fbec2ddd2bf | VM.CREATE | Completed | Successfully completed starting Vm. Vm Id: 8 |
> | 170 | 66412dc3-fc03-4a2d-b796-807bd6ec096f | VM.CREATE | Created | Successfully created entity for deploying Vm. Vm Id: 10 |
> | 171 | a6c91812-9218-451c-a801-60652089ba7b | VM.CREATE | Scheduled | starting Vm. Vm Id: 10 |
> | 172 | 3f0cd706-ac3d-48a5-b4f9-a51d96e95dca | VM.CREATE | Started | starting Vm. Vm Id: 10 |
> | 175 | dde1bff2-5f68-43a9-a090-10718c3a14f3 | VM.CREATE | Completed | Successfully completed starting Vm. Vm Id: 10 |
> | 180 | 9102d743-3b96-4611-93ab-1fa722170e90 | VM.CREATE | Created | Successfully created entity for deploying Vm. Vm Id: 12 |
> | 181 | fd01696d-4f6d-453c-a43c-81ef7e796579 | VM.CREATE | Scheduled | starting Vm. Vm Id: 12 |
> | 182 | 3173d69e-b39e-450b-abcb-e3568e86b647 | VM.CREATE | Started | starting Vm. Vm Id: 12 |
> | 183 | a919515f-3888-4bd5-8a2a-fc241554c263 | VM.CREATE | Completed | Successfully completed starting Vm. Vm Id: 12 |
> | 200 | b1e7c6a3-3885-4a1f-a3a3-d0683cab2070 | VM.CREATE | Created | Successfully created entity for deploying Vm. Vm Id: 13 |
> | 201 | 0f0680a9-07c9-4321-a5f9-05e781c75be0 | VM.CREATE | Scheduled | starting Vm. Vm Id: 13 |
> | 202 | 8a5c90de-312f-4a00-be4e-249505886bd3 | VM.CREATE | Started | starting Vm. Vm Id: 13 |
> | 203 | 281b30fa-ed89-439c-b7bd-63361e23c07e | VM.CREATE | Completed | Successfully completed starting Vm. Vm Id: 13 |
> | 184 | 1b180a44-3aff-44bc-88bb-2ca261b122e8 | VOLUME.CREATE | Created | Successfully created entity for creating volume. Volume Id: 14 |
> | 185 | b7268c3a-7154-48f6-ac49-452edd7cbd56 | VOLUME.CREATE | Scheduled | creating volume: Data-10 |
> | 186 | 5dba7765-3eb0-4d0f-8c8f-e4b6b878e992 | VOLUME.CREATE | Started | creating volume. Volume Id: 14 |
> | 187 | 3146b2c9-c573-4398-9ba0-d477dd4bfe01 | VOLUME.CREATE | Completed | Successfully completed creating volume. Volume Id: 14 |
> +-----+--------------------------------------+-----------------+-----------+--------------------------------------------------------------------------------+
> 29 rows in set (0.00 sec)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)