Description of problem: When unidling scaled apps, secondary gears are left idle. Version-Release number of selected component (if applicable): How reproducible: Idle all gears in a scaled application using `oo-admin-ctl-gears idle`. Unidle the primary gear via HTTP request or via `oo-admin-ctl-gears unidle`. Steps to Reproduce: 1. Create a scaled php-5.5 application 2. Add the mysql-5.4 cartridge to the application 3. Idle all gears in the application 4. Unidle the primary gear Actual results: The mysql cartridge in its own gear remains idle. Expected results: The mysql cartridge (and any other secondary cartridges) should also be started during unidle. Additional info: This occurs because the unidle logic is implemented a gear-local ApplicationContainer#start_gear in openshift-origin-node. The code could be changed to invoke a broker start event which would start up the entire application rather than just the primary gear.
https://github.com/openshift/origin-server/pull/5375
Test on devenv_4760, issue have been fixed After unidle the primary gear via HTTP request or via `oo-admin-ctl-gears unidle`, the db gear's state is started. move bug to verified.