Uh oh!
There was an error while loading. Please reload this page.
CLOUDSTACK-8964: Ovm3HypervisorGuru handle only srcData with HypervisorType is Ovm3 - #1177
Conversation
dc01fca to
a90b953Compareustcweizhou
commented
Dec 4, 2015
The diff between this PR and last commit (before 4.6) |
remibergsma
commented
Dec 4, 2015
Pinging @snuf to have a look. |
remibergsma
commented
Dec 6, 2015
LGTM based on these tests: Result: And: Result: I didn't test the actual feature. This just shows it didn't break anything else. |
DaanHoogland
commented
Dec 6, 2015
lgtm, merging |
CLOUDSTACK-8964: Ovm3HypervisorGuru handle only srcData with HypervisorType is Ovm3This PR can only be applied after PR #1176 The CopyCommand on Ovm3 should be handled by Ovm3StorageProcessor, not SSVM. Hence, I revert two commits on Ovm3HypervisorGuru, and add the hypervisorType check so that only the this guru will only handle Ovm3 (not KVM) * pr/1177: CLOUDSTACK-8964: Ovm3HypervisorGuru handle only srcData with HypervisorType is Ovm3 Revert "simple change to prevent failure and keep OVM3 snapshots working" Revert "CLOUDSTACK-8964 side effect isolation" Signed-off-by: Daan Hoogland <daan@onecht.net>
snuf
commented
Dec 7, 2015
Seems like we have the same problem in the XenServer code, as I stated earlier in another pull request somewhere out there, where this code originates from (XenServerGuru.java) . The place it's been done correctly is the VmwareGuru.java it seems, they actually check the hypervisor type, opposed to the XenServerGuru.java. So yes it's a fix, but it doesn't fix other places where the same logic has been applied in the past. |
ustcweizhou
commented
Dec 7, 2015
@snuf We should make sure these three files handle the corresponding hypervisor type (eg XenserverGuru only handle xenserver). This is why @anshulgangwar made in #1176 and I made in this PR #1177, we added the check on srcData.getHypervisorTyp. We think the issue is fixed on Xenserver and Ovm3. I tested creating a template from snapshot on KVM, the command CopyCommand is handled by ssvm, it works. |
This PR can only be applied after PR #1176
The CopyCommand on Ovm3 should be handled by Ovm3StorageProcessor, not SSVM.
Hence, I revert two commits on Ovm3HypervisorGuru, and add the hypervisorType check so that only the this guru will only handle Ovm3 (not KVM)