Abby / Shannon,

The issue should be tracked publicly for everyone to follow along. Private
customer specifics obviously stay within Pivotal, but the upstream efforts
around this issue should be kept public.

Thanks!

On Tue, Apr 25, 2017 at 3:32 PM Abby Chau <achau(a)pivotal.io> wrote:

Hi Mike,

Apologies that link is for a private Pivotal-only tracker story. Here is
the OSS tracker story
<https://www.pivotaltracker.com/story/show/144313611> which links to that
private story. I don't know how helpful this OSS tracker link is but
hopefully it will provide a mechanism for you to follow along with. Thanks.

Best,

Abby


On Tue, Apr 25, 2017 at 12:19 PM, Abby Chau <achau(a)pivotal.io> wrote:

Hi Mike,

The tracker issue to follow is here
<https://www.pivotaltracker.com/story/show/144128279>. Please do not
hesitate to reach out if you have any questions, thanks.

Best,

Abby


On Tue, Apr 25, 2017 at 11:57 AM, Mike Youngstrom <youngm(a)gmail.com>
wrote:

Thanks Abby,

Is there a tracker issue or something we can follow to get updates as
they are discovered?

Mike

On Mon, Apr 24, 2017 at 3:46 PM, Abby Chau <achau(a)pivotal.io> wrote:

Hi CF Devs,

It was recently discovered that routing release versions 149-151
includes a bug whereby increased latency and 502s can be observed.

If you have deployed cf-release 256 or greater, you should change your
gorouter job(s) to use version 0.147.0 of the cf-routing-release:

releases:
- name: cf
version: 256
- name: routing
version: 0.147.0
...
jobs:
- name: router_z1(z2)
...
templates:
- name: gorouter
release: routing
...


The routing team is currently investigating this issue and we will
provide a patch as soon as possible. Please feel free to reach out if you
have any questions.

Thanks,

Abby

--

Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815