I created a new route, and this time I get a different two different errors.

In http:

502 Bad Gateway

The server returned an invalid or incomplete response.


In https:

Application is not available

The application is currently not serving requests at this endpoint. It may not have been started or is still starting.

Possible reasons you are seeing this page:

  • The host doesn't exist. Make sure the hostname was typed correctly and that a route matching this hostname exists.
  • The host exists, but doesn't have a matching path. Check if the URL path was typed correctly and that the route was created using the desired path.
  • Route and path matches, but all pods are down. Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.

On 11 April 2017 at 21:35, Anton <kurrent93@gmail.com> wrote:
Hi Matt
On 11 April 2017 at 19:51, Matt Wringe <mwringe@redhat.com> wrote:

What happens if you open the metrics URL?

By default the metrics certificate is self signed and not trusted by the browser. So you will first need to click on the link and verify if you trust the certificate or not. If you accept the certificate and refresh the metrics page, do you still see the error?

Its a dns issue, rather than a cert issue:

This site can’t be reached

hawkular-metrics.apps.console.mydomain.com’s server DNS addresscould not be found.

DNS_PROBE_FINISHED_NXDOMAIN
 

If not, you might be running into an issue. If that is the case, can you please attach the output of 'oc get pods -n openshift-infra' to see what state each of the pods are in?

# oc get pods -n openshift-infra
NAME                         READY     STATUS    RESTARTS   AGE
hawkular-cassandra-1-qnx2x   1/1       Running   0          3d
hawkular-metrics-3qhpj       1/1       Running   5          3d
heapster-69qzn               1/1       Running   4          3d