-
Notifications
You must be signed in to change notification settings - Fork 71
[release-4.12] OCPBUGS-7650: Catalog Pod Startup Probe Timeout #450
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
[release-4.12] OCPBUGS-7650: Catalog Pod Startup Probe Timeout #450
Conversation
Updates the Startup Probe timeoutSeconds for catalog pods to be consistent with the timeouts in the readiness and liveness probes. Also adjusted the failure threshold in order to maintain the ~150s startup time failure as originally designed. Upstream-repository: operator-lifecycle-manager Upstream-commit: 401bfff4df20c97bef08db2dc9fc75bc1879be7a Signed-off-by: dtfranz <[email protected]>
@openshift-cherrypick-robot: Jira Issue OCPBUGS-672 has been cloned as Jira Issue OCPBUGS-7650. Retitling PR to link against new bug. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-7650, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
1 similar comment
/retest |
/label backport-risk-assessed |
/jira refresh |
@perdasilva: This pull request references Jira Issue OCPBUGS-7650, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, perdasilva The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/jira refresh |
@dtfranz: This pull request references Jira Issue OCPBUGS-7650, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/lgtm |
/retest |
16 similar comments
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@openshift-cherrypick-robot: Jira Issue OCPBUGS-7650: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-7650 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@bandrade How am I suppose to know what version of Version: version.Version{OpmVersion:"dd3cc9cbf", GitCommit:"dd3cc9cbf5ccc16441f427b2d1386d6ca430f82f", BuildDate:"2023-03-24T03:33:30Z", GoOs:"linux", GoArch:"arm64"}. Is there a reason why we use a commit instead a version? |
[ART PR BUILD NOTIFIER] This PR has been included in build operator-lifecycle-manager-container-v4.12.0-202305022015.p0.gdd3cc9c.assembly.stream for distgit operator-lifecycle-manager. |
[ART PR BUILD NOTIFIER] This PR has been included in build operator-registry-container-v4.12.0-202305022015.p0.gdd3cc9c.assembly.stream for distgit operator-registry. |
/cherry-pick release-4.11 |
@dtfranz: new pull request created: #509 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is an automated cherry-pick of #446
/assign dtfranz