Skip to content

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

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.15from
openshift-cherrypick-robot:cherry-pick-1019-to-release-4.15
Aug 13, 2025
Merged

[release-4.15] OCPBUGS-57430: reduce cache expiry frequency [release-4.19]#1023
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.15from
openshift-cherrypick-robot:cherry-pick-1019-to-release-4.15

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #1019

/assign openshift-ci-robot

Signed-off-by: grokspawn <jordan@nimblewidget.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: bf9ffe8b04b59e9acd859ac8a9b6698f1f2a3437
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

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
Copy Markdown

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

Details

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
Copy Markdown
Contributor

/retest-required

2 similar comments
@grokspawn
Copy link
Copy Markdown
Contributor

/retest-required

@grokspawn
Copy link
Copy Markdown
Contributor

/retest-required

@oceanc80
Copy link
Copy Markdown
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
Copy Markdown
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
Copy link
Copy Markdown
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

Details 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
Copy Markdown
Contributor

/retest-required

2 similar comments
@grokspawn
Copy link
Copy Markdown
Contributor

/retest-required

@grokspawn
Copy link
Copy Markdown
Contributor

/retest-required

@dtfranz
Copy link
Copy Markdown
Contributor

dtfranz commented Aug 4, 2025

/retest-required

3 similar comments
@dtfranz
Copy link
Copy Markdown
Contributor

dtfranz commented Aug 4, 2025

/retest-required

@dtfranz
Copy link
Copy Markdown
Contributor

dtfranz commented Aug 4, 2025

/retest-required

@dtfranz
Copy link
Copy Markdown
Contributor

dtfranz commented Aug 4, 2025

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

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

@dtfranz
Copy link
Copy Markdown
Contributor

dtfranz commented Aug 5, 2025

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown

/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
Copy Markdown

/retest-required

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

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

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

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

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

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

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

@grokspawn
Copy link
Copy Markdown
Contributor

/retest-required

1 similar comment
@grokspawn
Copy link
Copy Markdown
Contributor

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown

/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
Copy Markdown

/retest-required

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

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

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

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

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

@grokspawn
Copy link
Copy Markdown
Contributor

/retest-required

@dtfranz
Copy link
Copy Markdown
Contributor

dtfranz commented Aug 12, 2025

/test e2e-gcp-olm

@openshift-ci-robot
Copy link
Copy Markdown

/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
Copy Markdown

/retest-required

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

@grokspawn
Copy link
Copy Markdown
Contributor

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

@openshift-ci
Copy link
Copy Markdown
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.

Details

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
Copy Markdown
Contributor

/override ci/prow/e2e-gcp-olm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 13, 2025

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

Details

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
Copy link
Copy Markdown
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.

Details

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.

@openshift-merge-bot openshift-merge-bot Bot merged commit d793add into openshift:release-4.15 Aug 13, 2025
13 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-57430: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-57430 has been moved to the MODIFIED state.

Details

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-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.15.0-202508121235.p0.gd793add.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.15.0-202508121235.p0.gd793add.assembly.stream.el9.
All builds following this will include this PR.

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. 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

Development

Successfully merging this pull request may close these issues.