Re: [Openstack-operators] hostname on vms not correct until reboot

2014-09-10 Thread Abel Lopez
That screams of boot order. It sounds like cloud-init needs to start sooner, like immediately after network initialization. Are these home-grown images? On Sep 10, 2014, at 11:52 AM, Alex Leonhardt wrote: > Hi Abel, > > It's actually correct when logging in, but some services, like mcollective

Re: [Openstack-operators] hostname on vms not correct until reboot

2014-09-10 Thread Alex Leonhardt
Hi Abel, It's actually correct when logging in, but some services, like mcollective are reporting the wrong fqdn until we reboot the VM so as a temporary fix we added a reboot at the end of cloud-init. Any better way to get this sorted properly though? Alex On 8 Sep 2014 16:20, "Abel Lopez" wr

[Openstack-operators] some problem with nova

2014-09-10 Thread Ehsan Qarekhani
Hi I have some weird problem with nova-compute . in one of my nodes nova compute refuse to create instance whit this error Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1329, in _build_instance set_access_ip=set_access_ip) Fi