On 01/08/2016 10:17 PM, Philippe Lafoucrière wrote:
On Fri, Jan 8, 2016 at 4:12 PM, David Eads <de...@redhat.com> wrote:
Before you delete again, can you create a gist of job yaml so we can see
what's exploded?
There's ~5000 lines like
- lastProbeTime: 2016-01-08T18:48:51Z
lastTransitionTime: 2016-01-08T18:48:51Z
status: "True"
type: Complete
I'll have a look at status update, maybe we have a bug there.
Anyway thanks pointing us to that!
Maciej
Try `oc delete job/thejob --cascade=false --loglevel=6`. That should avoid
any reaping waits and provide some debug info if it still doesn't work.
Once that happens, you will be left with cleaning up the rest of what the
job created by hand.
You saved our day :)
The job is gone now.
Thanks David
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
