This could well be one of: https://bugzilla.redhat.com/show_bug.cgi?id=1429823 https://bugzilla.redhat.com/show_bug.cgi?id=1415112 https://bugzilla.redhat.com/show_bug.cgi?id=1440977 We need to know the original router image that was being run, and the new one.
@Ben Customer was using the following image: openshift3/ose-haproxy-router:v3.5.5.31.36 I did a pull on in on my local system: ┌─[jfoots@whiterun]─[~] └──> sudo docker pull openshift3/ose-haproxy-router:v3.5.5.31.36 sha256:26b66baa0d8192424e434a085d0f4dbada687e76191064553d1c01cd0a047f94: Pulling from registry.access.redhat.com/openshift3/ose-haproxy-router 26e5ed6899db: Pull complete 66dbe984a319: Pull complete d6be7b2600cc: Pull complete feb3f7332a97: Pull complete cc7568c9d8e3: Pull complete Digest: sha256:26b66baa0d8192424e434a085d0f4dbada687e76191064553d1c01cd0a047f94 Status: Downloaded newer image for registry.access.redhat.com/openshift3/ose-haproxy-router:v3.5.5.31.36 ┌─[jfoots@whiterun]─[~] └──> sudo docker images |grep haproxy registry.access.redhat.com/openshift3/ose-haproxy-router v3.5.5.31.36 ff115e0e90ee 7 months ago 748 MB
I'm closing this since I'm certain it was one of the above bugs... it's not worth chasing down which.