search

fabric8-services / fabric8-tenant-jenkins

Generates Jenkins tenant namespace YAML
Apache License 2.0
2 stars 14 forks source link

Fix 503 errors events of failing readiness probe in Jenkins Pod #121

Closed piyush-garg closed 6 years ago

piyush-garg commented 6 years ago

This will fix the issue of 503 events on Jenkins pod because of readiness probe failure during the idling/unidling condition and fewer error events logs for setup

In this commit, basically, the initial delay time has been increased from 10 seconds to 40 seconds because what we have observed till now is Jenkins takes approx 3m30s in first startup and approx 30s-35s in subsequent startups.

Timeout seconds have been increased to 4m because handling the the scenario where the first startup take approx 3m30s

Period seconds have been increased to 15s to give fewer errors but access to Jenkins should be given as early as possible

Fixes openshiftio/openshift.io#3934

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

sthaha commented 6 years ago

@piyush1594 see: rdprobe-failed

piyush-garg commented 6 years ago

@sthaha I tested it thrice and it worked for me.

sthaha commented 6 years ago

@piyush1594 I am guessing that on all 3 tries it started within 40 seconds. Have you checked how long it took to start?

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

fabric8cd commented 6 years ago

PR now available for testing: Launch in OpenShift.io and click the update tenant button

piyush-garg commented 6 years ago

I am merging this PR as it has two approvals. Thanks