[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25670: ------------------------------------- Description: This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online: steps: # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent) # EXEC: launch "Delete Resources" wizard # ASSERT: you see deployment configs, replication controllers, pods etc. # EXEC: select all resources and hit "Finish" # ASSERT: wait for all removal jobs to be finished # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there Result: !image-2018-01-29-09-34-08-598.png! Replication controller(s) and pods are left in place, they were not deleted. Some pods may be in terminating state and disappear eventually. was: This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online: steps: # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent) # EXEC: launch "Delete Resources" wizard # ASSERT: you see deployment configs, replication controllers, pods etc. # EXEC: select all resources and hit "Finish" # ASSERT: wait for all removal jobs to be finished # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there Result: !image-2018-01-29-09-34-08-598.png! Replication controller(s) and pods are left in place, they were not deleted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)