somejfn commented on issue #2722: CLOUDSTACK-10310 Fix KVM reboot on storage issue URL: https://github.com/apache/cloudstack/pull/2722#issuecomment-434280872 On problem is while NFS is unavailable, you wont be able to destroy the VM.... libvirt will just hang. So if you attempt to destroy the and start a new VM, when the NFS service comes back online you will get the duplicate VM. That's why I would rather just wait for the NFS issue to go away rather than fire VM-HA in that case. On Tue, Oct 30, 2018 at 5:32 AM Paul Angus <[email protected]> wrote: > IMHO i'd say if a VM on that storage is marked as ha-enabled, it should be > powered-off and restarted somewhere else, and if it isn't HA enabled, we > shouldn't do anything with the running VM (as it's for the user of the VM > to deal with it), > in either case we should probably set the host to 'alert' so then an admin > can see it and do something about it. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/cloudstack/pull/2722#issuecomment-434230839>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AOflqEYelB48SSZ6QeAJYCdjQsQoE014ks5uqBy6gaJpZM4U2Vve> > . >
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
