Description of problem: Run oo-install with -a option, user can not customize message server and db server to separated machines. Seem like -a option is ignore. Version-Release number of selected component (if applicable): oo-install-ose-2.0b-20131108-2228 How reproducible: Always Steps to Reproduce: 1.Make sure there is no ~/.openshift/oo-install-cfg.yml 2.Run oo-install with -a option $ ./oo-install -e -a 3. Actual results: The guide will install a all-in-one machine, user can not customize message server and db server to separated machines. Expected results: User could customize message server and db server to separated machines with -a option. Additional info:
This is a matter of getting the parameters passed from the bootstrap script to the actual installer. Two simple workarounds for the moment: 1. run with "-e -a" in quotes. 2. just run with -a ; -e is assumed by the ose-specific install scripts To make this work in a less surprising way I think we should change the following in the bootstrap script: # Grab command-line arguments args=("$@") [...] GEM_PATH=$GEMPATH RUBYLIB=$RUBYLIB OO_INSTALL_CONTEXT=ose sh -c "${TMPDIR}oo-install-ose-2.0b-20131108-2228/bin/oo-install $@" To this: # Grab command-line arguments cmdlnargs="$@" [...] GEM_PATH=$GEMPATH RUBYLIB=$RUBYLIB OO_INSTALL_CONTEXT=ose sh -c "${TMPDIR}oo-install-ose-2.0b-20131108-2228/bin/oo-install $cmdlnargs" This seems to pass through the args as expected, whether quoted or not, and whether added to the end of "sh <(curl ...)" or just directly on the downloaded script.
Script has been updated re https://github.com/openshift/openshift-extras/pull/169
Verified this bug with oo-install-ose-2.0b-20131111-2053 and PASS. Run "./oo-install -e -a" and "./oo-install -e", you will see the difference. -a option takes effect now.