Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Openshift ocp fails due to livenessProbe. #8263

Merged
merged 1 commit into from
Jan 15, 2018

Conversation

JamesDrummond
Copy link
Contributor

What does this PR do?

The livenessProbe's failureThreshold is set to low. This causes the livenessProbe having to short a period of probing before it fails and removes the container. The failureThreshold is set to 4, the initialDelaySeconds is set to 5 and the periodSeconds is 5. This means 5s+4x5s=25s before the container fails. This patch set failureThreshold higher to 11 allowing for a more reasonable overall probe time of 60s (5s+11x5s=60s) before fails and removes the container.

What issues does this PR fix or reference?

#7799

Release Notes

N/A

Signed-off-by: James Drummond james@devcomb.com

The livenessProbe's failureThreshold is set to low. This causes the livenessProbe having to short a period of probing before it fails and removes the container. The failureThreshold is set to 4, the initialDelaySeconds is set to 5 and the periodSeconds is 5. This means 5s+4x5s=25s before the container fails. This patch set failureThreshold higher to 11 allowing for a more reasonable overall probe time of 60s (5s+11x5s=60s) before fails and removes the container.

Signed-off-by: James Drummond <james@devcomb.com>
@JamesDrummond JamesDrummond added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. labels Jan 11, 2018
@JamesDrummond JamesDrummond added this to the 6.0.0-M5 milestone Jan 11, 2018
@JamesDrummond JamesDrummond self-assigned this Jan 11, 2018
@codenvy-ci
Copy link

Can one of the admins verify this patch?

1 similar comment
@codenvy-ci
Copy link

Can one of the admins verify this patch?

@JamesDrummond
Copy link
Contributor Author

JamesDrummond commented Jan 11, 2018

Put high severity as keycloak on multiuser will fail unless using a pod with high CPU that can startup keycloak under 25 seconds.

@codenvy-ci
Copy link

Can one of the admins verify this patch?

@benoitf benoitf added the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Jan 11, 2018
Copy link
Member

@sleshchenko sleshchenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK for me

@JamesDrummond JamesDrummond merged commit 4b0e2da into master Jan 15, 2018
@JamesDrummond JamesDrummond deleted the openshift-multiuser-fix branch January 15, 2018 16:24
@benoitf benoitf removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Jan 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants