Hide Forgot
Description of problem: if specifying --config in oc new-app --search with an invalid option, the order of where to put the --config option makes a difference to the returned output Looks like the order where I put --config matters in this case. *** put --config at the end of cmd line oc new-app --search --docker-image --config=/home/pruan/workdir/dhcp-16-164-pruan/ose_pruan1.kubeconfig [ruby-2.2.3] error: No configuration file found, please login or point to an existing file: 1. Via the command-line flag --config 2. Via the KUBECONFIG environment variable 3. In your home directory as ~/.kube/config To view or setup config directly use the 'config' command. *** put --config at the middle of the cmd line $ oc new-app --config=/home/pruan/workdir/dhcp-16-164-pruan/ose_pruan1.kubeconfig --search --docker-image Error: flag needs an argument: --docker-image Version-Release number of selected component (if applicable): oc v1.1.3-40-g678463c kubernetes v1.2.0-alpha.7-703-gbc4550d How reproducible: always. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is working correctly. --docker-image needs an additional argument. Since you aren't specifying an actual image, the --config=foo is being treated as that additional argument. Since --config=foo was consumed as the argument to --docker-image, you are not supplying a --config argument, so you get an error that there is no configuration.
(and of course in the second case you're correctly being told that you need to specify an additional argument to --docker-image)