Hi, We have an Openstack installation based on Kilo *(with KVM compute)*. One of the users tried to resize his instance. The operation failed midway because of an Auth exception from Neutron probably during a port binding update. The instance was actually tried to be rescheduled to a new Host (say B) from parent host (say A).
We see that nova updates the host name proactively to 'B' without a confirmation that the operation succeeded. And since Neutron did not finish the port update, the port is seen to be still bound to Host A. After some code walkthrough/readings, we were able to bring the instance back online by playing around with /var/lib/instances/<instance-id>_resize folder on host A, and then using the virsh utility. How can I update the OS-EXT-SRV-ATTR:host, OS-EXT-SRV-ATTR:hypervisor_ hostname, *OS-EXT-STS:power_state *attributes for the instances, so that I can manage the instance again via horizon/cli? Currently the API calls are directed to host B, because of the DB update. Is it feasible to update at all? or I am too greedy here. Thanks, Sudhakar.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
