Bug 855293
| Summary: | The db cartridge status is changed follow by scalable application status after move within district | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OKD | Reporter: | Rony Gong 🔥 <qgong> | ||||
| Component: | Pod | Assignee: | Dan McPherson <dmcphers> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 2.x | CC: | bmeng | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-11-06 18:47:51 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This error happened for all db, and happened for move accross district This is a known issue and won't be fixed till we have cartridge level state. We have made a change in direction on this. The intention now is we only track application level state (for at least the foreseeable future). So this means whatever you do at the application level is what we will make every cartridge when a question of state comes up. Checked again on devenv_2301, according comment #3 , it will only track application level state. Move stopped db in a started app, the db will be started after moved. Move stopped db in a stopped app, the db will be stopped after moved. Mark the bug as verified. |
Created attachment 610669 [details] move log from development.log Description of problem: Read the move log, I think now the move gear status is followed by app status. Version-Release number of selected component (if applicable): devenv_2128 How reproducible: always Steps to Reproduce: 1.Prepare mulit node env and create 1 district, 2.Create scalable app like jbosseap, and embed mysql 3.Just stop the mysql cartridge by rhc app cartridge stop -a qjbosseap -c mysql-5.1 4.Then move this mysql gear within district Actual results: after move, this mysql cartridge status changed to start Expected results: after move, this mysql cartridge status should keep be stop. Additional info: