we are seeing the same problem with 3.15.0-6 #11 kernel (we used an
utopic ami and added our bosh stemcell bits to it). Does that kernel
include the fix listed above?
Sorry it took so long to get this up and running our environment.
We do *not* see the problem in a precise system (3.2.0-64 #97)
That commit does not appear to have fixed our problem.
we took the 3.13.0-29 #53 kernel source, applied the patch above, and
deployed to our environment. We are seeing the same behavior with this
patch.
We are currently setting up a parallel test environment, as well as
building a precise image a
Thanks for the quick response and offers of help to test. We have a
workaround in-flight that we are focusing on, so someone from our org
may pick up testing and merging the 3.13 + fix kernel tomorrow (at the
earliest).
Thanks again.
--
You received this bug notification because you are a member
It may take a day or so to integrate a 3.15 kernel into our ami - we'll
have to modify our build process [0], then deploy it into one of the
environments that is exhibiting the problem.
We will start on that track later today - please let us know if you need
any additional info.
[0] https://gith
vcap@34fd733b-3ec0-4f6f-bdf7-24ab74b89b37:~$ cat /proc/version_signature
Ubuntu 3.13.0-24.47-generic 3.13.9
vcap@34fd733b-3ec0-4f6f-bdf7-24ab74b89b37:~$ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04
vcap@34fd733b-3ec0-4f6f-bdf7-24ab74b89b37:~$
--
You received this bug not
Public bug reported:
in an AWS environment managed by BOSH, we saw tcp connectivity problems
between pairs of VMs.
VM A and VM B are up, running ubuntu 14.04-based images, and in the same
vpc subnet.
VM B is terminated, and another VM is created that uses the IP address
from VM B
The new VM tri
