Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-55756

Deployment created via OCP console fails to trigger on Imagestream change

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.17.z
    • 4.16
    • Dev Console
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • Low
    • None
    • None
    • Rejected
    • ODC Sprint 3274, ODC Sprint 3275
    • 2
    • Done
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-50609. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-43061. The following is the description of the original issue:
      —
      Description of problem:

      When the ImageStreamTag is updated, the pod does not reflect the new image automatically for Deployments created via the OpenShift Console.

      Version-Release number of selected component (if applicable):

      Red Had Openshift Container Platform

      Steps to Reproduce:

          1. Create a Deployment via OpenShift console and check that the trigger annotation has a `paused` field as string (e.g., `"paused":"false"`) instead of a boolean value  (e.g., `"paused":false`)
    2. Make changes on the ImageStreamTag

      Actual results:

      No changes on the deployment or new Pods created.

      Expected results:

      The deployment should have the new changes of the ImageStreamTag.

              viraj-1 Vikram Raj
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Sanket Pathak Sanket Pathak
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: