Created attachment 601688 [details] development.log Description of problem: Version-Release number of selected component (if applicable): devenv_1931 How reproducible: always Steps to Reproduce: 1.Create scalable app, eg jbosseap-6.0 2.Embed mysql-5.1 3.Just stop the mysql by rhc app cartridge stop -a jbosseap -c mysql-5.1 [root@localhost qsjbosseap]# rhc app cartridge status -a qsjbosseap -c mysql-5.1 Password: RESULT: MySQL is stopped 4.Then move the mysql gear by mysql gear within district Actual results: The mysql gear become running status [root@localhost qsjbosseap]# rhc app cartridge status -a qsjbosseap -c mysql-5.1 Password: RESULT: MySQL is running Expected results: The mysql gear should still be stopped status Additional info: Then I stop the whole app, go on moving the mysql gear, mysql still changed to running status, and the move log show mysql component is runing(wrong). So please focus on the code of check mysql gear component status.
This kind of error also exist in non-scalable app with embed mysql, only stop mysql cartridge, but after move, the mysql will be running status.
per conversation with Rajat, expecting a fix by 5 p.m. today.
rev# 40f9344ad9fe289ea45ca28fbb949a3a788d5e85 in crankcase.repo! Please note the expected behaviour for this bug : - When a gear with mysql on it is moved, its state will be determined by the application's status - So, stop the app (its framework) and then move the mysql gear (scalable or not) and check the mysql cartridge's state (it should be stopped because the app was stopped) - what has changed with the fix? Earlier, if the app was stopped, but the catridge was running, we would keep the cartridge as running after move, now we explicitly stop it because the app was stopped. Note: this fix is yet to be hot-fixed into stage
on stage with pull request#327
verified on devenv-stage_228