Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1571479 - [3.9] Web server works fine, but is inaccessible via a route (Application is not available...)
[3.9] Web server works fine, but is inaccessible via a route (Application is ...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Routing (Show other bugs)
3.9.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.9.z
Assigned To: Ravi Sankar
zhaozhanqi
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-24 19:49 EDT by Ravi Sankar
Modified: 2018-10-25 05:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Headless service will have service.Spec.ClusterIP=None and this is not ignored as part of un-idling. Consequence: This will generate incorrect endpoint ID in the HAProxy config and the config will fail to load. This leads to router not servicing any routes. Fix: Ignore headless services during unidle handling Result: No problem with HAProxy config loading and router will service routes as expected.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-08-09 18:13:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2335 None None None 2018-08-09 18:14 EDT

  None (edit)
Description Ravi Sankar 2018-04-24 19:49:46 EDT
+++ 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 3.6.0.45.1) 

How reproducible:
Always.

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/).

Actual results:
The error "The application is currently not serving requests at this endpoint. It may not have been started or is still starting."

Expected results:
Default OpenShift Apache page.
Comment 1 Ravi Sankar 2018-04-25 15:01:55 EDT
Fixed by https://github.com/openshift/ose/pull/1234
Comment 2 Ravi Sankar 2018-04-26 17:12:43 EDT
https://github.com/openshift/ose/pull/1235
Comment 6 hongli 2018-05-02 02:31:22 EDT
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.
Comment 8 hongli 2018-05-02 21:58:36 EDT
not fixed in 3.9.27, please check if PR merged.
Comment 9 Ben Bennett 2018-05-03 11:57:38 EDT
3.9.27-1 was cut before this was merged.  Not sure why it got moved by the errata tool.
Comment 12 zhaozhanqi 2018-07-26 05:06:31 EDT
This bug had been verified in https://bugzilla.redhat.com/show_bug.cgi?id=1553552#c5.
Comment 14 errata-xmlrpc 2018-08-09 18:13:49 EDT
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/RHBA-2018:2335

Note You need to log in before you can comment on or make changes to this bug.