Bug 1036550

Summary:	jbossews app fail to be started after update ose from 1.2 to 2.0
Product:	OpenShift Container Platform	Reporter:	Johnny Liu <jialiu>
Component:	Cluster Version Operator	Assignee:	Jason DeTiberus <jdetiber>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.0.0	CC:	bleanhar, jdetiber, libra-onpremise-devel
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 14:43:57 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:

Description Johnny Liu 2013-12-02 09:37:36 UTC

Description of problem:
After upgrade to 2.0 from 1.2, jbossews app could not be started, and seen from app log, get the following error:
==> jbossews/logs/jbossews.log <==
(standard_in) 1: syntax error
(standard_in) 1: syntax error
/var/lib/openshift/5295d61caeb90571cc0000ce/jbossews//bin/tomcat: line 25: [: -gt: unary operator expected

 

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

How reproducible:
Always

Steps to Reproduce:
1. Setup ose-1.2 env
2. Create jbossews-1.0 or jbossews-2.0 app on the node
3. Upgrade env from 1.2 to 2.0
4. Access the app


Actual results:
"503 Service Temporarily Unavailable" error is seen, try to start this app using rhc, still failed. Seen from app log, get the following error:
==> jbossews/logs/jbossews.log <==
(standard_in) 1: syntax error
(standard_in) 1: syntax error
/var/lib/openshift/5295d61caeb90571cc0000ce/jbossews//bin/tomcat: line 25: [: -gt: unary operator expected

Expected results:
jbossews app could be started successfully.

Additional info:

Comment 2 Jason DeTiberus 2013-12-03 00:11:18 UTC

This is fixed in the latest upgrade puddle: http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-02

Please note that this pad has changed the upgrade steps to use a puddle, so there are a few workarounds that need to be done to make sure the right bits are installed during the upgrade.

I tested with jbossews-1.0, jbossews-2.0 in both scalable and non-scalable applications.

Comment 3 Johnny Liu 2013-12-03 09:38:33 UTC

Rest this bug following http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-02, still failed.

Now I already set up an ose-1.2 test bed for you, I also created all kinds of cartridge app, you could use it for upgrade testing to reproduce this bug.

Broker: 10.4.59.154 root/redhat
Node: 10.4.59.132 root/redhat
Account/password: jialiu/redhat

Comment 4 Jason DeTiberus 2013-12-03 21:52:16 UTC

I was unable to replicate this using the latest pad/puddle:
http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-03

After fixing a broken upgrade with the mysql cartridge (which is included in
the puddle on the pad above) I was not able to replicate.

I believe this error occurred because earlier versions of the 2013-12-02 pad
linked to a puddle that was missing the updated msg-node rpm and all gear
migrations were failing.

Comment 5 Johnny Liu 2013-12-05 09:32:06 UTC

Verified this bug following http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-04, and PASS.