Skip to content

[release-4.22] OU-1360: reset queries when namespace changes in dev perspective#934

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-932-to-release-4.22
May 13, 2026
Merged

[release-4.22] OU-1360: reset queries when namespace changes in dev perspective#934
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-932-to-release-4.22

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #932

/assign PeterYurkovich

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 12, 2026

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OU-1315

Details

In response to this:

This is an automated cherry-pick of #932

/assign PeterYurkovich

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 etmurasaki and jgbernalp May 12, 2026 17:01
@PeterYurkovich
Copy link
Copy Markdown
Contributor

/retest

@PeterYurkovich
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 12, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 12, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@PeterYurkovich
Copy link
Copy Markdown
Contributor

/cherry-pick release-4.21

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 12, 2026
@openshift-cherrypick-robot
Copy link
Copy Markdown
Author

@PeterYurkovich: once the present PR merges, I will cherry-pick it on top of release-4.21 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.21

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.

@PeterYurkovich
Copy link
Copy Markdown
Contributor

PeterYurkovich commented May 12, 2026

/retitle [release-4.22] OU-1360: reset queries when namespace changes in dev perspective

@openshift-ci openshift-ci Bot changed the title [release-4.22] OU-1315: reset queries when namespace changes in dev perspective [release-4.22] OU-1360: reset queries when namespace changes in dev perspective May 12, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 12, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 12, 2026

@openshift-cherrypick-robot: This pull request references OU-1360 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "openshift-5.0" instead.

Details

In response to this:

This is an automated cherry-pick of #932

/assign PeterYurkovich

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.

@PeterYurkovich
Copy link
Copy Markdown
Contributor

/jira-refresh

@PeterYurkovich
Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 12, 2026

@PeterYurkovich: This pull request references OU-1360 which is a valid jira issue.

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.

@PeterYurkovich
Copy link
Copy Markdown
Contributor

/label qe-approved
QE performed on main. 4.22 has not diverged from main significantly enough to require additional testing

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label May 12, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD f3f3c19 and 2 for PR HEAD 9ac25a7 in total

@PeterYurkovich
Copy link
Copy Markdown
Contributor

/retest

@jgbernalp
Copy link
Copy Markdown
Contributor

/test e2e-aws-ovn

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 13, 2026

@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 cf64033 into openshift:release-4.22 May 13, 2026
8 checks passed
@openshift-cherrypick-robot
Copy link
Copy Markdown
Author

@PeterYurkovich: new pull request created: #940

Details

In response to this:

/cherry-pick release-4.21

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.

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

4 participants