Andreas Kupries

This sounds similar to the #928. Same pod (`asactors-0`), also around DNS. There was a fix around the beginning of June. @satadruroy Do you have instructions on how to repro...

# Attempt 1 - minikube - deployed with auto-scaler - after everything is green - using a loop to kill uaa-0 pod, and keep it down. - kill all the...

@satadruroy Can you add a more detailed set of instructions on how to set up a cluster showing the trouble ? From the ground up, which ever provider, kubecf version,...

Per > we made setting up DNS as a pre-requisite for deploying autoscaler (via helm upgrade once you've deployed KubeCF and set up DNS) this ticket is out of date....

Looking into local reproduction. - minikube (Higher than normal memory: 25G). - Kubecf current head (commit 0e63aa6559b42f996041e8335f8d675d5e35dfe7). - Deployed with `sizing.diego_cell.instances: 2`. - Using `stern` to capture all the logs...

Failed to reproduce using: - minikube v1.9.2 on "Opensuse-Leap" "15.1" - kubernetes 1.17.5 (kubectl 1.15.10) - KubeCF 2.5.0 Staging is ok, App (`goenv`) starts. App is accesible, i.e working. It...

`./uaa/uaa/jobs/patch_uaa.sh` is gone. UAA 74.12.0 = https://github.com/cloudfoundry/uaa-release/commit/2c0703096a0008110615083b48416acc397ab8e3

PR = https://github.com/cloudfoundry/uaa-release/pull/197

Based on https://github.com/cloudfoundry-incubator/kubecf/issues/520#issuecomment-648407686 Since this is filed upstream now, will close. Will track the upstream PR so hopefully, when it's done, we can somehow track it to what we need...

Proposed fix https://github.com/cloudfoundry/gosigar/pull/50