Skip to content

[release-4.17] OCPBUGS-55756: update the Deployment pod on change in imageStream #15022

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
Merged
openshift-merge-bot merged 1 commit into from
May 27, 2025
Merged

[release-4.17] OCPBUGS-55756: update the Deployment pod on change in imageStream #15022

openshift-merge-bot merged 1 commit into from
May 27, 2025

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented May 6, 2025

This is an automated cherry-pick of #14757

/assign vikram-raj

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request May 6, 2025
Merged
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 6, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-50609 has been cloned as Jira Issue OCPBUGS-55756. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-55756: update the Deployment pod on change in imageStream

Details

In response to this:

This is an automated cherry-pick of #14757

/assign vikram-raj

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.17] OCPBUGS-50609: update the Deployment pod on change in imageStream [release-4.17] OCPBUGS-55756: update the Deployment pod on change in imageStream May 6, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 6, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 6, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-55756, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state New, 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-50609 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-50609 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

Requesting review from QA contact:
/cc @sanketpathak

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 #14757

/assign vikram-raj

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 added the component/dev-console Related to dev-console label May 6, 2025
vikram-raj
vikram-raj reviewed May 20, 2025
View reviewed changes
Copy link
Member

@vikram-raj vikram-raj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label backport-risk-assessed

/approve

@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 May 20, 2025
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 20, 2025
@vikram-raj
Copy link
Member

vikram-raj commented May 20, 2025

/retest

vikram-raj
vikram-raj reviewed May 22, 2025
View reviewed changes
Copy link
Member

@vikram-raj vikram-raj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

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

openshift-ci bot commented May 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@sanketpathak
Copy link
Contributor

sanketpathak commented May 22, 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 May 22, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 22, 2025

/retest-required

Remaining retests: 0 against base HEAD b93b13b and 2 for PR HEAD 5cd24d0 in total

@vikram-raj
Copy link
Member

vikram-raj commented May 22, 2025

/cherry-pick release-4.16

@openshift-cherrypick-robot
Copy link
Author

openshift-cherrypick-robot commented May 22, 2025

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

Details

In response to this:

/cherry-pick release-4.16

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

openshift-ci-robot commented May 26, 2025

/retest-required

Remaining retests: 0 against base HEAD b93b13b and 2 for PR HEAD 5cd24d0 in total

2 similar comments
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 26, 2025

/retest-required

Remaining retests: 0 against base HEAD b93b13b and 2 for PR HEAD 5cd24d0 in total

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 27, 2025

/retest-required

Remaining retests: 0 against base HEAD b93b13b and 2 for PR HEAD 5cd24d0 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 27, 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 f9c412e into openshift:release-4.17 May 27, 2025
6 checks passed
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 27, 2025

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

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

Details

In response to this:

This is an automated cherry-pick of #14757

/assign vikram-raj

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-cherrypick-robot
Copy link
Author

openshift-cherrypick-robot commented May 27, 2025

@vikram-raj: new pull request created: #15091

Details

In response to this:

/cherry-pick release-4.16

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-cherrypick-robot openshift-cherrypick-robot mentioned this pull request May 27, 2025
Merged
@openshift-bot
Copy link
Contributor

openshift-bot commented May 27, 2025

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-console
This PR has been included in build openshift-enterprise-console-container-v4.17.0-202505271106.p0.gf9c412e.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented May 28, 2025

Fix included in accepted release 4.17.0-0.nightly-2025-05-28-095050

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

Reviewers

@sanketpathak sanketpathak Awaiting requested review from sanketpathak

@lokanandaprabhu lokanandaprabhu Awaiting requested review from lokanandaprabhu

1 more reviewer

@vikram-raj vikram-raj vikram-raj left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@gouyang gouyang

@vikram-raj vikram-raj

@jrichter1 jrichter1

@ebenahar ebenahar

@yanpzhan yanpzhan

@sanketpathak sanketpathak

@juzhao juzhao

@lihongyan1 lihongyan1

@XiyunZhao XiyunZhao

@Tai-RedHat Tai-RedHat

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. component/dev-console Related to dev-console jira/severity-low Referenced Jira bug's severity is low 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.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.