[jbosstools-issues] [JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
Andre Dietisheim (JIRA)
issues at jboss.org
Thu Apr 5 13:00:00 EDT 2018
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Sprint: devex #147 April 2018
> 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.Final
>
> 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)
More information about the jbosstools-issues
mailing list