[
https://issues.apache.org/jira/browse/CLOUDSTACK-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar resolved CLOUDSTACK-7763.
--------------------------------------
Resolution: Fixed
> Reservations for VMware VMs remain after dynamic scaling completes
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-7763
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7763
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.5.0
> Reporter: Bharat Kumar
> Assignee: Bharat Kumar
> Fix For: 4.5.0
>
>
> When using the dynamic scaling feature for VMware VMs, a reservation is
> configured on the VM, however it is not removed once the scaling completes
> successfully. This is happening even though vmware.reserve.cpu/mem parameters
> are false for the cluster and in Global Settings. The reservation is removed
> if you subsequently stop/start the VM.
> REPRO STEPS
> ==================
> 1) Deploy a VM from a dynamically scalable template.
> 2) When it is up and running, notice the lack of any configured reservations.
> 3) Scale up the VM by changing to a Compute Offering with more CPU/RAM.
> 4) After it succeeds, notice the reservations are still applied.
> 5) Stop and start the VM.
> 6) Notice that the reservations have been removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
