openstack team mailing list archive

[Vishvananda Ishaya <vishvananda@xxxxxxxxx>]

Generally the easiest is to give the new machine the same hostname.

You can also update the references to the host in the db:

update networks set host=newhostname where host=oldhostname

Vish

On Jul 22, 2011, at 12:39 PM, Leandro Reox wrote:

> Hi all, 
> 
> Being working on controller/network node HA for a time know, but at this point im having an issue that maybe someone has faced before . 
> When i switch the controller to an "spare" one, the computes nodes still searching for "network.$oldcontrollerhostname" . Is there a place where the hostname on the controller is stored ? maybe a field on the database ? . The instances stucks in "networking" status
> 
> The entry on the nova-compute.log from the compute that is trying to spawn the instance is clear : 
> 
> DEBUG nova.rpc [-] Making asynchronous call on network.controller1 ... from (pid=4440) call /usr/lib/pymodules/python2.6/nova/rpc.py:350
> 
> Where "controller1" is the OLD controller/network node 
> 
> Any clues ?
> 
> Regards
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp