[Openstack-operators] hostname on vms not correct until reboot
Abel Lopez
alopgeek at gmail.com
Mon Sep 8 15:20:56 UTC 2014
Yes. I think this is similar to changing hostname on an interactive shell,
you won't see your prompt change until you logout/in. Seems to be a new
feature, maybe something in cloud-init 0.7.5? IIRC it used to be correct at
first login.
On Monday, September 8, 2014, Alex Leonhardt <aleonhardt.py at gmail.com>
wrote:
> HI all,
>
> did anyone have the same problem ?
>
> Alex
>
> On 3 September 2014 13:57, Alex Leonhardt <aleonhardt.py at gmail.com
> <javascript:_e(%7B%7D,'cvml','aleonhardt.py at gmail.com');>> wrote:
>
>> Hi,
>>
>> I'm using openstack together with puppet and mcollective (VM images is
>> pre-provisoined) but when a new VM is being spun up, it seems that the host
>> is being wrongly identified as host-i-p-g-o-e-s-h-e-r-e instead of its
>> actual hostname that was set by cloud-init / puppet ?
>>
>> Am sure there is a trick to make this work properly ?
>>
>> Note that after I reboot the VM (no changes made) the host comes up with
>> the correct name in mcollective. Am just wondering if there is something I
>> forgot to set in cloud-init or if someone had the same issue and knows a
>> proper fix (not rebooting) ?
>>
>>
>> Thanks
>> Alex
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140908/0beeaf73/attachment.html>
More information about the OpenStack-operators
mailing list