[openstack-dev] [nova] Recovering from Instance from a failed 'resize' Operation
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/_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
Re: [openstack-dev] [neutron][dvr]
Ok. Thanks for the response Swami. Filed a defect [1] for tracking this.. [1] https://bugs.launchpad.net/neutron/+bug/1539387 Thanks, Sudhakar. On Thu, Jan 28, 2016 at 10:34 PM, Vasudevan, Swaminathan (PNB Roseville) < swaminathan.vasude...@hpe.com> wrote: > Hi Sudhakar, > > I don’t think there was any specific reason behind this. > > But we can definitely check for the config flag and then add the topic > ‘dvr_update’. > > Go ahead and file a bug and we can address it. > > > > Thanks > > Swami > > > > *From:* Sudhakar Gariganti [mailto:sudhakar.gariga...@gmail.com] > *Sent:* Wednesday, January 27, 2016 10:00 PM > *To:* openstack-dev@lists.openstack.org > *Subject:* [openstack-dev][neutron][dvr] > > > > Hi all, > > > > One basic question related to DVR topic '*dvr_update'*. In OVS Neutron > agent, I see that the *dvr_update* topic is being added to the consumer > list irrespective of DVR being enabled or not. Because of this, even though > I have disabled DVR in my environment, I still see the agent subscribe and > listen on dvr_update topic. > > > > Is there any reason for enabling the DVR topic by default, unlike l2_pop > which makes the agent subscribe to the l2_pop topic only when l2_pop is > enabled?? > > > > 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
[openstack-dev] [neutron][dvr]
Hi all, One basic question related to DVR topic '*dvr_update'*. In OVS Neutron agent, I see that the *dvr_update* topic is being added to the consumer list irrespective of DVR being enabled or not. Because of this, even though I have disabled DVR in my environment, I still see the agent subscribe and listen on dvr_update topic. Is there any reason for enabling the DVR topic by default, unlike l2_pop which makes the agent subscribe to the l2_pop topic only when l2_pop is enabled?? 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
