+++ This bug was initially created as a clone of Bug #1567532 +++
Description of problem:
An application created from the template "Apache HTTP Server (httpd)" using the example Git repository (and presumably any other application) works fine (readiness probe and curl on localhost from terminal are both able to access it normally), but when I try to access it via the route (http://testrote-apache-test.193b.starter-ca-central-1.openshiftapps.com/), it shows an error (Application is not available...)
The same thing happens with both HTTP and HTTPS.
Version-Release number of selected component (if applicable):
v3.9.14 (online version 22.214.171.124.1)
Steps to Reproduce:
1. Create a project (and an application) using the "Apache HTTP Server (httpd)" template and the sample repository (https://github.com/openshift/httpd-ex.git).
2. The URL of the generated route is opened in a browser (in my case http://testrote-apache-test.193b.starter-ca-central-1.openshiftapps.com/).
The error "The application is currently not serving requests at this endpoint. It may not have been started or is still starting."
Default OpenShift Apache page.
Fixed by https://github.com/openshift/ose/pull/1234
Tested in atomic-openshift-3.9.27-1.git.0.964617d but still can found error in haproxy logs when creating headless service and idling it.
E0502 06:15:17.588280 1 limiter.go:137] error reloading router: exit status 1
[ALERT] 121/061517 (963) : parsing [/var/lib/haproxy/conf/haproxy.config:229] : 'server ept:service-unsecure:None:27017' : could not resolve address 'None'.
[ALERT] 121/061517 (963) : Failed to initialize server(s) addr.
seems the PR has not been merged to 3.9.27.
not fixed in 3.9.27, please check if PR merged.
3.9.27-1 was cut before this was merged. Not sure why it got moved by the errata tool.
This bug had been verified in https://bugzilla.redhat.com/show_bug.cgi?id=1553552#c5.
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.