[ https://issues.jboss.org/browse/JBIDE-21579?page=com.atlassian.jira.plugi... ] Xia Zhao updated JBIDE-21579: ----------------------------- Steps to Reproduce: Steps to Reproduce: 1. Login openshift with JBT 2. Go into a project 3. Right click on a service Actual Result: Not able to delete service Expected Result: Should be able to delete service Additional info: This is a regression introduced by the new changes on JBT property view was: 1. Prepare 2 applications which will deliver different HTML outputs on a same port 8080. Say pod1 in project1 will reurn string "I'm A" if you curl http://127.0.0.1/8080 after a successful port-forward operation, and pod2 in project2 will reutrn string "I'm B" if you curl http://127.0.0.1/8080 after a successful port-forward operation. (Let me know if you need the detailed application json files for these 2 projects) 2. Deploy these 2 applications sepereately into project1 and project2 of openshift 3. Login openshift with JBT (I used Jboss Developer Studio on Mac OS) 4. Inside JBT, go to project1, right click on pod1 (when this pod is running healty), port-forward it to local port 8080 --> This is used to make local 8080 port is now in use 5. curl http://127.0.0.1/8080, should return string "I'm A" in the result HTML file 6. If you go back to JBT, close the port-forward window in step #4, and revisit it , should still see from UI that port forwarding is in process 7. Now go to project2, right click on pod2 (when this pod is running healty), port-forward it to local port 8080 --> This should not be success since port 8080 is already in use, but no error message is popped up, and the Port Forward wizard pretended to be succeeded. 8. Close the port-forward window in step7, and revisit it for the 2nd time now, we can see from the UI that port forwarding is ended. 9. curl http://127.0.0.1/8080, still return string "I'm A" in the result HTML file, this means the port forward in step4 is still taking effect, and the attempt in step 6 had failed, this is the expected result here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)