Bug 1045018

Summary: scalable jbosseap fail to be migrated when upgrade env following 1.1->1.2->2.0
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: Cluster Version OperatorAssignee: Jason DeTiberus <jdetiber>
Status: CLOSED WONTFIX QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 2.0.0CC: bleanhar, libra-onpremise-devel, lmeyer
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: 2014-02-04 18:46: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:
Attachments:
Description Flags
upgrade_errors.log none

Description Johnny Liu 2013-12-19 13:10:44 UTC 
Description of problem:
create a scalable jbosseap app in ose-1.1 env, upgrade it to 1.2->2.0, failure is seen.

Version-Release number of selected component (if applicable):
openshift-enterprise-release-2.0.0c-1.git.21.e364d06.el6op.noarch
openshift-enterprise-upgrade-node-2.0.0c-1.git.21.e364d06.el6op.noarch
openshift-enterprise-upgrade-broker-2.0.0c-1.git.21.e364d06.el6op.noarch
openshift-enterprise-yum-validator-2.0.0c-1.git.21.e364d06.el6op.noarch

How reproducible:
Always

Steps to Reproduce:
1.set up ose-1.1 env
2.create scalable jbosseap on it.
3.upgrade env to 1.2
4.do some change, and git push, make sure it is working well.
5.upgrade env to 2.0


Actual results:
When running 02-node-upgrade-gears, failure is seen for scalable jbosseap app.
Pls refer to attachment for log.

Expected results:
No failure.

Additional info:
If install a ose-1.2, and create scalable jbosseap on it, then upgrade to 2.0, this issue does NOT happen.
Comment 1 Johnny Liu 2013-12-19 13:11:33 UTC 
Created attachment 838975 [details]
upgrade_errors.log