On 06/02/2015 12:32 AM, Ian Wells wrote:
The fix should work fine. It is technically a workaround for the way
checksums work in virtualised systems, and the unfortunate fact that
some DHCP clients check checksums on packets where the hardware has
checksum offload enabled. (This doesn't work due
Ooook, fully understood now. Thanks Ihar & Ian for the clarification :)
Miguel Ángel Ajo
On Tuesday, 2 de June de 2015 at 13:33, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 06/02/2015 10:10 AM, Miguel Ángel Ajo wrote:
> > The backport seems reasonable IM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/02/2015 10:10 AM, Miguel Ángel Ajo wrote:
> The backport seems reasonable IMO.
>
> Is this tested in a multihost environment?.
>
> I ask, because given the Ian explanation (which probably I got
> wrong), the issue is in the NET->NIC->VM path
nvolve an iptables rule.
> > >
> > > -Ryan
> > >
> > > -----Original Message-
> > > From: Mark McClain [mailto:m...@mcclain.xyz]
> > > Sent: Monday, June 01, 2015 6:47 PM
> > > To: OpenStack Development Mailing List (not for
#x27;t involve an iptables rule.
>>
>> -Ryan
>>
>> -Original Message-
>> From: Mark McClain [mailto:m...@mcclain.xyz]
>> Sent: Monday, June 01, 2015 6:47 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re:
an
>
> -Original Message-
> From: Mark McClain [mailto:m...@mcclain.xyz]
> Sent: Monday, June 01, 2015 6:47 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] virtual machine can not get DHCP
> lease due packe
others might be looking into
that didn't involve an iptables rule.
-Ryan
-Original Message-
From: Mark McClain [mailto:m...@mcclain.xyz]
Sent: Monday, June 01, 2015 6:47 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] virtual
> On Jun 1, 2015, at 7:26 PM, Tidwell, Ryan wrote:
>
> I see a fix for https://bugs.launchpad.net/neutron/+bug/1244589 merged during
> Kilo. I'm wondering if we think we have identified a root cause and have
> merged an appropriate long-term fix, or if
> https://review.openstack.org/148718 w
I see a fix for https://bugs.launchpad.net/neutron/+bug/1244589 merged during
Kilo. I'm wondering if we think we have identified a root cause and have
merged an appropriate long-term fix, or if https://review.openstack.org/148718
was merged just so there's at least a fix available while we inve
