#135 Fedora CI Pull Request Pipeline - Application is not available
Closed by msrb. Opened by plautrba.

https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-pr-pipeline reports:

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.

The jenkins POD was restarted:

https://console.apps.ci.centos.org:8443/console/project/continuous-infra/browse/pods/jenkins-193-rxn4h?tab=details

It looks like there is routing issue

I see some issues like:

1:21:01 PM  Warning     Unhealthy   Readiness probe failed: HTTP probe failed with statuscode: 503
452 times in the last hour
1:11:01 PM  Warning     Unhealthy   Readiness probe failed: Get http://10.128.9.135:8080/login: dial tcp 10.128.9.135:8080: getsockopt: connection refused
162 times in the last hour
1:06:01 PM  Warning     Unhealthy   Liveness probe failed: HTTP probe failed with statuscode: 503

@plautrba thanks for the ticket, I after we redeployed the POD again the jenkins is accessible.

Metadata Update from @bgoncalv:
- Issue status updated to: Closed (was: Open)

The same problem appears with https://src.fedoraproject.org/rpms/selinux-policy/pull-request/97 -> https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr-pipeline/4591/pipeline/ -> Application is not available

Metadata Update from @plautrba:
- Issue status updated to: Open (was: Closed)

Seeing it right now, trying to review 2-day-old bodhi results: (bodhi link) (jenkins link)

[UPDATE, just a few seconds later] and, of course, it's working now.

I restarted the instance. Please try now :wink:

Metadata Update from @msrb:
- Issue status updated to: Closed (was: Open)

Metadata