You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Alessandro Caviglione <c....@gmail.com> on 2018/09/20 15:39:22 UTC
VR DHCP issue
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??
Re: VR DHCP issue
Posted by Rohit Yadav <ro...@shapeblue.com>.
Restart the network with cleanup=true, check if the new VR has the necessary dhcp settings?
- Rohit
<https://cloudstack.apache.org>
________________________________
From: Alessandro Caviglione <c....@gmail.com>
Sent: Monday, October 1, 2018 4:32:41 PM
To: users@cloudstack.apache.org
Subject: Re: VR DHCP issue
Hi,
on VR I do not have any /etc/dhcphosts.txt
/etc/cloudstack/dhcpentry.json contains DHCP entry but /var/log/cloud.log
stops at last VR startup... no DHCP entry... and I still have DHCP issue! :(
On Thu, Sep 27, 2018 at 11:45 AM Andrei Mikhailovsky
<an...@arhont.com.invalid> wrote:
> Hi Marcelo,
>
> could you please elaborate on the fix please? I am having this issue with
> a couple of my VRs (not all).
>
> Running /etc/init.d/cloud-early-config start doesn't work as there is no
> such script in the init.d directory. Running service cloud-early-config
> start doesn't fix the DHCP issue.
>
> Thanks
>
>
rohit.yadav@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
----- Original Message -----
> > From: "Lotic Lists" <li...@lotic.com.br>
> > To: "users" <us...@cloudstack.apache.org>
> > 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
> >
> > -----Original Message-----
> > From: Ivan Kudryavtsev <ku...@bw-sw.com>
> > Sent: quinta-feira, 20 de setembro de 2018 13:46
> > To: users <us...@cloudstack.apache.org>
> > 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 <Da...@shapeblue.com>:
> >
> >> 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....@gmail.com>
> >> 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@shapeblue.com
> >> www.shapeblue.com<http://www.shapeblue.com>
> >> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
> >>
> >>
> >>
>
Re: VR DHCP issue
Posted by Alessandro Caviglione <c....@gmail.com>.
Hi,
on VR I do not have any /etc/dhcphosts.txt
/etc/cloudstack/dhcpentry.json contains DHCP entry but /var/log/cloud.log
stops at last VR startup... no DHCP entry... and I still have DHCP issue! :(
On Thu, Sep 27, 2018 at 11:45 AM Andrei Mikhailovsky
<an...@arhont.com.invalid> wrote:
> Hi Marcelo,
>
> could you please elaborate on the fix please? I am having this issue with
> a couple of my VRs (not all).
>
> Running /etc/init.d/cloud-early-config start doesn't work as there is no
> such script in the init.d directory. Running service cloud-early-config
> start doesn't fix the DHCP issue.
>
> Thanks
>
> ----- Original Message -----
> > From: "Lotic Lists" <li...@lotic.com.br>
> > To: "users" <us...@cloudstack.apache.org>
> > 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
> >
> > -----Original Message-----
> > From: Ivan Kudryavtsev <ku...@bw-sw.com>
> > Sent: quinta-feira, 20 de setembro de 2018 13:46
> > To: users <us...@cloudstack.apache.org>
> > 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 <Da...@shapeblue.com>:
> >
> >> 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....@gmail.com>
> >> 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@shapeblue.com
> >> www.shapeblue.com
> >> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
> >>
> >>
> >>
>
Re: VR DHCP issue
Posted by Andrei Mikhailovsky <an...@arhont.com.INVALID>.
Hi Marcelo,
could you please elaborate on the fix please? I am having this issue with a couple of my VRs (not all).
Running /etc/init.d/cloud-early-config start doesn't work as there is no such script in the init.d directory. Running service cloud-early-config start doesn't fix the DHCP issue.
Thanks
----- Original Message -----
> From: "Lotic Lists" <li...@lotic.com.br>
> To: "users" <us...@cloudstack.apache.org>
> 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
>
> -----Original Message-----
> From: Ivan Kudryavtsev <ku...@bw-sw.com>
> Sent: quinta-feira, 20 de setembro de 2018 13:46
> To: users <us...@cloudstack.apache.org>
> 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 <Da...@shapeblue.com>:
>
>> 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....@gmail.com>
>> 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@shapeblue.com
>> www.shapeblue.com
>> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
>>
>>
>>
RE: VR DHCP issue
Posted by Lotic Lists <li...@lotic.com.br>.
Workaround is run "/etc/init.d/cloud-early-config start"
Att.
Marcelo
-----Original Message-----
From: Ivan Kudryavtsev <ku...@bw-sw.com>
Sent: quinta-feira, 20 de setembro de 2018 13:46
To: users <us...@cloudstack.apache.org>
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 <Da...@shapeblue.com>:
> 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....@gmail.com>
> 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@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
>
>
>
>
Re: VR DHCP issue
Posted by Ivan Kudryavtsev <ku...@bw-sw.com>.
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 <Da...@shapeblue.com>:
> 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....@gmail.com>
> 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@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London WC2E 9DPUK
> @shapeblue
>
>
>
>
Re: VR DHCP issue
Posted by Dag Sonstebo <Da...@shapeblue.com>.
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....@gmail.com> 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@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue