Skip to content

[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

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #446

/assign dtfranz

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-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-672 has been cloned as Jira Issue OCPBUGS-7650. Retitling PR to link against new bug.
/retitle [release-4.12] OCPBUGS-7650: Catalog Pod Startup Probe Timeout

In response to this:

This is an automated cherry-pick of #446

/assign dtfranz

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-ci openshift-ci bot changed the title [release-4.12] OCPBUGS-672: Catalog Pod Startup Probe Timeout [release-4.12] OCPBUGS-7650: Catalog Pod Startup Probe Timeout Feb 16, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 16, 2023
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-7650, which is invalid:

  • expected dependent Jira Issue OCPBUGS-672 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #446

/assign dtfranz

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-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2023

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.12] OCPBUGS-7650: Catalog Pod Startup Probe Timeout

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.

@dtfranz
Copy link
Contributor

dtfranz commented Feb 17, 2023

/retest

1 similar comment
@dtfranz
Copy link
Contributor

dtfranz commented Feb 17, 2023

/retest

@perdasilva
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 20, 2023
@perdasilva
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

@perdasilva: This pull request references Jira Issue OCPBUGS-7650, which is invalid:

  • expected dependent Jira Issue OCPBUGS-672 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@perdasilva
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 21, 2023

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 21, 2023
@dtfranz
Copy link
Contributor

dtfranz commented Feb 23, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Feb 23, 2023
@openshift-ci-robot
Copy link

@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
  • bug is open, matching expected state (open)
  • bug target version (4.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-672 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-672 targets the "4.13.0" version, which is one of the valid target versions: 4.13.0
  • bug has dependents

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:

/jira refresh

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-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 23, 2023
@awgreene
Copy link
Contributor

awgreene commented Mar 2, 2023

/lgtm

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 2, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 5819088 and 2 for PR HEAD 47de0c3 in total

@perdasilva
Copy link
Contributor

/retest

16 similar comments
@dtfranz
Copy link
Contributor

dtfranz commented Mar 3, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 6, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 6, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 7, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 7, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 7, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 7, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 7, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 8, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 8, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 8, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 8, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 9, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 9, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 13, 2023

/retest

@dtfranz
Copy link
Contributor

dtfranz commented Mar 15, 2023

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 5819088 and 2 for PR HEAD 47de0c3 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b674ff3 and 1 for PR HEAD 47de0c3 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 21, 2023

@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-merge-robot openshift-merge-robot merged commit dd3cc9c into openshift:release-4.12 Mar 21, 2023
@openshift-ci-robot
Copy link

@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:

This is an automated cherry-pick of #446

/assign dtfranz

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.

@IzzyMusa
Copy link

IzzyMusa commented Apr 5, 2023

@bandrade How am I suppose to know what version of opm this corresponds to??

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?

@openshift-bot
Copy link
Contributor

[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.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[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.
All builds following this will include this PR.

@dtfranz
Copy link
Contributor

dtfranz commented Jul 12, 2023

/cherry-pick release-4.11

@openshift-cherrypick-robot
Copy link
Author

@dtfranz: new pull request created: #509

In response to this:

/cherry-pick release-4.11

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.