Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-2550

On seamless update of image stream tag the status of Web server is not updated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • Operator.2.0.0.GA
    • None
    • None
    • False
    • None
    • False
    • Hide
      1. create web server with existing image stream.
      2. - oc describe webserver/image-stream-test 
      3. - oc get pods
      4. update the image stream with new image (or add new tag)    - oc tag quay.io/$user/my-image-name-war my-image-name-imagestream:latest --scheduled
      5. - oc get pods to check that there are new pods created in the container
      6. - oc describe webserver/image-stream-testyou will see that the pods described are still the same as in step 2. 
      Show
      create web server with existing image stream. - oc describe webserver/image-stream-test  - oc get pods update the image stream with new image (or add new tag)    - oc tag quay.io/$user/my-image-name-war my-image-name-imagestream:latest --scheduled - oc get pods to check that there are new pods created in the container - oc describe webserver/image-stream-testyou will see that the pods described are still the same as in step 2. 

      When updating imagestream with new image the Operator in order to update the application, delete the existing pods and create new ones, updated in their place. The problem is that in the Webserver yaml, in status section, remains the original pods description. 

              rh-ee-vmouriki Vasileios Mourikis (Inactive)
              ktsagara@redhat.com Katerina Tsagaraki (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: