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 wrote:
> That screams of b
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
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
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
wrote:
> HI all
HI all,
did anyone have the same problem ?
Alex
On 3 September 2014 13:57, Alex Leonhardt 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-
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 tr
