| Summary: | OSE helloworld example app not working: getsockopt: connection refused | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Quickstart Cloud Installer | Reporter: | Antonin Pagac <apagac> | ||||||||
| Component: | Installation - OpenShift | Assignee: | Jason Montleon <jmontleo> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | James Olin Oden <joden> | ||||||||
| Severity: | unspecified | Docs Contact: | Derek <dcadzow> | ||||||||
| Priority: | unspecified | ||||||||||
| Version: | 1.0 | CC: | arubin, bthurber, dymurray, jmontleo, joden, llasmith, tsanders | ||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||
| Target Release: | 1.1 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-02-28 01:39:24 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Antonin Pagac
2016-09-07 09:06:53 UTC
Created attachment 1198606 [details]
'oc describe pod php-helloworld-1-build'
Spoke with Antonin and we are waiting to see if this can be reproduced. If it can, the log we need would be from the command 'oc logs bc/docker-registry'. Normally this error is due to OpenShift docker registry not running, but in this instance the docker-registry deployer failed before the registry even was created. Couldn't reproduce with the latest ISO on 9/8. I verified after deployment the registry was running and the sample application was accessible. I finally managed to reproduce the issue with 20160902.5. The error message is the same. Yesterday, when manually started, sample app was working. There is a suspicion for a timing issue. I'll try to reproduce using 9/8 ISO. Reproduced also with QCI-1.0-RHEL-7-20160902.5. Sorry, I meant QCI-1.0-RHEL-7-20160908.1 Upon manually starting the failing sample app, I get this error: "Could not resolve host: www.github.com; Unknown error" I then did these steps: "[root@5-ose-master1 ~]# ping github.com ping: unknown host github.com [root@5-ose-master1 ~]# getent hosts github.com 192.30.253.113 github.com [root@5-ose-master1 ~]# ping github.com PING github.com (192.30.253.113) 56(84) bytes of data. 64 bytes from 192.30.253.113: icmp_seq=1 ttl=51 time=15.7 ms ... [root@5-ose-master1 ~]# oc start-build php-helloworld" The example app is now working and available. It seems for some reason the DNS is taking too long to respond on my bare metal setup. Same issue seen on the QCI-1.1-RHEL-7-20161121.t.0 iso. I have seen successes with the sample app on this iso version but this deployment took ~6hrs to deploy. Created attachment 1222996 [details]
Output of OpenShift commands
*** Bug 1365992 has been marked as a duplicate of this bug. *** *** Bug 1367173 has been marked as a duplicate of this bug. *** With sample application working as of 12/7 I am moving this to ON_QA in correlation with BZ 1384103. Still seems to be broken. I'm getting a "503 Service Unavailable" when I click the link. The compose is QCI-1.1-RHEL-7-20161206.t.0 After investigating James' deployment, the master host is unable to mount the NFS share from the Satellite host without getting an "access denied". I am able to mount his share from my desktop which tells me there is some firewall issue or perhaps selinux issue blocking the master host from mounting. *** Bug 1384103 has been marked as a duplicate of this bug. *** *** Bug 1395584 has been marked as a duplicate of this bug. *** Verified in QCI-1.1-RHEL-7-20161212.t.2-QCI-x86_64-dvd1.iso Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:0335 |