[
https://issues.apache.org/jira/browse/CLOUDSTACK-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-5268:
----------------------------------------
Assignee: Alena Prokharchyk (was: Jessica Wang)
This is caused by an API regression.
listCapabilities API used to return "KVMsnapshotenabled" property, but not any
more.
http://10.223.49.195:8080/client/api?command=listCapabilities&response=json&sessionkey=JaYnM2xp3HIR3IfB0i%2BKCE0s1C8%3D&_=1386366600376
{
"listcapabilitiesresponse": {
"capability": {
"securitygroupsenabled": false,
"cloudstackversion": "4.3.0-SNAPSHOT",
"userpublictemplateenabled": true,
"supportELB": "false",
"projectinviterequired": false,
"allowusercreateprojects": true,
"customdiskofferingmaxsize": 1024,
"regionsecondaryenabled": false
}
}
}
Jessica
> [Automation] [UI]There is no option to create snapshot from volume of running
> vm
> ---------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5268
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.3.0
> Environment: KVM
> Branch 4.3
> Reporter: Rayees Namathponnan
> Assignee: Alena Prokharchyk
> Priority: Blocker
> Fix For: 4.3.0
>
>
> Steps to reproduce
> Step 1 : Deploy VM
> Step 2 : Once VM is up, select the root volume
> Step 3 : Create snapshot
> Actual Result
> There is no option to create snapshot from volume; you need to stop vm first
> to create snapshot
--
This message was sent by Atlassian JIRA
(v6.1#6144)