[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)

[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25049: ------------------------------------- Description: # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry. {code} [adietish@localhost minishift]$ ./minishift openshift registry No information found for 'service/docker-registry' {code} You can achieve that by 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 restart 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 was: # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry. {code} [adietish@localhost minishift]$ ./minishift openshift registry No information found for 'service/docker-registry' {code} You can achieve that by logging into your cdk with oc as "admin" and then: {code} oc project default oc delete svc docker-registry {code} # 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.2.3#72005)