> Steps to reproduce: > 1. openstack comupte service --down --disable host1.openstack.example.com > nova-compute > 2. openstack server evacute vm-1
Was the "host1" completely disconnected from network when executing the evacuate action (i.e. completely shut off)? I think that's the assumption of the evacuation in OpenStack. Otherwise, there is a risk of in-parallel operations from two hypervisors at the same time and it leads to data corruption, etc. ** Project changed: cinder => cinder (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2126799 Title: VM evacuation cause corruption on VM staying on the host To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder-purestorage/+bug/2126799/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
