Bug 1599427

Summary:	application not available after successful deployment
Product:	OpenShift Online	Reporter:	bugzy <bugzy231>
Component:	Routing	Assignee:	Dan Mace <dmace>
Status:	CLOSED WORKSFORME	QA Contact:	zhaozhanqi <zzhao>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aos-bugs, rpenta, zzhao
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-10 22:16:51 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:
Embargoed:

Description bugzy 2018-07-09 19:00:57 UTC

Description of problem: application not available on the browser after successful deployment. 


Version-Release number of selected component (if applicable):


How reproducible:Create a node js application from github repo


Steps to Reproduce:
1.Create a new project
2.add a node js application to the project from the catalog
3.git repository: https://github.com/bugzy101/afrihub.git

Actual results: This message will appear on the browser:

Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.



Expected results:Home page of my application


Additional info: The pod is active and running after deployment, and the logs show no errors. everything looks good, but when you visit the route on a browser, it shows the message that application is not available.

Comment 1 zhaozhanqi 2018-07-10 03:42:50 UTC

hi, bugzy

I was testing this for online-int. it's working well using nodejs with your repo

see: http://nodejs-test-zzhao.34bf.online-int.openshiftapps.com/

Could you show what's the version and env when you met this issue. thanks.

Comment 2 zhaozhanqi 2018-07-10 06:13:52 UTC

sorry, bugzy. just saw you are using external account. I'm not sure maybe you cannot access the internal URL http://nodejs-test-zzhao.34bf.online-int.openshiftapps.com/.

Could you show more what's the version and env?

Comment 3 bugzy 2018-07-10 12:27:43 UTC

(In reply to zhaozhanqi from comment #1)
> hi, bugzy
> 
> I was testing this for online-int. it's working well using nodejs with your
> repo
> 
> see: http://nodejs-test-zzhao.34bf.online-int.openshiftapps.com/
> 
> Could you show what's the version and env when you met this issue. thanks.

Hi Zhao, it seems to be working now after the whole day of deploying it. As per the issue, I only had a MONGO_URL with its login credentials in the enviroment, and everyother setting was on default. But it is working now anyways. Thanks a lot.

Comment 4 Ravi Sankar 2018-07-10 17:52:01 UTC

@bugzy, @zzhao
As per comment#3, there is no issue with the deployment?
Please close the bug or provide us with more details if there is a real issue.