The readiness and liveness probes don't support authentication - the health check, even if stats are enabled, should not require authorization.
On Wed, Feb 17, 2016 at 3:16 PM, Rishi Misra <[email protected]> wrote: > Thanks Ram - I was able to get around it using by removing Liveness and > Readiness probe entries from router dc. However, I'd like to know why http > probes are not working. It seems like username/password are not being > passed in the request. Router config does have these entries defined: > > - name: STATS_PASSWORD > value: xxxxxx > - name: STATS_PORT > value: "1936" > - name: STATS_USERNAME > value: admin > > I also see that router pod does have username/password defined in > haproxy.config. So it must be the probe itself which is failing to pass > the credentials. Let me know how I can debug this further. > > Thanks. > > On Fri, Jan 8, 2016 at 4:17 PM, Ram Ranganathan <[email protected]> > wrote: > >> Well, not really recommended on a live/prod system. >> >> But on a test system, one approach would be to create the router as you >> did and then edit the router DC (oc edit dc router) and disable the >> Liveness and Readiness probes (comment with # the relevant sections in the >> yaml or delete the bits in json) and wait for the router to come up. >> >> And you can then adjust your firewall rules to see if you can connect to >> the healthz and router ports (1936, 80, 443) using curl ala: >> curl -vvv http://127.0.0.1:1936/healthz # or use: curl -I -H >> "Host: foo.test" http://127.0.0.1:80/ - you should get back a 503 from >> the router >> >> HTH, >> >> Ram// >> >> On Fri, Jan 8, 2016 at 7:10 AM, Rishi Misra <[email protected]> >> wrote: >> >>> Hello, >>> >>> For some reason router pod fails to start. It appears to be connection >>> related but I can't seem to figure out what would cause it. I have >>> disabled firewall on my system but continue to get this error. Any >>> pointers greatly appreciated: >>> >>> 9:30:41 AM >>> Pod >>> router-1-gvp03 >>> Unhealthy >>> Readiness probe failed: Get http://x.xx.xxx.xx:1936/healthz: dial tcp >>> x.xx.xxx.xx:1936: getsockopt: connection refused >>> Log entries correspond to: >>> >>> I0108 09:30:41.773611 48315 prober.go:183] HTTP-Probe Host: http:// >>> x.xx.xxx.xx, Port: 1936, Path: /healthz >>> I0108 09:30:41.773781 48315 prober.go:183] HTTP-Probe Host: http:// >>> x.xx.xxx.xx, Port: 1936, Path: /healthz >>> I0108 09:30:41.773892 48315 prober.go:183] HTTP-Probe Host: http:// >>> x.xx.xxx.xx, Port: 1936, Path: /healthz >>> I0108 09:30:41.774025 48315 prober.go:139] Readiness probe for >>> "router-1-gvp03_test:router" failed (failure): Get >>> http://x.xx.xxx.xx:1936/healthz: >>> dial tcp x.xx.xxx.xx:1936: getsockopt: connection refused >>> I0108 09:30:41.774314 48315 server.go:734] >>> Event(api.ObjectReference{Kind:"Pod", Namespace:"test", >>> Name:"router-1-gvp03", UID:"5f3265d4-b614-11e5-9574-02000000002e", >>> APIVersion:"v1", ResourceVersion:"744", >>> FieldPath:"spec.containers{router}"}): reason: 'Unhealthy' Readiness probe >>> failed: Get http://x.xx.xxx.xx:1936/healthz: dial tcp x.xx.xxx.xx:1936: >>> getsockopt: connection refused >>> >>> Thanks. >>> >>> _______________________________________________ >>> dev mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>> >>> >> >> >> -- >> Ram// >> main(O,s){s=--O;10<putchar(3^O?97-(15&7183>>4*s)*(O++?-1:1):10)&&\ >> main(++O,s++);} >> > > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
