Red Hat Bugzilla – Bug 849698
MIN_GEAR setting for a cartridge is not working.
Last modified: 2017-03-08 12:34 EST
Description of problem:
Change the MIN_GEAR setting for a cartridge to 'n' in the manifest file.Create a scalable app,but the gear's number is also 2.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Modify /usr/libexec/stickshift/cartridges/php-5.3/info/manifest.ymle Min: 3
2.Restart stickshift-broker service
3.Create an scalable app about php
rhc app create -a php1 -t php-5.3 -pxx -s
The gear's number is 2.
The gear's number is 4. (3+1=4)
Works for me.
I was able to get this to work on the devenv_2064 today. Instead of 3, I set the Min gears to 2 for php-5.3 cartridge. When I created an application, it had 2 gears for php and 1 for haproxy totalling 3 gears for the application.
I also tried to scale down and got a validation error message saying,
"Cannot scale below minimum gear requirements for group '2'"
Did you have a gear limit of 4+ for your user account? Also, can you try this again on the latest devenv and if it still fails, it would be nice to try and debug on your instance itself.
On devenv, it works perfectly.
The issue only exists in on-premise origin. This issue's product is assigned to "Openshift On-Premise". :)
Krishna: Refer comments above. Can you please co-ordinate with Brenton on this bug as I am going to be away on vacation starting tomorrow?
Need to verify post GA that this is still a problem.
Would you mind re-testing this against the latest version of the product?
(In reply to comment #6)
It doesn't work yet with the lastest puddle (OSE 2012-12-06.1). Even I restart broker and node system, it still can't work.
After I update the file /usr/libexec/openshift/cartridges/php-5.3/info/manifest.yml. Then must execute "cd /var/www/openshift/broker
bundle exec rake tmp:clear". Finaly, it can work.
Whatever, I verify it.
We haven't touched this, so I assume it shipped correctly with 1.0