Bug 1635755 - NodeJS application is showing "Application is not available"
Summary: NodeJS application is showing "Application is not available"
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Networking
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Casey Callendrello
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-03 15:33 UTC by Sascha
Modified: 2020-01-09 10:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-21 16:04:31 UTC
Target Upstream Version:
Embargoed:
sascha.kieslich: needinfo-


Attachments (Terms of Use)

Description Sascha 2018-10-03 15:33:42 UTC
Description of problem:


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

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

Steps to Reproduce:
1. Create a NodeJS 10 application on open shift container platform
2. adding git repository to project 
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:
My application index page is showen

Additional Information:
- pods are created and up running
- no errors in monitoring or logs
- none of my log messages are showen in application log

route yml: 

apiVersion: route.openshift.io/v1
kind: Route
metadata:
  annotations:
    openshift.io/generated-by: OpenShiftWebConsole
    openshift.io/host.generated: 'true'
  creationTimestamp: '2018-09-23T14:04:14Z'
  labels:
    app: einhorngarde
  name: einhorngarde
  namespace: einhorngarde
  resourceVersion: '2733089365'
  selfLink: /apis/route.openshift.io/v1/namespaces/einhorngarde/routes/einhorngarde
  uid: 8dbc6ff5-bf39-11e8-b32a-0a69cdf75e6f
spec:
  host: einhorngarde-einhorngarde.7e14.starter-us-west-2.openshiftapps.com
  port:
    targetPort: 8080-tcp
  to:
    kind: Service
    name: einhorngarde
    weight: 100
  wildcardPolicy: None
status:
  ingress:
    - conditions:
        - lastTransitionTime: '2018-09-23T14:04:14Z'
          status: 'True'
          type: Admitted
      host: einhorngarde-einhorngarde.7e14.starter-us-west-2.openshiftapps.com
      routerCanonicalHostname: elb.7e14.starter-us-west-2.openshiftapps.com
      routerName: router
      wildcardPolicy: None

Comment 1 Ben Bennett 2019-01-17 18:38:55 UTC
Can you please try the different layers:
1) Can you curl the pod IP at the right port (I don't have the service or pod spec so I can't tell what that is)
2) Can you curl the service IP at port 8080
3) Can you provide the service and pod specs

Comment 2 Casey Callendrello 2019-02-21 16:04:31 UTC
Closing for now, feel free to reopen if this is still an issue.

Comment 3 Sascha 2020-01-09 10:34:37 UTC
Thank you very much. I don't use this Server anymore. Bug can be closed, so I don't get any more emails.


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