Red Hat Bugzilla – Bug 1468396
Routes stop working after new deployment
Last modified: 2017-07-20 19:42:05 EDT
Description of problem: Deployment is started with the following commands oc project <project> oc start-build <build> -n <name> After the build is complete a new deployment starts, once the deployment finishes I can no longer access the route until I restart Docker on the master node. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Follow the above steps 2. Try to access the route before restarting Docker 3. Actual results: Can not access routes Expected results: For routes to be accessible Additional info:
Please get logs from the router pod. Use command 'oc logs..'! It may be required to run the router with more verbosity on logs. See this article to re-deploy the router with say --loglevel=5: https://access.redhat.com/solutions/2801701
I suspect this is solved by the second fix in https://bugzilla.redhat.com/show_bug.cgi?id=1464567 Can they try updating to the latest 3.4 errata (or just update to the latest 3.4 router image) and re-test please. If that does not fix it, then we would need the logs at the elevated loglevel as @rchopra requested.
Ben, That resolved the issue. I'm closing this bug.