Skip to content

[release-4.15] OCPBUGS-57430: reduce cache expiry frequency [release-4.19] #1023

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: release-4.15
Choose a base branch
from
Open

[release-4.15] OCPBUGS-57430: reduce cache expiry frequency [release-4.19] #1023

wants to merge 1 commit into from
+6 −2

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #1019

/assign openshift-ci-robot

@grokspawn
reduce cache expiriry frequency (#3591)
98387bd 
Signed-off-by: grokspawn <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: bf9ffe8b04b59e9acd859ac8a9b6698f1f2a3437
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jun 12, 2025
Merged
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-57352 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.15] OCPBUGS-57430: reduce cache expiry frequency [release-4.19]

In response to this:

This is an automated cherry-pick of #1019

/assign openshift-ci-robot

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.15] OCPBUGS-57352: reduce cache expiry frequency [release-4.19] [release-4.15] OCPBUGS-57430: reduce cache expiry frequency [release-4.19] Jun 12, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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 Jun 12, 2025
@openshift-ci-robot
Copy link

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

  • expected dependent Jira Issue OCPBUGS-57429 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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 #1019

/assign openshift-ci-robot

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 openshift-eng/jira-lifecycle-plugin repository.

@grokspawn
Copy link
Contributor

/retest-required

2 similar comments
@grokspawn
Copy link
Contributor

/retest-required

@grokspawn
Copy link
Contributor

/retest-required

@oceanc80
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 Jun 30, 2025
@grokspawn
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 30, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 30, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, openshift-cherrypick-robot

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 Jun 30, 2025
@grokspawn
Copy link
Contributor

/retest-required

2 similar comments
@grokspawn
Copy link
Contributor

/retest-required

@grokspawn
Copy link
Contributor

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@grokspawn
Copy link
Contributor

/retest-required

6 similar comments
@dtfranz
Copy link
Contributor

dtfranz commented Aug 1, 2025

/retest-required

@grokspawn
Copy link
Contributor

/retest-required

@dtfranz
Copy link
Contributor

dtfranz commented Aug 4, 2025

/retest-required

@dtfranz
Copy link
Contributor

dtfranz commented Aug 4, 2025

/retest-required

@dtfranz
Copy link
Contributor

dtfranz commented Aug 4, 2025

/retest-required

@dtfranz
Copy link
Contributor

dtfranz commented Aug 4, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@dtfranz
Copy link
Contributor

dtfranz commented Aug 5, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

4 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@grokspawn
Copy link
Contributor

/retest-required

1 similar comment
@grokspawn
Copy link
Contributor

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

3 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@grokspawn
Copy link
Contributor

/retest-required

@dtfranz
Copy link
Contributor

dtfranz commented Aug 12, 2025

/test e2e-gcp-olm

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b1fb5e0 and 2 for PR HEAD 98387bd in total

@grokspawn
Copy link
Contributor

/override e2e-gcp-olm
These failures are due to issues with the test suite, not this PR.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 13, 2025

@grokspawn: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • e2e-gcp-olm

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-gcp-console-olm
  • ci/prow/e2e-gcp-olm
  • ci/prow/e2e-gcp-olm-flaky
  • ci/prow/e2e-gcp-ovn
  • ci/prow/e2e-upgrade
  • ci/prow/images
  • ci/prow/periodics-images
  • ci/prow/unit-api
  • ci/prow/unit-olm
  • ci/prow/unit-psm
  • ci/prow/unit-registry
  • ci/prow/verify
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-console-olm
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-olm
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-olm-flaky
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-ovn
  • pull-ci-openshift-operator-framework-olm-main-e2e-upgrade
  • pull-ci-openshift-operator-framework-olm-main-images
  • pull-ci-openshift-operator-framework-olm-main-periodics-images
  • pull-ci-openshift-operator-framework-olm-main-unit-api
  • pull-ci-openshift-operator-framework-olm-main-unit-olm
  • pull-ci-openshift-operator-framework-olm-main-unit-psm
  • pull-ci-openshift-operator-framework-olm-main-unit-registry
  • pull-ci-openshift-operator-framework-olm-main-verify
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override e2e-gcp-olm
These failures are due to issues with the test suite, not this PR.

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-sigs/prow repository.

@grokspawn
Copy link
Contributor

/override ci/prow/e2e-gcp-olm

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 13, 2025

@grokspawn: Overrode contexts on behalf of grokspawn: ci/prow/e2e-gcp-olm

In response to this:

/override ci/prow/e2e-gcp-olm

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-sigs/prow repository.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 13, 2025

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-olm 98387bd link true /test e2e-gcp-olm

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ankitathomas ankitathomas Awaiting requested review from ankitathomas

@dinhxuanvu dinhxuanvu Awaiting requested review from dinhxuanvu

@Xia-Zhao-rh Xia-Zhao-rh Awaiting requested review from Xia-Zhao-rh

Assignees

@bandrade bandrade

@jianzhangbjz jianzhangbjz

@openshift-ci-robot openshift-ci-robot

@emmajiafan emmajiafan

@kuiwang02 kuiwang02

@Xia-Zhao-rh Xia-Zhao-rh

@KeenonLee KeenonLee

@grokspawn grokspawn

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. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.