[jbosstools-issues] [JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)

[Ondrej Dockal (JIRA)]

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

Ondrej Dockal closed JBIDE-25049.
---------------------------------


> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though  both are started)
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-25049
>                 URL: https://issues.jboss.org/browse/JBIDE-25049
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk, openshift
>    Affects Versions: 4.5.0.AM2
>            Reporter: Andre Dietisheim
>            Assignee: Rob Stryker
>            Priority: Minor
>              Labels: connection_wizard, openshift_v3
>             Fix For: 4.5.1.AM3
>
>         Attachments: discover_openshift_registry.png, screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish at localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> You can achieve that by :
> * have server adapter stopped, minishift started
> * logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc docker-registry
> {code}
> Once the service is deleted you need to start the cdk.
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
>  !screenshot-1.png! 
>  
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)