[jbosstools-issues] [JBoss JIRA] (JBIDE-23263) CDK docker registry is filled for an existing OpenShift 3 connection

Martin Malina (JIRA) issues at jboss.org
Tue Nov 15 05:23:01 EST 2016


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

Martin Malina closed JBIDE-23263.
---------------------------------


Verified in devstudio-10.2.0.GA-v20161115-0558-B6461-installer-standalone.jar
What I did:
1. Start CDK and wait for OpenShift connection to be created
2. Edit the OpenShift connection to remove the registry
3. Restart CDK in Servers view
4. Check that the registry has been added in the OpenShift connection details again

> CDK docker registry is filled for an existing OpenShift 3 connection
> --------------------------------------------------------------------
>
>                 Key: JBIDE-23263
>                 URL: https://issues.jboss.org/browse/JBIDE-23263
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: cdk
>    Affects Versions: 4.4.1.Final
>            Reporter: Marián Labuda
>            Assignee: Rob Stryker
>              Labels: openshift_v3
>             Fix For: 4.4.2.AM3
>
>
> If I already have an existing OpenShift 3 connection, which would have been otherwise created by starting CDK server adapter, an the connection does not have filled CDK docker registry URL, then the field for registry is still empty even after successful start of CDK server adapter. I would like to have the registry URL filled for an existing connection.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)



More information about the jbosstools-issues mailing list