I don't know if it is related to this hostname issue, but my nova-compute
on cloudcontroller can't initiate an iscsi volume in the same controller.
2012-12-14 14:13:46 DEBUG nova.utils
[req-98c1f3b8-ac10-4aa6-a806-f2dd18928af2 None None] Result was 255 from
(pid=5250) execute /usr/lib/python2.7/di
Razique, thanks for the tip.
To find out which tables has the hostname set I did this:
# for i in `mysql -uroot -p'PASSWORD' -e 'show tables;' nova | grep -v -e
'+' -e 'T'`; do echo $i && mysql -uroot -p'PASSWORD' -e "select * from
$i";' nova | grep OLD_HOSTNAME; done
This will print many data with
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 & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15
Le 14 déc. 2012 à 15:43
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=old
4 matches
Mail list logo