No, i do not even get the 503 page from the haproxy router. I am absolutely stumped.
On Sun, May 29, 2016 at 10:37 PM, Skarbek, John <john.skar...@ca.com> wrote: > Dean, > > Obviously, despite being public, I cannot see this I guess do to > fireballing or security groups, but what is the end resultant behavior? Do > we see a 503 page from the haproxy router? > > > > -- > John Skarbek > > On May 29, 2016 at 23:23:57, Dean Peterson (peterson.d...@gmail.com) > wrote: > > Yes, that works: > > oc get routes > NAME HOST/PORT PATH SERVICE > TERMINATION LABELS > abecornlandingpage landing.enterprisewebservice.com > <https://urldefense.proofpoint.com/v2/url?u=http-3A__landing.enterprisewebservice.com&d=DQMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=5wvPPkum61VcCicru_usEqZ3Ag06IRhmkEdzG2WSaos&s=NU2Dg-TJqCdhpFExLH4JtyKDj3x6b08DoSwGHjp0zt0&e=> > abecornlandingpage:web > template=abecorn-landing-page-template > > > > On Sun, May 29, 2016 at 10:22 PM, Skarbek, John <john.skar...@ca.com> > wrote: > >> That’s weird, that should’ve worked… What about simply oc get routes >> >> >> -- >> John Skarbek >> >> On May 29, 2016 at 23:19:40, Dean Peterson (peterson.d...@gmail.com) >> wrote: >> >> is the command correct? i just get "Error from server: routes >> "–-all-namespaces" not found" >> >> >> On Sun, May 29, 2016 at 10:15 PM, Skarbek, John <john.skar...@ca.com> >> wrote: >> >>> What do we see when we do a: >>> >>> oc get routes –all-namespaces >>> >>> >>> -- >>> John Skarbek >>> >>> On May 29, 2016 at 23:01:16, Dean Peterson (peterson.d...@gmail.com) >>> wrote: >>> >>> The docker logs look fine: >>> >>> - Checking HAProxy /healthz on port 1936 ... >>> - HAProxy port 1936 health check ok : 0 retry attempt(s). >>> I0530 02:17:38.582715 1 router.go:310] Router reloaded: >>> - Checking HAProxy /healthz on port 1936 ... >>> - HAProxy port 1936 health check ok : 0 retry attempt(s). >>> I0530 02:17:43.579202 1 router.go:310] Router reloaded: >>> - Checking HAProxy /healthz on port 1936 ... >>> - HAProxy port 1936 health check ok : 0 retry attempt(s). >>> I0530 02:17:51.216070 1 router.go:310] Router reloaded: >>> - Checking HAProxy /healthz on port 1936 ... >>> - HAProxy port 1936 health check ok : 0 retry attempt(s). >>> I0530 02:27:34.602411 1 router.go:310] Router reloaded: >>> - Checking HAProxy /healthz on port 1936 ... >>> - HAProxy port 1936 health check ok : 0 retry attempt(s). >>> I0530 02:37:35.603549 1 router.go:310] Router reloaded: >>> - Checking HAProxy /healthz on port 1936 ... >>> - HAProxy port 1936 health check ok : 0 retry attempt(s). >>> I0530 02:47:36.601751 1 router.go:310] Router reloaded: >>> - Checking HAProxy /healthz on port 1936 ... >>> - HAProxy port 1936 health check ok : 0 retry attempt(s). >>> >>> I've verified the router service account can access endpoints: >>> >>> oadm policy who-can list endpoints --all-namespaces >>> Namespace: <all> >>> Verb: list >>> Resource: endpoints >>> >>> Users: system:serviceaccount:default:router >>> system:serviceaccount:management-infra:management-admin >>> system:serviceaccount:openshift-infra:namespace-controller >>> >>> Groups: system:cluster-admins >>> system:cluster-readers >>> system:masters >>> system:nodes >>> system:routers >>> >>> >>> >>> On Sun, May 29, 2016 at 8:06 PM, Dean Peterson <peterson.d...@gmail.com> >>> wrote: >>> >>>> Yes, the route url is pointing at the public ip address of my ec2 >>>> instance: >>>> >>>> [ec2-user@ip-172-31-15-150 ~]$ sudo su >>>> [root@ip-172-31-15-150 ec2-user]# dig landing.enterprisewebservice.com >>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__landing.enterprisewebservice.com&d=DQMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=Q3AdrkSZOU_rcZHf2m47KnWSZ3f1fVx5dTNk1KZCv38&s=QdLx5uRgnlFAxOCITylv9UOGHmCAq2HOG5GJ1GiQ8E0&e=> >>>> >>>> ; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7_2.3 <<>> >>>> landing.enterprisewebservice.com >>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__landing.enterprisewebservice.com&d=DQMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=Q3AdrkSZOU_rcZHf2m47KnWSZ3f1fVx5dTNk1KZCv38&s=QdLx5uRgnlFAxOCITylv9UOGHmCAq2HOG5GJ1GiQ8E0&e=> >>>> ;; global options: +cmd >>>> ;; Got answer: >>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41943 >>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 >>>> >>>> ;; OPT PSEUDOSECTION: >>>> ; EDNS: version: 0, flags:; udp: 4096 >>>> ;; QUESTION SECTION: >>>> ;landing.enterprisewebservice.com >>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__landing.enterprisewebservice.com&d=DQMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=Q3AdrkSZOU_rcZHf2m47KnWSZ3f1fVx5dTNk1KZCv38&s=QdLx5uRgnlFAxOCITylv9UOGHmCAq2HOG5GJ1GiQ8E0&e=>. >>>> IN A >>>> >>>> ;; ANSWER SECTION: >>>> landing.enterprisewebservice.com >>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__landing.enterprisewebservice.com&d=DQMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=Q3AdrkSZOU_rcZHf2m47KnWSZ3f1fVx5dTNk1KZCv38&s=QdLx5uRgnlFAxOCITylv9UOGHmCAq2HOG5GJ1GiQ8E0&e=>. >>>> 30 IN A 52.39.102.120 >>>> >>>> ;; Query time: 30 msec >>>> ;; SERVER: 172.31.15.150#53(172.31.15.150) >>>> ;; WHEN: Sun May 29 21:03:52 EDT 2016 >>>> ;; MSG SIZE rcvd: 77 >>>> >>>> I have tried pointing a cname record at the public dns name of the >>>> openshift master running the router as well with no luck. >>>> >>>> On Sun, May 29, 2016 at 7:34 PM, Skarbek, John <john.skar...@ca.com> >>>> wrote: >>>> >>>>> Dean, >>>>> >>>>> You should not need to touch the /etc/resolv.conf file at all. Do you >>>>> have a wildcard A or CNAME record pointed to the public IP or FQDN of your >>>>> instance? >>>>> >>>>> If you were to do an nslookup or dig using the dns name provided by >>>>> the route, does it resolve to the public IP of your instance? >>>>> >>>>> >>>>> -- >>>>> John Skarbek >>>>> >>>>> On May 29, 2016 at 20:14:27, Dean Peterson (peterson.d...@gmail.com) >>>>> wrote: >>>>> >>>>> It seems every time I install openshift everything goes perfectly, >>>>> right up until I add a route and try to reach any of my services. I >>>>> installed with ansible using the stock openshift ansible playbook. After >>>>> I >>>>> installed I completed the setup for AWS configuration. Everything is >>>>> running. I am able to get to the actual openshift instance but I am not >>>>> able to hit the service endpoints. I have a pod running successfully, the >>>>> router logs look great. I am running a master and node on the same EC2 >>>>> instance. I used the public dns name as the master and node inventory >>>>> address. The openshift address uses a public domain configured through >>>>> Route53. If I can get to the openshift web console, why can't the router >>>>> route me to my services? I can see port 80 is bound to haproxy. As I >>>>> mentioned I completed all of the steps for the extra AWS configuration. >>>>> My >>>>> resolv.conf though points to the internal ip address assigned to the EC2 >>>>> instance. If I try to add the public address it gets overwritten. Am I >>>>> missing something obvious here? The router always seems to hang me up. >>>>> _______________________________________________ >>>>> users mailing list >>>>> users@lists.openshift.redhat.com >>>>> >>>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openshift.redhat.com_openshiftmm_listinfo_users&d=DQICAg&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=6bl7FzdE28dWS3Gc-3HCmy4opxYoELwnx2aNqL36DsQ&s=S1nZKZLfiQW2AfbvWciOvRQfvxeEV-bZsPgCY0c_3dk&e= >>>>> >>>>> >>>> >>> _______________________________________________ >>> users mailing list >>> users@lists.openshift.redhat.com >>> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openshift.redhat.com_openshiftmm_listinfo_users&d=DQICAg&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=Q3AdrkSZOU_rcZHf2m47KnWSZ3f1fVx5dTNk1KZCv38&s=NiG1WNrZpwdl-CrfVj3cpoGXGhJwRbIBBg6D0k6-Ffw&e= >>> >>> >> >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
