Bug 867322

Summary:	Better to change the status of mongodb and mysql from "NEW" to "STARTED" when they are embeded to scalable application.
Product:	OKD	Reporter:	Yujie Zhang <yujzhang>
Component:	Containers	Assignee:	Rob Millner <rmillner>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	2.x	CC:	mfisher, xtian
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:49:34 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:

Description Yujie Zhang 2012-10-17 10:16:51 UTC

Description of problem:

After I embeded mongodb and mysql to scalable application, the status of these two cartridges are "NEW", for the cartridges are running, suggest to change the status to "STARTED", just the same like postgresql.

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

How reproducible:always


Steps to Reproduce:
1.Create a scalable application
2.Embed mongodb and mysql
3.Check the status of these two cartridges
  
Actual results:

The status of mongodb and mysql is "NEW".

Expected results:

Better to change the status to "STARTED" to make it consistent with postgresql.

Additional info:

Comment 1 Rob Millner 2012-10-26 23:41:19 UTC

Added to https://github.com/openshift/origin-server/pull/777

Comment 2 Xiaoli Tian 2012-10-29 02:38:19 UTC

(In reply to comment #1)
> Added to https://github.com/openshift/origin-server/pull/777

Move it to ON_QA since above pull request is merged.

Comment 3 Yujie Zhang 2012-10-29 05:11:57 UTC

(In reply to comment #1)
Tested this issue on devenv_2397, it has been fixed now, thanks.