[jbosstools-issues] [JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change
Xavier Coulon (JIRA)
issues at jboss.org
Tue Mar 15 05:54:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176903#comment-13176903 ]
Xavier Coulon commented on JBIDE-21815:
---------------------------------------
scenario that works:
- select an image that was already pulled
- click {{next}} and verify that the environment variables match the given image
- click {{back}} and select another image, even not already pulled
- click again {{next}} and verify that the environment variables match the new given image -> OK
scenario that fails:
- select an image that was +*not*+ already pulled
- click {{next}} and verify that the environment variables match the given image
- click {{back}} and select another image, that was already pull
- click again {{next}} and verify that the environment variables match the new given image -> FAIL
> Image metadata not refreshed after name change
> ----------------------------------------------
>
> Key: JBIDE-21815
> URL: https://issues.jboss.org/browse/JBIDE-21815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> Steps to reproduce:
> - open the *Deploy Docker Image* wizard
> - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}}
> - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again.
> - ASSERT: the metadata should have been updated
> - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list