Space Deletion Function is not reliably deleting OpenShift resources

[ldimaggi]

As of today, human users and automated tests do not have a reliable way to remove a space, and all of its related OpenShift resources. The users/tests are able to work-around this by performing an environment reset, but this is problematic as the reset intermittently results in some resources not restarting. For example, issue #4598 describes an intermittent problem where Jenkins is not accessible after an environment reset.

In addition, the environment reset is a does not give the user fine-grained control over its actions. It is a destructive function that intentionally removes ALL user resources and restarts the user's pods. If a user wants to remove all resources associated with a single space, but not all resources associated with other spaces, then he/she cannot use the environment reset feature.

For automated tests, the environment reset function is also not reliable as after the reset, there are intermittent problems with Jenkins not starting. If a human user encounters this problem, the workaround is to reset the environment a second time. For automated tests, its less practical to reset the environment a variable number of times.

A reliable space deletion function that also removes all associated OpenShift resources is preferable for both human users and automated tests.

Related issues:
#4121
#4598
#4656

[christianvogt]

This is also important for devs to run e2e tests with their own accounts. We encourage devs to run e2e tests and also fix them up. However if they need to always reset their env it's a big ask depending on the setup they already have. It would best to have a cleaner solution.

[pmacik]

A reliable space deletion function that also removes all associated OpenShift resources is preferable for both human users and automated tests.

In addition, all the corresponding Che workspaces from the space's codebases should be removed as well.

[ldimaggi]

Will the fix to this issue:
fabric8-services/fabric8-tenant#710

Also solve our env reset issues?
@MatousJobanek

[ljelinkova]

If I understand it correctly, the reset of environment calls delete on all spaces. That means that if delete space does not work properly, the reset of environment does not work either.

That is why it is so annoying to have an issue like this where delete space does not delete Che workspaces.

#4559

It means we need to manually delete all che workspaces for all our testing accounts periodically (every few weeks) otherwise the Che tests stop to work properly.

Another issue is that neither work items are deleted

#4382

BTW, I do not think this is a feature request, the space deletion is broken and should be fixed.

[ppitonak]

Pipelines are not removed on space delete, too #3802