Skip to content

[release-4.16] OCPBUGS-57429: reduce cache expiry frequency [release-4.19]#1022

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.16from
openshift-cherrypick-robot:cherry-pick-1019-to-release-4.16
Jul 23, 2025
Merged

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

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jun 12, 2025

This is an automated cherry-pick of #1019

/assign openshift-ci-robot

@grokspawn
reduce cache expiriry frequency (#3591)
c4f5346 
Signed-off-by: grokspawn <jordan@nimblewidget.com>
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
Copy Markdown

openshift-ci-robot commented Jun 12, 2025

@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.16] OCPBUGS-57429: 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.16] OCPBUGS-57352: reduce cache expiry frequency [release-4.19] [release-4.16] OCPBUGS-57429: 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-ci-robot commented Jun 12, 2025

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

  • expected dependent Jira Issue OCPBUGS-57428 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.

@openshift-ci openshift-ci Bot requested review from dinhxuanvu and tmshort June 12, 2025 21:05
@grokspawn
Copy link
Copy Markdown
Contributor

grokspawn commented Jun 17, 2025

/retest-required

2 similar comments
@grokspawn
Copy link
Copy Markdown
Contributor

grokspawn commented Jun 27, 2025

/retest-required

@grokspawn
Copy link
Copy Markdown
Contributor

grokspawn commented Jun 30, 2025

/retest-required

@oceanc80
Copy link
Copy Markdown
Contributor

oceanc80 commented Jun 30, 2025

/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

grokspawn commented Jun 30, 2025

/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

grokspawn commented Jul 1, 2025

/retest-required

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor

Xia-Zhao-rh commented Jul 2, 2025

/retest

@grokspawn
Copy link
Copy Markdown
Contributor

grokspawn commented Jul 3, 2025

/retest-required

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor

Xia-Zhao-rh commented Jul 4, 2025

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Jul 4, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 4, 2025

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

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

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.

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor

Xia-Zhao-rh commented Jul 4, 2025

/label cherry-pick-approved

@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 Jul 4, 2025
@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor

Xia-Zhao-rh commented Jul 23, 2025

/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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 23, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 23, 2025

@Xia-Zhao-rh: This pull request references Jira Issue OCPBUGS-57429, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.z) matches configured target version for branch (4.16.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-57428 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-57428 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
  • bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

Details

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

@openshift-ci openshift-ci Bot requested a review from Xia-Zhao-rh July 23, 2025 01:10
@deepsm007
Copy link
Copy Markdown

deepsm007 commented Jul 23, 2025

/test okd-scos-images

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 23, 2025

@openshift-cherrypick-robot: all tests passed!

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 922674d into openshift:release-4.16 Jul 23, 2025
14 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 23, 2025

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

Jira Issue OCPBUGS-57429 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.

@grokspawn
Copy link
Copy Markdown
Contributor

grokspawn commented Jul 23, 2025

Thanks for the assist @deepsm007!

@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Jul 24, 2025

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.16.0-202507230505.p0.g922674d.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Jul 24, 2025

[ART PR BUILD NOTIFIER]

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

@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Jul 24, 2025

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.16.0-202507230505.p0.g922674d.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

Reviewers

@dinhxuanvu dinhxuanvu Awaiting requested review from dinhxuanvu

@tmshort tmshort Awaiting requested review from tmshort

@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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.