Attempt to create the che project multiple times if it was previously deleted.

[metlos]

Each attempt waits exponentially longer before retry.

This should enable us to redeploy che using just a single invocation of deploy_che.sh.

[sleshchenko]

Does it fix #10409 ?

[skabashnyuk]

Can you explain the issue (usecase) and the way how you fix it? In general.

[metlos]

Does it fix #10409 ?

Yes, in a slightly different way than originally - the wait time exponentially increases between each attempt (which I'm not sure is ideal but it works)

Can you explain the issue (usecase) and the way how you fix it? In general.

$ oc delete project X
$ sleep 5
$ oc get project X
... nothing returned
$ oc new-project X
AlreadyExists exception

The way to fix it is just to retry a couple of times. A first attempt is performed immediately, the second after 2 seconds, the third 4 seconds after that, the fourth 8 seconds after the third and the fifth 16 seconds after the fourth.

[amisevsk]

I've seen this problem when just trying to use minishift in general; the time between a project being 'deleted' as in removed from visible projects to when all resources in the project are cleaned up can be significant.

[sleshchenko]

One comment:

The way to fix it is just to retry a couple of times. A first attempt is performed immediately, the second after 2 seconds, the third 4 seconds after that, the fourth 8 seconds after the third and the fifth 16 seconds after the fourth.

Is it needed to increase waiting time between attempts? Maybe it would be more clear and simpler like wait for delete project 1 minute (check every few seconds 2-5).
I just wonder what is a probability that namespace will be removed during first tries? I assume quite small. Then in most of cases script will wait 16 seconds without any check even if a namespace is already removed? Waiting time can be smaller and the cost of it - one request per few seconds, which I believe won't hurt any OS installation or desktop.

[metlos]

ci-build