[jbosstools-issues] [JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-4070: ---------------------------------------- So the 1st possible explanation of using EAP5 inapplicable. The screenshots in the doc clearly show OpenShift3 and an OpenShift 3 server adapter being used. The rsync output that's reported shows other weird things: One can see a ROOT.war and a ROOT.EAR being deployed (./ROOT.war, .deploy/ROOT.ear/SimpleHelloWorld.war/Hello.jsp, deploy/ROOT.war etc.) I also suspect that the output being shown does not report the output as is. The deployment is actually happening in 2 phases: # First, the remote is synced down to the local machine # Then, in a 2nd phase, the local machine is synced back up to the remote pod. The 2nd thing to take care of is that existing contents are being mixed in, since we're rsyncing. So the more you deploy the more things might get mixed up. I also suspect "Clean" in the server adapter not to really clear contents [~rob.stryker] correct?). Is it possible for the user to manually clear his deployment folder on the pod and the local Eclipse? * to clear the pod: use the [oc command line tool|https://github.com/openshift/origin/releases/tag/v1.3.0] to login into the pod and rm the deployment folder # oc login https://ose-masterint.mmm.com:8443 # oc project ostestrest # oc get pod # oc rsh <pod running your eap> => you get into a shell in your pod # cd /deployments # rm -rf * * to clear the local deployments folder: # remove the server adapter ([~rob.stryker] this should clear the local artifacts that were synced pod > local, correct?) Once both have been cleared please redeploy and paste the output completely untouched as-is (dont cut off anything), please. I'd love the user to use our latest builds. Could he use an Eclipse Neon and install [JBoss Tools/OpenShift 4.4.2.AM3|http://tools.jboss.org/downloads/jbosstools/neon/4.4.2.AM3.html] into it? We should also make sure the user is using the latest oc binaries that match his openshift version. What version of OpenShift server is being used? The user should use the [oc binaries|https://github.com/openshift/origin/releases] in a version that match the server. Is it possibel to get the projects that the user is using? It would be a great help to have these artifacts, far more efficient that doing guesswork based on screenshots and explanations. Those help, no doubt, but real hands-on is far superior. -- This message was sent by Atlassian JIRA (v7.2.3#72005)