Not sure, but this does look like a networking issue On Fri, May 20, 2016 at 4:59 PM, Skarbek, John <[email protected]> wrote: > Anyone got any tips on troubleshooting this: > > In the events log: > > Deployment Config Warning Failed update Error updating deployment > default/router-14 status to Pending > > And in the log from the deployer pod: > > oc logs router-14-deploy > I0520 20:55:31.651525 1 deployer.go:201] Deploying from > default/router-10 to default/router-14 (replicas: 3) > I0520 20:55:32.769105 1 rolling.go:228] RollingUpdater: Continuing > update with existing controller router-14. > I0520 20:55:32.769140 1 rolling.go:228] RollingUpdater: Scaling up > router-14 from 0 to 3, scaling down router-10 from 3 to 0 (keep 2 pods > available, don't exceed 3 pods) > I0520 20:55:33.808723 1 rolling.go:228] RollingUpdater: Scaling > router-10 down to 2 > I0520 20:55:35.916581 1 rolling.go:228] RollingUpdater: Scaling > router-14 up to 1 > F0520 20:55:43.260379 1 deployer.go:69] Get > https://172.30.0.1:443/api/v1/namespaces/default/pods?labelSelector=deployment%3Drouter-10%2Cdeploymentconfig%3Drouter%2Crouter%3Dtrue: > read tcp 172.30.0.1:443: connection reset by peer > > I find it hard to believe he had a problem talking to kubernetes. I’m able > to deploy other things without issues. This problems appears to be very > sporadic, but enough to annoy me. > > > > -- > John Skarbek > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
