Description of problem: I have a PV which failed to be recycled. The error from OSE is: Message: Recycling error: Pod failed, pod.Status.Message unknown. This does not really give me any sort of indication as to what happened. The recycle pod was not alive long enough for me to actually look at its logs (it was created/failed and deleted in the span of about 2 seconds). Version-Release number of selected component (if applicable): oc v3.1.1.6-33-g81eabcc kubernetes v1.1.0-origin-1107-g4c8e6f4 How reproducible: Create a hostPath volume and add it as a PV, bind it to a project then release it. Steps to Reproduce: 1. Add HostPath PV 2. Use Metrics project and tell Cassandra to bind to it 3. Re-deploy the metrics infrastructure with REDEPLOY=true 4. See that the PV is in Failed mode Actual results: Failed to clean PV Expected results: Clean up of PV or better error message. Maybe error that points me to docker ps -a | grep $podname ? Additional info:
Is this same issue or a dupe of this: https://bugzilla.redhat.com/show_bug.cgi?id=1326881
They are two distinct issues. One (this one) is a problem with the error reporting of OSE as to what/why something failed. The other issue is an issue with the pv recycler. So maybe they are caused by the same problem but to me they are totally separate things.
Jan's changes to 1.3 with the binding code improved this error. Please revalidate. The operation executor might also improve this. Waiting on this to be merged.
Re-test please.
Please retest
Tested on below version, # openshift version openshift v3.4.0.16+cc70b72 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 "oc describe pv pv_name" show a descriptive Message and Events. So this bug is fixed. Once bug is QN_QA, we can move it to verified.
This has been merged into ose and is in OSE v3.4.0.17 or newer.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0066