Bug 819862

Summary:	gearname_ctl.sh does not keep consistent between existing app and newly created app after run migrate
Product:	OKD	Reporter:	Johnny Liu <jialiu>
Component:	Containers	Assignee:	Rob Millner <rmillner>
Status:	CLOSED DUPLICATE	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.x	CC:	mfisher
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-08 21:31:26 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 Johnny Liu 2012-05-08 12:11:09 UTC

Description of problem:
For existing app, after migrate, the following is added into gearname_ctl.sh:
export CARTRIDGE_TYPE="<gear_cartridge_type>"

Then create a new app, check its gearname_ctl.sh, found there is such line.

From that, I did not found the meaning of migrate operation. For my understanding, the goal of migrate is to make existing app and new app keep insistent.

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

How reproducible:
Always

Steps to Reproduce:
1. Launch devenv-stage_187
2. Create app - app1
3. Update packages to the latest version, then run migrate script
4. Create a new app - app2

  
Actual results:
Compared gearname_ctl.sh of app1 and app2, found the following line is only existing old app - app1.

export CARTRIDGE_TYPE="<gear_cartridge_type>"

Expected results:
Existing app and new app should keep insistent.

Additional info:

Comment 1 Rob Millner 2012-05-08 21:31:26 UTC

There was a bug preventing new apps from getting the correct "CARTRIDGE_TYPE" setting.

*** This bug has been marked as a duplicate of bug 819966 ***