Bug 1404221

Summary:	Getting "Application is not available" message
Product:	OpenShift Online	Reporter:	Douglas Fernandes <douglasf.filho>
Component:	Deployments	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED NOTABUG	QA Contact:	zhou ying <yinzhou>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.x	CC:	aos-bugs, douglasf.filho, wgordon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Other
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-13 17:58:01 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:

Description Douglas Fernandes 2016-12-13 12:00:36 UTC

Description of problem:

I can access my application from the original path that was generated by the online console on openshift next gen (http://home-compliance.44fs.preview.openshiftapps.com/), but, if I try to access my domain "http://www.compliancesoftware.com.br", it's seams not routing to my application address, instead of this, I'm getting the screen with Aplication is not available message.

Detail: Already set the DNS CNAME to point to "http://home-compliance.44fs.preview.openshiftapps.com/" when accessing "http://www.compliancesoftware.com.br"

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


How reproducible:

Deploying a war file of site using WildFly 10.0

Steps to Reproduce:
1.On online console of next gen, create a new project.
2.Follow these instructions "https://blog.openshift.com/deploying-war-file-openshift-online-3/"
3.After deploy, the application may be accessible from the route exposed to.

Actual results:
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:
The same as accessing the original url: the application index

Additional info:

Comment 1 Douglas Fernandes 2016-12-13 12:07:05 UTC

To be cleary:

hit "http://www.compliancesoftware.com.br/" or "http://compliancesoftware.com.br/" points to "http://home-compliance.44fs.preview.openshiftapps.com/" via CNAME setting on DNS Server (I'm using CloudFlare).

If accessing "http://home-compliance.44fs.preview.openshiftapps.com/", will take the application home screen;

If accessing "http://compliancesoftware.com.br/", got the Application not available screen.

Thank you and sorry by my poor english spelling.

Comment 2 Will Gordon 2016-12-13 17:58:01 UTC

Hi Douglas,

This is actually expected behavior during our developer preview. For our next gen platform, we have custom domains disabled. This is a feature that will be coming, once we reach our General Availability. For information regarding General Availability, please check our website or blog occasionally for announcements that are yet to come:
https://www.openshift.com/
https://blog.openshift.com/

Thanks!