Description of problem: The order of the argument matters when running oo-devel-node app-create. Why should it? Version-Release number of selected component (if applicable): current How reproducible: always. Steps to Reproduce: 1. oo-devel-node app-create --with-namespace case247269 --with-app-name case247269 --with-app-uuid 999999999999999999999999 --with-container-uuid 999999999999999999999999 2. 3. Actual results: [0mMissing --with-container-uuid UUID Usage: oo-devel-node app-create --with-container-uuid UUID --with-namespace NAMESPACE \ --with-app-uuid UUID --with-app-name NAME --with-secret-token TOKEN \ [--with-uid UID] [--with-container-name NAME] \ [--with-quota-blocks BLOCKS] [--with-quota-files FILES] Expected results: order of the argument shouldn't matter. Additional info:
https://github.com/openshift/origin-server/pull/4524 This seems to be the default behavior of commander and the use case isn't interesting enough to work around. I added a better error message but not going to make another change to fix fully.
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/0b67ffa5e974276ab9b8d4b2ca50f3fcc9bda58b Better message for bug 1028633
It's fixed, verified on devenv_4247, please refer to the following results: # oo-devel-node app-create --with-namespace case247269 --with-app-name case247269 --with-app-uuid 999999999999999999999999 --with-container-uuid 999999999999999999999999 Missing --with-container-uuid UUID as the first option Usage: oo-devel-node app-create --with-container-uuid UUID --with-namespace NAMESPACE \ --with-app-uuid UUID --with-app-name NAME --with-secret-token TOKEN \ [--with-uid UID] [--with-container-name NAME] \ [--with-quota-blocks BLOCKS] [--with-quota-files FILES]