Description of problem:
The state of  mysql and mongodb that embed to scalable app should be started, not be new, I test it both from RESTAPI and Web console

Version-Release number of selected component (if applicable):
devenv_1904

How reproducible:
always


Steps to Reproduce:
1.Create scalable app and embed mysql, mongdb
2.Use RestAPI to get gear groups and get gear state.
3.find the state for mysql and mongodb are wrong,
  
Actual results:
[root@localhost ~]# curl -k -X GET -H 'Accept: application/xml' --user qgong0:111111 https://ec2-184-72-195-25.compute-1.amazonaws.com/broker/rest/domains/qgong/applications/q1sjboss/gear_groups
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <supported-api-versions>
    <supported-api-version>1.0</supported-api-version>
    <supported-api-version>1.1</supported-api-version>
  </supported-api-versions>
  <messages/>
  <type>gear_groups</type>
  <version>1.1</version>
  <status>ok</status>
  <data>
    <gear-group>
      <gear-profile>small</gear-profile>
      <cartridges>
        <cartridge>
          <job-url>https://jenkins-qgong.dev.rhcloud.com/job/q1sjboss-build/</job-url>
          <name>jenkins-client-1.4</name>
        </cartridge>
        <cartridge>
          <name>jbossas-7</name>
        </cartridge>
        <cartridge>
          <name>haproxy-1.4</name>
        </cartridge>
      </cartridges>
      <name>@@app/comp-proxy/cart-haproxy-1.4</name>
      <gears>
        <gear>
          <state>started</state>
          <id>b0e561c177994eefa8b489710f69819d</id>
        </gear>
      </gears>
    </gear-group>
    <gear-group>
      <gear-profile>small</gear-profile>
      <cartridges>
        <cartridge>
          <username>admin</username>
          <password>hkCr3QwGABNr</password>
          <database-name>q1sjboss</database-name>
          <connection-url>mongodb://9efdf77c0e-qgong.dev.rhcloud.com:35621/</connection-url>
          <name>mongodb-2.0</name>
        </cartridge>
      </cartridges>
      <name>@@app/comp-proxy/cart-mongodb-2.0/group-singlenode</name>
      <gears>
        <gear>
          <state>new</state>
          <id>9efdf77c0e2b46a3a385f81353177dfc</id>
        </gear>
      </gears>
    </gear-group>
    <gear-group>
      <gear-profile>small</gear-profile>
      <cartridges>
        <cartridge>
          <name>jbossas-7</name>
        </cartridge>
      </cartridges>
      <name>@@app/comp-web/cart-jbossas-7/group-app-servers</name>
      <gears>
        <gear>
          <state>started</state>
          <id>9023e52aed8243aaabae7163df976bb7</id>
        </gear>
      </gears>
    </gear-group>
    <gear-group>
      <gear-profile>small</gear-profile>
      <cartridges>
        <cartridge>
          <username>admin</username>
          <password>denXjz57cdei</password>
          <database-name>q1sjboss</database-name>
          <connection-url>mysql://2e580b9f92-qgong.dev.rhcloud.com:35596/</connection-url>
          <name>mysql-5.1</name>
        </cartridge>
      </cartridges>
      <name>@@app/comp-proxy/cart-mysql-5.1/group-mysql</name>
      <gears>
        <gear>
          <state>new</state>
          <id>2e580b9f9247404fa12f04b3f8eb67ea</id>
        </gear>
      </gears>
    </gear-group>
  </data>
</response>


Expected results:
The state of that mysql and mongodb shouldn't be new, should be started

Additional info:
In this page
https://ec2-184-72-195-25.compute-1.amazonaws.com/app/console/applications/q1sjboss

I see the mysql and mongo state are new too.