[Openstack-operators] hostname on vms not correct until reboot
Alex Leonhardt
aleonhardt.py at gmail.com
Sat Sep 13 15:05:27 UTC 2014
Hi abel,
good point! checked it and you're right! there are actually another 2
services that come up before cloud-init (i just assumed it's the next
service after network init no matter what) ... thanks for the pointer! :)
alex
On 10 September 2014 23:27, Abel Lopez <alopgeek at gmail.com> wrote:
> 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 <aleonhardt.py at gmail.com>
> wrote:
>
> 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" <alopgeek at gmail.com> wrote:
>
>> 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>
>>> 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/20140913/0227bea1/attachment.html>
More information about the OpenStack-operators
mailing list