Bug 968994

Description of problem:
When hot_deploy is present, new scaled gears are never started.

Version-Release number of selected component (if applicable):
Codebase as of 3/18/2013

How reproducible:
Consistent (tested with JBoss EAP and PHP)

Steps to Reproduce:
1. Spin up a development instance (assuming dev.rhcloud.com below)

2. Create a scaled JBoss EAP application named scale:
  rhc app-create scale jbosseap -s

3. Enable hot_deploy
  cd scale; touch .openshift/markers/hot_deploy
  git add .; git commit -a -m "Adding hot deploy";
  git push

4. Scale the application to 3 gears
  rhc cartridge-scale jbosseap --app scale --min 3 --max 6

Actual results:
The new gears do not have JBoss started on them.

Expected results:
The new gears should be started and serving traffic

Additional info:
Snip from the /var/log/openshift/platform.log (notice the 'not starting cartridge jbosseap...):

...
+ ssh 146678179485050841595904.180.46 'gear remotedeploy --init --hot-deploy'
Deploying JBoss
Not starting cartridge jbosseap because hot deploy is enabled

Exit code: 0
...

This behavior is consistent with the PHP cartridge as well:

1. Spin up a development instance (assuming dev.rhcloud.com below)

2. Create a scaled JBoss EAP application named scale:
  rhc app-create scalephp php-5.3 -s

3. Enable hot_deploy
  cd scalephp; touch .openshift/markers/hot_deploy
  git add .; git commit -a -m "Adding hot deploy";
  git push

4. Scale the application to 3 gears
  rhc cartridge-scale php-5.3 --app scalephp --min 3 --max 6