[jbosstools-issues] [JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata if image is not pulled to a docker connection

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-22916:
-------------------------------------
    Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1345


> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata if image is not pulled to a docker connection
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22916
>                 URL: https://issues.jboss.org/browse/JBIDE-22916
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.1.AM3
>            Reporter: Marián Labuda
>            Assignee: Jeff MAURY
>              Labels: deploy_docker_wizard, openshift_v3
>             Fix For: 4.4.2.AM2
>
>         Attachments: 2016-09-06 at 14-19-31.mp4
>
>
> When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest".
> You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)