Sync test script code for KUBECONFIG related operation on prow

[amitkrout]

/kind feature
/kind code-refactoring

Which functionality do you think we should add?

kubectl will prevent multiple concurrent writes to the configuration file: it uses a config.lock file and if the lock exists then changes to the configuration file are prevented which has been fixed in the pr #3041.

Now to make the test code in the same logic need to be implemented for OpenShift cluster, however it does not looks straight forward when running it on prow. I can see different type of failure even after implementing the suggestion given on pr #3041. So i am creating a separate issue make the code in sync for both OpenShift and Kubernetes cluster type.

NOTE: Our existing test code is not broken, actually the --project flag which is saving us from the failure against multiple concurrent writes to the KUBECONFIG configuration file.

Discussion thread - #3041 (comment)

Why is this needed?

Code refactoring and ofcourse syncing of test code for OpenShift and Kubernetes cluster type.

[prietyc123]

I have tried out multiple fixes but It seems something fishy happening on prow. @kadel has also given some suggestions on this in comment but it also leads to failure

Again I can see the KUBECONFIG file exported from /tmp/admin.kubeconfig on prow and I tried hardcoding the path just to check where it is getting stuck. Again unexpected failure

In both the cases I observed KUBECONFIG gets copied and set to the temporary config but I am not sure about the behavior of the test. Though our tests are working as expected on travis CI with both kubernetes and openshift cluster. So, It should not be the test related problem. I suspect this could be infra related issue.

Anyway I am going to do a workaround in separate pr in this sprint.

[amitkrout]

closing it on behalf of #3221.