[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=14215908#comment-14215908
]
ASF subversion and git services commented on CLOUDSTACK-7767:
-
Commit c04cdae60bc9a10f584c2f0b591aa5a5d9c7e3e4 in cloudstack's branch
refs/heads/4.5 from [~anshulg]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c04cdae ]
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
[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=14191342#comment-14191342
]
ASF GitHub Bot commented on CLOUDSTACK-7767:
Github user anshul1886 commented on the pull request:
https://github.com/apache/cloudstack/pull/27#issuecomment-61217217
Yes, this should go to 4.5 as well. Somebody can cherry-pick this to 4.5.
> [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
>
[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=14190010#comment-14190010
]
ASF GitHub Bot commented on CLOUDSTACK-7767:
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack/pull/27#issuecomment-61086586
shouldnt this go in 4.5 as well?
> [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-a51d96
[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=14189859#comment-14189859
]
ASF subversion and git services commented on CLOUDSTACK-7767:
-
Commit 448bb797404c9578256a7d9cdac8b3c4e1560276 in cloudstack's branch
refs/heads/master from [~rohit.ya...@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=448bb79 ]
PR #27 CLOUDSTACK-7767
Fixed events are not generated for snapshot creation #27
This closes #27
> [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-60652089
[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=14189861#comment-14189861
]
ASF GitHub Bot commented on CLOUDSTACK-7767:
Github user bhaisaab commented on the pull request:
https://github.com/apache/cloudstack/pull/27#issuecomment-61066104
Thanks, merging since CI build passed.
> [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-
[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=14189862#comment-14189862
]
ASF GitHub Bot commented on CLOUDSTACK-7767:
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/27
> [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
[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=14189858#comment-14189858
]
ASF subversion and git services commented on CLOUDSTACK-7767:
-
Commit d8b46b81b946672ab6836f13ea0389cee63321d8 in cloudstack's branch
refs/heads/master from [~anshulg]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d8b46b8 ]
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 |
> starti
[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
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 |
> sta
