Description of problem: After restore snapshot for scaled app which embedding the databases, when run "rhc app show <appname> --gears", the databases' status all are "stopped", but actually, all databases are running. Version-Release number of selected component (if applicable): devenv_stage_655 How reproducible: always Steps to Reproduce: 1. Create a scaled app with DBs rhc app create crb19s ruby-1.9 mysql-5.5 postgresql-9.2 mongodb-2.2 -s --no-git 2. Save the snapshot for this app rhc snapshot save -a crb19s -f crb19s.tar.gz 3. Restore snapshot for this app rhc snapshot restore -a crb19s -f crb19s.tar.gz 4. Check the state of DBs by "rhc app show --gears" rhc app show crb19s --gears Actual results: ID State Cartridges Size SSH URL -------------------------------- ------- -------------------- ----- ------------------------------------------------------------------------------------- 52e4729b3ec6484fdb0000fa started ruby-1.9 haproxy-1.4 small 52e4729b3ec6484fdb0000fa.rhcloud.com 80e0e906863411e3a13322000ab587e2 started ruby-1.9 haproxy-1.4 small 80e0e906863411e3a13322000ab587e2.rhcloud.com 52e49c963ec6480a64000011 stopped mysql-5.5 small 52e49c963ec6480a64000011.rhcloud.com 595266973212013372637184 stopped mongodb-2.2 small 595266973212013372637184.rhcloud.com 08f7d0f0864b11e3a13322000ab587e2 stopped postgresql-9.2 small 08f7d0f0864b11e3a13322000ab587e2.rhcloud.com Expected results: The DB's status should be started after restore snapshot for scaled app when checking by "rhc app show <appname> --gears" Additional info: 1. can show the correct status for DBs by "rhc cartridge status" 2. The DBs all can be connected.
*** This bug has been marked as a duplicate of bug 1030305 ***