I've updated the document to correct for the omission pointed out by Rich.
On Fri, Oct 7, 2016 at 7:37 AM, Grifalconi, Michael <
Sorry for the long delay but I had to wait to test your suggestion.. and
We still had some issue that needed a restart of some VMs but nothing
compared the issue we faced before.
I strongly suggest to include this step in the update guide you provided.
On 27/09/16 15:22, "Rich Wohlstadter" <lethwin(a)gmail.com> wrote:
We were hitting the same issue. It turned out to be that that the
etcd_proxy (temporarily on etcd_z2) was advertising dns for
cf-etcd.service.cf.internal which caused some of the below services to try
and contact the proxy securely which would fail. What we did is added a
step after you generate the manifest and get ready to deploy the upgrade to
v241, edit and delete the following consul property on your etcd_z2 job
That solved the issue. Once everything is talking to the secure etcd
standalone and you scale back up the generation scripts will add it back in
and your good to go. Hope this helps.