sn't fix the DHCP issue.
>
> Thanks
>
>
rohit.ya...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
- Original Message -
> > From: "Lotic Lists"
> > To: "users"
> > Sent: Friday, 21 Septembe
7;t fix the DHCP issue.
>
> Thanks
>
> - Original Message -
> > From: "Lotic Lists"
> > To: "users"
> > Sent: Friday, 21 September, 2018 03:50:12
> > Subject: RE: VR DHCP issue
>
> > Workaround is run "/etc/init.d/cloud-early-config
x the DHCP issue.
Thanks
- Original Message -
> From: "Lotic Lists"
> To: "users"
> Sent: Friday, 21 September, 2018 03:50:12
> Subject: RE: VR DHCP issue
> Workaround is run "/etc/init.d/cloud-early-config start"
>
> Att.
> Marcelo
Workaround is run "/etc/init.d/cloud-early-config start"
Att.
Marcelo
-Original Message-
From: Ivan Kudryavtsev
Sent: quinta-feira, 20 de setembro de 2018 13:46
To: users
Subject: Re: VR DHCP issue
Hello, in the past and in 4.9 too, I have met a bug like that with D
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 :
> Hi Allessandro,
>
> First of all have you tried to restar
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
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 i
