git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: VR DHCP issue


Workaround is run "/etc/init.d/cloud-early-config start"

Att.
Marcelo

-----Original Message-----
From: Ivan Kudryavtsev <kudryavtsev_ia@xxxxxxxxx> 
Sent: quinta-feira, 20 de setembro de 2018 13:46
To: users <users@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: VR DHCP issue

Hello, in the past and in 4.9 too, I have met a bug like that with DHCP:
https://github.com/fgrehm/vagrant-lxc/issues/153

I have to apply that fix in our VRs to make it work always as expected.

чт, 20 сент. 2018 г., 22:52 Dag Sonstebo <Dag.Sonstebo@xxxxxxxxxxxxx>:

> Hi Allessandro,
>
> First of all have you tried to restart the networks "with cleanup"
> (alternatively just destroyed the VRs and let them recreate)?
>
> Can you check the content of the following files on your problem VRs:
>
> /etc/dhcphosts.txt
> /etc/cloudstack/dhcpentry.json
>
> Also look through the VR /var/log/cloud.log for any hints why DHCP 
> entries are not passed or parsed.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 20/09/2018, 16:39, "Alessandro Caviglione" 
> <c.alessandro@xxxxxxxxx>
> wrote:
>
>     Hi guys,
>     I'm experiencing an issue in our CS 4.9.
>     In fact, sonce a week ago, randomly some instances became unreachable.
>     After investigation we see that instances does not have IP address.
>     We tried to restart VR, restart instance, migrate both to another 
> host, but
>     same issue.
>     So we configured the instance with a fixed ip address and it comes back
>     online.
>     We have had this issue on about 15 VR...
>     Any idea??
>
>
>
> Dag.Sonstebo@xxxxxxxxxxxxx
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>