[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283503#comment-14283503
 ] 

ASF subversion and git services commented on CLOUDSTACK-4201:
-------------------------------------------------------------

Commit a6f9411b1eb46739c9b47fc16ad7796cc0e3d221 in cloudstack's branch 
refs/heads/4.5 from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a6f9411 ]

CLOUDSTACK-7771: Throw exception while restoring vm if the template is already 
deleted. Also fix the usage event being generated from the right template id 
and fix the log message which sometime showed incorrect template id.
CLOUDSTACK-4201: listServiceOfferings API needs to be able to take 
virtualmachineid of SystemVM and return service offerings available for the vm 
to change service offering

(cherry picked from commit ee0f0a1cffb96a8371d9a8c4210b428660f79d4f)
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>


> listServiceOfferings API needs to be able to take virtualmachineid of 
> SystemVM and return service offerings available for the vm to change service 
> offering
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4201
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4201
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: listServiceOfferings API needs to be able to take 
> virtualmachineid of SystemVM and returns service offerings available for the 
> vm to change service offering. If vm is running only scale up service 
> offering should be presented. If vm is stopped all service offering should be 
> shown.
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>             Fix For: 4.6.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to