Check the nova database, the network tables and fixed_ip contains the hostname.
Update these fields too and you should be ok :)
(Maybe your /etc/hosts files, keystone endpoints if you used hostnames)

Razique Mahroua - Nuage & Co
Tel : +33 9 72 37 94 15


Le 14 déc. 2012 à 15:43, Gui Maluf <guimal...@gmail.com> a écrit :

Hey guys. I think I did a stupid thing.
My setup is 1 cloudcontroller + node and 2 node with FlatDHCP, mult_host, net HA.

Recently I've changed the hostname of my cloudcontroller; to make things consistent I've updated the services table inside nova db to mark as deleted=1 the lines where host=oldhostname.

I dont know what happened because now nothing of the nova-network works. It doesn't create br100 anymore, neither iptables rules of SNAT and DNAT

The worse thing about that problem, is that this is  production setup. All my instances from the cloudcontroller are unavaible cause of this. Nodes are creating everything regularly

I couldn't found nothing wrong on logs, no errors. Anyway, here are my logs and setup files.

controller nova.conf: http://paste.openstack.org/show/28095/
node nova.conf: http://paste.openstack.org/show/28096/
iptables -L -t nat + brctl show + virsh list: http://paste.openstack.org/show/28098/

Any other information please let me know!
I need to fix this ASAP

--
guilherme \n
\t maluf

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to