App healthchecks: controller log shows failed to connect to container (Key not found)

[carmstrong]

Healthchecks seemed to work fine once the containers booted, but I thought this read a little odd:

Aug 04 06:34:10 deistest18-coreos-2 sh[22450]: INFO unbent-zaniness: chris scaled containers web=25
Aug 04 06:34:59 deistest18-coreos-2 sh[22450]: WARNING unbent-zaniness: failed to connect to container ('Key not found : /deis/services/unbent-zaniness/unbent-zaniness_v5.web.19'); trying again in 0.5 seconds
Aug 04 06:34:59 deistest18-coreos-2 sh[22450]: WARNING unbent-zaniness: failed to connect to container ('Key not found : /deis/services/unbent-zaniness/unbent-zaniness_v5.web.19'); trying again in 2.5 seconds
Aug 04 06:35:02 deistest18-coreos-2 sh[22450]: WARNING unbent-zaniness: failed to connect to container ('Key not found : /deis/services/unbent-zaniness/unbent-zaniness_v5.web.19'); trying again in 5.0 seconds

This is confusing for the user - perhaps we should say something like "unbent-zaniness_v5.web.19 failed a health check".

[krancour]

perhaps we should say something like "unbent-zaniness_v5.web.19 failed a health check".

👍

[bacongobbler]

This is not something we'll be able to get to for the LTS release (#4776) and the architecture in deis v2 has dramatically changed such that this is no longer relevant so I'm closing this.