Hide Forgot
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:
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.
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
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.
Verified this bug following http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-04, and PASS.