Bug 973740

Summary:	Do not leave migration metadata in place as a result of validate-gear
Product:	OpenShift Online	Reporter:	Paul Morie <pmorie>
Component:	Containers	Assignee:	Paul Morie <pmorie>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	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:	2013-06-24 14:53:40 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 Paul Morie 2013-06-12 15:21:09 UTC

Currently in the migrations we leave the migration metadata in place if the gear status after migration is not what we expect.  Instead, we should just log the status - as leaving the migration metadata in place has left a lot of gears with metadata in production.

Comment 1 openshift-github-bot 2013-06-12 22:17:54 UTC

Commit pushed to master at https://github.com/openshift/li

https://github.com/openshift/li/commit/94b91bdfd736400b8c35274a5086547c6635a268
Fix bug 973740: do not leave migration metadata in place due to gear status

Comment 2 Paul Morie 2013-06-12 22:25:25 UTC

Will be present in devenv 3354

Comment 3 Xiaoli Tian 2013-06-14 11:19:18 UTC

(In reply to Paul Morie from comment #2)
> Will be present in devenv 3354

Verified it on devenv-stage_375: 

set problem =1 to simulate the problem error:
Will find the following log after running migration

Post-migration response code: 200
Problem detected with gear status:
Cart status for python [OK]: CLIENT_RESULT: Application is running
CLIENT_RESULT: %

Did not find metadata left in the gear.