Bug 1392188

Summary:

NodeJS application is showing "Application is not available" instead index.html

Product:

OpenShift Online

Reporter:

Jordi <jordiszrz>

Component:

Networking

Assignee:

Ben Bennett <bbennett>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Meng Bo <bmeng>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

3.x

CC:

aos-bugs, bingli, jordiszrz, mmasters

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:

Clones:

1396798 (view as bug list)

Environment:

Last Closed:

2017-02-16 22:11:16 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:

Attachments:

Description	Flags
log.doc	none

Description Jordi 2016-11-05 20:18:31 UTC

Description of problem:


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

How reproducible:
Create a NodeJS 4 application using the example from quick start.

Steps to Reproduce:
1. Create a NodeJS 4 application using the example from quick start.
2. Wait until it deploys.
3. Open the browser and trye 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:
The index.html from example should be showed.

Additional info:

Yesterday it worked without problem. I can see the next warning message in the monitoring (I dont know if it is related):
Error syncing pod, skipping: failed to "TeardownNetwork" for "api-1-deploy_iknow" with TeardownNetworkError: "Failed to teardown network for pod \"f07239f9-a385-11e6-a4cc-0e63b9c1c48f\" using network plugins \"redhat/openshift-ovs-multitenant\": Error running network teardown script: Could not find IP address for container 29dfedce5e6f63185f614e8a47b5970f3225ebe830416f0871c62d93ac03310a"

Comment 1 Jordi 2016-11-07 12:56:56 UTC

The monitoring message is not related, I have test it in a new account and the problem persist but the monitoring message dosent appears.

Comment 2 Ben Bennett 2016-11-07 13:44:42 UTC

What version?

That teardown error is a red herring.  Can you see if the pod is running and get the endpoints list?  I imagine that there is a deployment error that you need to look into.

Comment 3 Jordi 2016-11-07 17:19:04 UTC

Hi,

Is not a deployment error, I have connected with rsh to the service, and executed a curl command with the next results:
IP Service: the index.html is received succesfuly
Endpoint: the index.html is received succesfuly
External URL: the application is not available message is received

I will give you the IP and endpoint a bit later (I cant access just now).

Comment 4 Jordi 2016-11-07 17:32:17 UTC

Created attachment 1218160 [details]
log.doc

Comment 5 Jordi 2016-11-07 17:37:58 UTC

I have attached a doc file with the log of the next commands:
oc status
oc get ep
oc rsh
   curl -kv http://172.30.250.25:8080 --> This is the service IP (ok)
   curl -kv http://10.1.83.12:8080 --> This is the endpoint IP (ok)
   curl -kv http://nodejs-mongodb-example-iknow.44fs.preview.openshiftapps.com --> This is the external URL (fail)

Have you tried to create a new node.js application using the template "nodejs-mongodb-example"? I think that this is a global problema and should be happening to everyone.

Comment 6 Ben Bennett 2016-11-07 18:22:01 UTC

What does your route yaml look like?

Comment 7 Jordi 2016-11-07 19:14:10 UTC

Here is it (I have just recreated it with same result):

apiVersion: v1
kind: Route
metadata:
  name: nodejs-mongodb-example
  namespace: iknow
  selfLink: /oapi/v1/namespaces/iknow/routes/nodejs-mongodb-example
  uid: 0c916fa9-a51e-11e6-a4cc-0e63b9c1c48f
  resourceVersion: '321643248'
  creationTimestamp: '2016-11-07T19:11:55Z'
  labels:
    app: nodejs-mongodb-example
    template: nodejs-mongodb-example
  annotations:
    openshift.io/host.generated: 'true'
spec:
  host: nodejs-mongodb-example-iknow.44fs.preview.openshiftapps.com
  to:
    kind: Service
    name: nodejs-mongodb-example
    weight: 100
  port:
    targetPort: web
status:
  ingress:
    -
      host: nodejs-mongodb-example-iknow.44fs.preview.openshiftapps.com
      routerName: router
      conditions:
        -
          type: Admitted
          status: 'True'
          lastTransitionTime: '2016-11-07T19:11:56Z'

Comment 9 Miciah Dashiel Butler Masters 2016-11-07 22:15:35 UTC

Thanks for the report! The problem should be resolved now.  Can you verify?

Comment 10 Jordi 2016-11-07 22:22:20 UTC

Great!! Now it works :D

Thanks a lot Miciah, I will continue testing it next days.

Comment 11 Meng Bo 2016-11-08 11:55:44 UTC

@Jordi
Can you help change the status of the bug to VERIFIED if your problem has been resolved?

Comment 12 Jordi 2016-11-08 14:56:11 UTC

Done!

Comment 13 Bing Li 2016-11-09 02:20:27 UTC

The router works fine now in Online and the application's public url can be accessed normally.

Comment 14 Stefanie Forrester 2016-11-21 15:27:20 UTC

*** Bug 1396892 has been marked as a duplicate of this bug. ***