[jbosstools-issues] [JBoss JIRA] (JBIDE-25046) Can't find CDK for registry discovery when 2 connections are defined for CDK

[Jeff MAURY (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-25046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465445#comment-13465445 ] 

Jeff MAURY commented on JBIDE-25046:
------------------------------------

Side note: if the admin connection is created after the CDK server has been started, then the discover will work.

> Can't find CDK for registry discovery when 2 connections are defined for CDK
> ----------------------------------------------------------------------------
>
>                 Key: JBIDE-25046
>                 URL: https://issues.jboss.org/browse/JBIDE-25046
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.5.1.AM2
>            Reporter: Jeff MAURY
>            Assignee: Rob Stryker
>              Labels: cdk, cdk_server_adapter_, explorer, openshift, openshift_v3
>             Fix For: 4.5.x
>
>
> EXEC: define an Openshift connection for CDK/admin
> EXEC: define an Openshift connection for CDK/developer
> EXEC: define a CDK3 server
> EXEC: start the CDK 3 server
> ASSERT: the CDK/admin OS3 connection is updated (registry not empty)
> ASSERT:  the CDK/developer OS3 connection is not updated (registry empty)
> EXEC: on the CDK/developer OS3 connection, click the DIscover buttoon
> ASSERT: the registry URL is updated, not the error dialog is displayed



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