DaanHoogland commented on PR #7878: URL: https://github.com/apache/cloudstack/pull/7878#issuecomment-1685826549
> Perhaps useful for someone using VMware, where there is a separate system to manage VMs independently. I don't know that a test via KVM is going to really exercise it in the same way the VMware integration does. > > Worst case, we see an event for VMware users indicating the VM was removed from its host out of band, but we aren't making a change to how the VM state is handled and synced up for these kinds of migrations. A scenario we have seen (which is purely a billing issue but still) Is that a VM was at a certain moment powered off and hence absent in reports from both hosts, while migration was still going on. This led to billing issues as those are a bit fragile. it relies a bit too much on a proper order of events and matching on/off create/delete etc combinations of events. What I am missing in this PR is the start event (also for OOB). We will have to test this and I think you are right this will probably only be an issue on vmware (not sure about xen). @borisstoyanov (@vladimirpetrov) I think we need to give an extra eye to testing this. > 1. The fix to this is probably to properly detect the migrating scenario and change the VM state to `Migrating`, but outside of the scope of this PR. agreed -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
