[
https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi...
]
Josef Kopriva edited comment on JBIDE-25670 at 2/13/18 6:39 AM:
----------------------------------------------------------------
Hi [~adietish], I have followed your steps, but after ~3 minutes, pod and replication
controllers are still there:
!Screenshot_20180213_123635.png|thumbnail!
One of error messages:
{code:java}
eclipse.buildId=11.3.0.AM1-v20180209-1312-B2027
java.version=1.8.0_161
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -data file:/home/jkopriva/devstudio_B2027_11.3.AM1_3/workspace/
-os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.tools.openshift.core
Error
Tue Feb 13 12:29:59 CET 2018
Error deleting Pod named nodejs-mongo-persistent-1-build.
com.openshift.restclient.NotFoundException: pods
"nodejs-mongo-persistent-1-build" not found pods
"nodejs-mongo-persistent-1-build" not found
at
com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:112)
at
com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:257)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:221)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:209)
at com.openshift.internal.restclient.DefaultClient.delete(DefaultClient.java:320)
at
org.jboss.tools.openshift.core.connection.Connection.deleteResource(Connection.java:545)
at
org.jboss.tools.openshift.internal.core.job.AbstractDeleteResourceJob.delete(AbstractDeleteResourceJob.java:45)
at
org.jboss.tools.openshift.internal.core.job.DeleteResourcesJob.lambda$0(DeleteResourcesJob.java:46)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at
org.jboss.tools.openshift.internal.core.job.DeleteResourcesJob.doRun(DeleteResourcesJob.java:47)
at
org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
was (Author: jkopriva):
Hi [~adietish], I have followed your steps, but after ~3 minutes, pod and replication
controllers are still there:
!Screenshot_20180213_123635.png|thumbnail!
Delete Resources: replication controllers and pods are not deleted
(on OpenShift Online)
----------------------------------------------------------------------------------------
Key: JBIDE-25670
URL:
https://issues.jboss.org/browse/JBIDE-25670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.2.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: delete_resources
Fix For: 4.5.3.AM1
Attachments: Screenshot_20180213_123635.png, image-2018-01-29-09-34-08-598.png
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.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)