Bug 1559675
Summary: | Jenkins readinessProbe initialDelaySeconds: 3 is too short and spamming events | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Takayoshi Kimura <tkimura> |
Component: | ImageStreams | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED ERRATA | QA Contact: | Dongbo Yan <dyan> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.7.0 | CC: | aos-bugs, bparees, jokerman, mmccomas, xiuwang |
Target Milestone: | --- | ||
Target Release: | 3.9.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: resource constraints can lead to the readiness probe in the example jenkins templates readiness probes citing failure prematurely
Consequence: jenkins deployments would fail unnecessarily
Fix: the readiness probe was relaxed in the tempaltes
Result: unnecessary jenkins deployment failures due to the aggressive readiness probe should decrease / go away
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-17 06:43:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Takayoshi Kimura
2018-03-23 01:41:34 UTC
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 |