[
https://issues.apache.org/jira/browse/CLOUDSTACK-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Tutkowski updated CLOUDSTACK-10099:
----------------------------------------
Attachment: CLOUDSTACK-10099.png
I believe this will solve the problem.
I'm testing this out.
> GUI invokes migrateVirtualMachine instead of migrateVirtualMachineWithVolume
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10099
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10099
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
> Affects Versions: 4.11.0.0
> Environment: All
> Reporter: Mike Tutkowski
> Fix For: 4.11.0.0
>
> Attachments: CLOUDSTACK-10099.png
>
>
> I have a VM whose root disk in on zone-wide, managed storage.
> When I go to migrate the VM to a host in another cluster, the GUI correctly
> points out that to migrate the VM to the desired host that storage migration
> will be required.
> Since I am good with both the VM and its disk being migrated, I initiate the
> action.
> The GUI ends up invoking the migrateVirtualMachine API command instead of the
> migrateVirtualMachineWithVolume API command, which causes the process to
> fail. The process does fail gracefully (nothing seems to be left in a bad
> state).
> If I invoke the migrateVirtualMachineWithVolume API command from CloudMonkey
> and pass in the necessary parameters, the migration is successful.
> I know this used to work from the GUI at some point in 4.10 development
> because I recorded a video demonstrating this feature as executed from the
> GUI:
> https://www.youtube.com/watch?v=_pbnvQxTAqw&t=1006s&list=PLqOXKM0Bt13DFnQnwUx8ZtJzoyDV0Uuye&index=17
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
