Bug 1330845

Description of problem:
Using "oc set probe" command to set a probe in dc, when set an exec action(-- cmd) as a  probe in front of other options, other options will be a part of exec action, not independent option. 
Better to enhance usage info, like :  oc exec [options] POD [-c CONTAINER] -- COMMAND [args...]


Version-Release number of selected component (if applicable):
openshift v3.2.0.20
kubernetes v1.2.0-36-g4a3f9c5
etcd 2.2.5

How reproducible:
Always

Steps to Reproduce:
1.Create a project, and create a dc
2.set an exec action(-- cmd) as a  probe in front of other options,
$ oc set probe dc/mysql --liveness -- echo ok --period-seconds=20
3.when pod is running, check the probe in pod
$ oc describe pod mysql-2-tx02a

Actual results:
In step3:
 Liveness:		exec [echo ok --period-seconds=20] delay=0s timeout=1s period=10s #success=1 #failure=3

Expected results:
 Liveness:		exec [echo ok] delay=0s timeout=1s period=20s #success=1 #failure=3

Additional info:
when set an exec action(-- cmd) behind other options, like:$ oc set probe dc/mysql --liveness --period-seconds=20 -- echo ok , the result will be correct.