Bug 1396892

Summary: [online prod] Route's public hostname can't be accessed in online dev-preview
Product: OpenShift Online Reporter: Bing Li <bingli>
Component: WebsiteAssignee: Stefanie Forrester <dakini>
Status: CLOSED DUPLICATE QA Contact: Bing Li <bingli>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.xCC: aos-bugs, jokerman, mmccomas, zhiwliu
Target Milestone: ---   
Target Release: ---   
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: 2016-11-21 15:27:20 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 Bing Li 2016-11-21 05:58:38 UTC 
Description of problem:
Create a new app using the example from quick start, the public url can't be accessed in the browser.

Version-Release number of selected component (if applicable):
Online PROD
OpenShift Master: v3.3.1.3
Kubernetes Master: v1.3.0+52492b4

How reproducible:
Always

Steps to Reproduce:
1. Create a new app using a default quickstart template. E.g. "dancer-mysql-example";

2. After all the pods are running well, check if the route's public url can be accessed or not.


Actual results:
1. Route's public hostname can't be accessed by a browser: "Application is not available"

Expected results:
1. Should be accessed successfully.
Comment 1 Zhiwu Liu 2016-11-21 06:14:51 UTC 
according to https://bugzilla.redhat.com/show_bug.cgi?id=1392188#c8 , after a re-deploy, it works, user can access it's app
Comment 2 Bing Li 2016-11-21 06:30:20 UTC 
Route is working well in online dev-preview and it's a same issue with bug 1392188.
Comment 3 Stefanie Forrester 2016-11-21 15:27:20 UTC 
I checked config management and it doesn't look like this is at risk of happening again. EXTENDED_VALIDATION=true remains after the ansible run.

*** This bug has been marked as a duplicate of bug 1392188 ***