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 subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/18 11:05:09 UTC
[jira] [Commented] (CLOUDSTACK-5458) cpu speed is not getting
updated in vm_instance table after service offeirngs change
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851542#comment-13851542 ]
ASF subversion and git services commented on CLOUDSTACK-5458:
-------------------------------------------------------------
Commit efe2549e7a364d9c1c5f5fedfbb75c38ee2b0e63 in branch refs/heads/4.3 from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=efe2549 ]
CLOUDSTACK-5458: cpu speed is not getting updated in vm_instance table after service offeirngs change
Removed cpu, ram and cpu speed fields from the vm_instance table as these are not used
> cpu speed is not getting updated in vm_instance table after service offeirngs change
> ------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5458
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5458
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Reporter: prashant kumar mishra
> Assignee: Koushik Das
> Attachments: Logs_db_xenlogs.rar
>
>
> Steps to repro
> -------------------
> 1-prepare Cs setup with xen(6.2)
> 2-deploy a vm with small SO
> 3- stop vm
> 4-change vm SO from small to medium
> 5-start vm
> 6-wait for capacity.check.period interval
> 7-check speed in vm_instance table
> Expected:
> --------------
> speed should get updated in vm_instance table
> Actual
> ---------
> speed value is not getting updated in vm_instance table
>
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)