Description of problem: Jenkins readinessProbe initialDelaySeconds: 3 is too short. Jenkins is Java and it typically needs 60 sec for boot on 4 CPU cores machine. 3 sec is too short, spamming events with readiness probe failure messages and users get confused by these many failures. I think initialDelaySeconds: 60 would be reasonable default. The livenessProbe is configured with initialDelaySeconds: 420. Version-Release number of selected component (if applicable): v3.7 How reproducible: Always Steps to Reproduce: 1. oc new-app jenkins-ephemeral 2. 3. Actual results: Getting readiness probe failure 20 times at Jenkins boot Expected results: No or few readiness probe failure at Jenkins boot Additional info:
Upstream pull req https://github.com/openshift/origin/pull/19072
This got bumped in the 3.9 ansible installer version of the templates, and https://github.com/openshift/origin/pull/18900 is waiting for 3.9 to open back up after GA. Once that happens it will be in the subsequent 3.9 errata. The template is already modified for this in the openshift/origin master branch. There are no plans to update 3.7 openshift to backport these changes.
Could access jenkins webconsole smoothly with ocp 3.9.20 which has included new updated jenkins template.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1566