Bug 1396798 - Application is showing "Application is not available"
Summary: Application is showing "Application is not available"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Routing
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-20 10:41 UTC by Stijn.beeckmans
Modified: 2016-11-21 11:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1392188
Environment:
Last Closed: 2016-11-21 11:42:39 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Stijn.beeckmans 2016-11-20 10:41:50 UTC
+++ This bug was initially created as a clone of Bug #1392188 +++

Description of problem:


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

How reproducible:
Create a NodeJS 4 application using the helloworld code below:
[code]
// Load the http module to create an http server.
var http = require('http');

// Configure our HTTP server to respond with Hello World to all requests.
var server = http.createServer(function (request, response) {
  response.writeHead(200, {"Content-Type": "text/plain"});
  response.end("Hello World\n");
});

// Listen on port 8080
server.listen(8080);

// Put a friendly message on the terminal
console.log("Server running on OpenShift");
[/code]

Steps to Reproduce:
1. Create a NodeJS 4 application using the code above
2. Wait until it deploys.
3. Open the browser and try the public URL.

Actual results:

Appears the messagge:

"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:
"Hello world"

Additional info:

Yesterday it worked without problem. I haven't touched it and today it fails... I tried to rebuild/redeploy but it didn't change anything.

I tested the different URL's with curl:
curl -kv http://172.31.10.162:8080 --> This is the service IP (fail)
curl -kv http://10.1.26.33:8080 --> This is the endpoint IP (fail)
curl -kv http://backend-demoproject.44fs.preview.openshiftapps.com/ --> This is the external URL (fail)

Route yaml:
apiVersion: v1
kind: Route
metadata:
  name: backend
  namespace: demoproject
  selfLink: /oapi/v1/namespaces/demoproject/routes/backend
  uid: cd597104-ad20-11e6-a64c-0e3d364e19a5
  resourceVersion: '383378633'
  creationTimestamp: '2016-11-17T23:51:47Z'
  labels:
    app: backend
  annotations:
    openshift.io/generated-by: OpenShiftWebConsole
    openshift.io/host.generated: 'true'
spec:
  host: backend-demoproject.44fs.preview.openshiftapps.com
  to:
    kind: Service
    name: backend
    weight: 100
  port:
    targetPort: 8080-tcp
status:
  ingress:
    -
      host: backend-demoproject.44fs.preview.openshiftapps.com
      routerName: router
      conditions:
        -
          type: Admitted
          status: 'True'
          lastTransitionTime: '2016-11-17T23:51:47Z'

I have this problem with all services on my project
- Backend (see info above)
- Frontend (http://frontend-demoproject.44fs.preview.openshiftapps.com/)

Comment 1 Stijn.beeckmans 2016-11-21 11:42:39 UTC
I can reach the endpoints again, so this is no longer a bug...


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