time-out errors while deleting deployments on openshift

[ashetty1]

I see time-out errors while deleting deployments. This is with openshift. Could someone tell me why I am seeing these warning messages when the deployments seem to be successfully deleted.

$ kompose --file docker-guestbook.yml down
INFO[0000] Successfully deleted service: frontend       
WARN[0060] Can't delete deployment: frontend due to 'timed out waiting for the condition' 
INFO[0060] Successfully deleted service: redis-master   
WARN[0120] Can't delete deployment: redis-master due to 'timed out waiting for the condition' 
INFO[0120] Successfully deleted service: redis-slave    
WARN[0180] Can't delete deployment: redis-slave due to 'timed out waiting for the condition'

[ngtuna]

@surajssd @kadel could you check it with an Openshift environment?

[surajssd]

@ashetty1

• What is the version of openshift you are using?
• How did you deploy this particular example on openshift?

[surajssd]

@ashetty1 So I did this, with my openshift cluster running:

$ kompose --file docker-guestbook.yml up
We are going to create Kubernetes deployments and services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'kubectl create -f' commands instead. 

INFO[0000] Successfully created service: frontend       
INFO[0000] Successfully created service: redis-master   
INFO[0000] Successfully created service: redis-slave    
INFO[0000] Successfully created deployment: frontend    
INFO[0000] Successfully created deployment: redis-master 
INFO[0000] Successfully created deployment: redis-slave 

Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods' for details.

And once it was successfully deployed I did this, which successfully deleted all the components:

$ kompose --file docker-guestbook.yml down                                                                                                                                           
INFO[0000] Successfully deleted service: redis-slave    
INFO[0003] Successfully deleted deployment: redis-slave 
INFO[0003] Successfully deleted service: frontend       
INFO[0006] Successfully deleted deployment: frontend    
INFO[0006] Successfully deleted service: redis-master   
INFO[0009] Successfully deleted deployment: redis-master 

And the version of openshift I am using:

$ oc version
oc v1.3.0
kubernetes v1.3.0+52492b4
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://127.0.0.1:8443
openshift v1.3.0
kubernetes v1.3.0+52492b4

So basically what happened here is kompose did talk to kubernetes running underneath openshift directly, so everything we saw above is kubernetes, not openshift. I doubt if deployments are directly supported by openshift origin 1.2.

[ashetty1]

@surajssd will try and update soon.

[ngtuna]

Any update @ashetty1 ?

[ashetty1]

@surajssd what you said made sense. We could close this bug now.