Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-22767

Deploy Docker Wizard: Create image stream contains wrong tags in some cases

    XMLWordPrintable

Details

    • Hide

      ASSERT: Have an OpenShift 3 account and project. Have a docker connection.
      EXEC: Open Deploy Image to OpenShift wizard (e.g. from context menu of a project in OpenShift Explorer "Deploy Docker Image...").
      EXEC: Fill in image "docker.io/openshift/hello-openshift:v1.2.1" and proceed through wizard.
      EXEC: Finish the wizard.
      EXEC: Check created Image Stream (select a project in OpenShift explorer view and select in tabbed properties in properties view Image Streams, then open its context menu and select Edit... and see content of opened editor).

      RESULT: There are plenty of tags and none of them is the desired one (v1.2.1).
      EXPECTED RESULT: There should be defined image with the tag v1.2.1.

      Show
      ASSERT: Have an OpenShift 3 account and project. Have a docker connection. EXEC: Open Deploy Image to OpenShift wizard (e.g. from context menu of a project in OpenShift Explorer "Deploy Docker Image..."). EXEC: Fill in image "docker.io/openshift/hello-openshift:v1.2.1" and proceed through wizard. EXEC: Finish the wizard. EXEC: Check created Image Stream (select a project in OpenShift explorer view and select in tabbed properties in properties view Image Streams, then open its context menu and select Edit... and see content of opened editor). RESULT: There are plenty of tags and none of them is the desired one (v1.2.1). EXPECTED RESULT: There should be defined image with the tag v1.2.1.

    Description

      In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...).

      Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image.

      Consequences of this issue are no pods created once the deploy image to OpenShift is finished. User has to manually trigger Deploy Latest from context menu of a deployment configuration to spin up an application pod.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-22915 Deploy Docker Image: Replication controller is not created for some images

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              mlabuda_jira Marián Labuda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: