[ https://issues.jboss.org/browse/JBIDE-25159?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25159: ------------------------------------- Description: # ASSERT: have *cdk 3.1.1* installed and running # ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent* # EXEC: install cdk 3.2.0.alpha1 and launch it # ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1) # ASSERT: *DONT* delete the server adapter for it # EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app # EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu. Result: The server adapter wizard doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk. !image-2017-10-06-15-23-43-428.png! Expected result: The server adapter wizard should show up. The existing server adapter is not matching the service that is selected in the explorer. was: # ASSERT: have *cdk 3.1.1* installed and running # ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent* # EXEC: install cdk 3.2.0.alpha1 and launch it # ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1) # ASSERT: *DONT* delete the server adapter for it # EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app # EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu. Result: The server adapter doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk. !image-2017-10-06-15-23-43-428.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)