Skip to content
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.

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

OCPBUGS-43061: update the Deployment pod on change in imageStream #14523

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vikram-raj
Copy link
Member

Fixes: https://issues.redhat.com/browse/OCPBUGS-43061

Descriptions:

  • When the ImageStreamTag is updated, the pod does not automatically reflect the new image for Deployments created via the OpenShift Console. As in trigger annotation boolean value for paused is set as a string.
OCPBUGS-43061.mov

@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 Nov 21, 2024
@openshift-ci-robot
Copy link
Contributor

@vikram-raj: This pull request references Jira Issue OCPBUGS-43061, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Fixes: https://issues.redhat.com/browse/OCPBUGS-43061

Descriptions:

  • When the ImageStreamTag is updated, the pod does not automatically reflect the new image for Deployments created via the OpenShift Console. As in trigger annotation boolean value for paused is set as a string.
OCPBUGS-43061.mov

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 yapei November 21, 2024 10:05
@vikram-raj
Copy link
Member Author

/cc @lokanandaprabhu

Copy link
Contributor

openshift-ci bot commented Nov 21, 2024

@vikram-raj: 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/okd-scos-e2e-aws-ovn 1824081 link false /test okd-scos-e2e-aws-ovn

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.

Copy link
Contributor

@lokanandaprabhu lokanandaprabhu left a comment

Choose a reason for hiding this comment

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

Hi @vikram-raj ,

I have checked in both 4.18 latest nightly and 4.16 cluster, if I change imageStream it is getting reflected with paused value equal to "false" . I feel like issue is something else based on the document attached in ticket - https://docs.google.com/document/d/1Ob7D6BCMg_UZGnwpVNzHWumkkN782CU-Xc1TC09adAk/edit?tab=t.0

Screen.Recording.2024-11-22.at.12.45.07.PM.mov
Screen.Recording.2024-11-22.at.12.36.41.PM.mov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants