Description of problem: When user create app with --enable-jenkins and medium gear-size options, jenkins app is deployed onto default small node. Seem rhc does not pass the specified gear-size to jenkins app creation. Version-Release number of selected component (if applicable): rhc-1.24.3.1-1.el6op.noarch How reproducible: Always Steps to Reproduce: 1.Set up env, 1 small node, and 1 medium node 2.Create app with --enable-jenkins and --gear-size options # rhc app-create myapp php-5.3 --enable-jenkins -g medium 3. Actual results: The php-5.3 app is deployed onto the medium node, while jenkins app is deployed on to default small node. Expected results: Both php-5.3 app and jenkins app are deployed onto small node. Additional info:
Found a typo: Expected results: Both php-5.3 app and jenkins app are deployed onto medium node.
Commit pushed to master at https://github.com/openshift/rhc https://github.com/openshift/rhc/commit/5332b7f27d1daeb898d27d204d4e434c064a3706 Bug 1111456 - jenkins app default to small gear with enable-jenkins and custom gear size When user creates app using rhc with --enable-jenkins and medium --gear-size options, the jenkins app is deployed onto default small gear size. The rhc code doesn't pass the gear size option during jenkins app creattion. This commit will modify the code to allow the gear size value to be passed into method that create jenkins app. Bug 1111456 Link <https://bugzilla.redhat.com/show_bug.cgi?id=1111456> Signed-off-by: Vu Dinh <vdinh>
QE, Based on the original report's step to reproduce, can we verify that jenkins apps will now successfully deploy on the correct sized gear when given as an option? Puddle: http://etherpad.corp.redhat.com/puddle-2-2-2016-02-19 Thank you
Verified this bug with rhc-1.38.6.1-1.el6op.noarch, and PASS. # rhc app create php53app php-5.3 -p redhat --enable-jenkins --gear-size medium After app is created, log into medium node, found the two app is deployed onto the same node. # ls /var/lib/openshift/ aquota.user jialiu-jenkins-1 jialiu-php53app-1 lost+found
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-0489.html