I think there was something that I screwed up after I did the advanced install per the documentation. I was also having a bunch of issues with pushing and pulling with the built in docker repository. Thinking that I screwed up something with one of the service accounts, I blew away the environment and redid it from scratch and everything worked fine after that. If I'm able to reproduce the issue, I will definitely file an issue. Thanks.
On Fri, Jul 8, 2016 at 9:29 PM, Clayton Coleman <[email protected]> wrote: > The error message may be incorrect - we probably need to tone it down > because it is not actionable in all cases. Would you please file an issue > regarding this with info about your router? > > On Jul 7, 2016, at 2:47 PM, Tony Saxon <[email protected]> wrote: > > I set up an HA router based on the docs at > https://docs.openshift.org/latest/admin_guide/high_availability.html#admin-guide-high-availability > > Everything seemed to work fine, however when I exposed a deployed example > I get an error message in the status: > > [root@oso-master ~]# oc status -v > In project test on server https://oso-master.libvirt:8443 > > http://deployment-example-test.router.default.svc.cluster.local to pod > port 8080-tcp (svc/deployment-example) > dc/deployment-example deploys istag/deployment-example:latest > deployment #1 deployed 40 hours ago - 1 pod > > Errors: > * route/deployment-example is routing traffic to svc/deployment-example, > but either the administrator has not installed a router or the router is > not selecting this route. > try: oc adm router -h > Warnings: > * dc/deployment-example has no readiness probe to verify pods are ready > to accept traffic or ensure deployment is successful. > try: oc set probe dc/deployment-example --readiness ... > > View details with 'oc describe <resource>/<name>' or list everything with > 'oc get all'. > > > After spending a few hours trying to figure out what the issue was, I > finally just tried to test access to the service from outside through the > HA router that was set up and it seemed to work. Can anyone point me to > where I would look to determine what is actually causing the error? > > _______________________________________________ > 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
