Title: Configuring Bundler Describe the issue: At documentation [1], To start broker, we try to do "# service openshift-broker start", but it cannot work due to no v8314 package. To start broker needs to install v8314 package.(See[2] line 45) [1] OpenShift Enterprise 2 Deployment Guide https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#Configuring_Bundler [2] /etc/init.d/openshift-broker 41 start() { 42 echo -n $"Starting $prog: " 43 pushd $osdir > /dev/null 44 rm -rf Gemfile.lock 45 scl enable ruby193 v8314 "bundle install --local > /dev/null" 46 chown apache:apache Gemfile.lock 47 RETVAL=$? Suggestions for improvement: Please describe following command somewhere in the document. (prior to starting broker service.) # yum install v8314.x86_64
Can you explain how exactly you hit this situation? OpenShift Enterprise requires a fully updated RHEL installation. When you run 'yum update' on this system ruby193-v8 should be replaced by v8314-v8. The latest broker RPM should be pulled in as well. I few this more as a packaging bug.
I did following steps. * Step 1. subscription-manager repos \ --enable=rhel-6-server-rpms \ --enable=rhel-server-rhscl-6-rpms \ --enable=rhel-6-server-ose-2.1-infra-rpms \ --enable=rhel-6-server-ose-2.1-rhc-rpms \ --enable=rhel-6-server-ose-2.1-node-rpms \ --enable=jb-ews-2-for-rhel-6-server-rpms \ --enable=rhel-6-server-ose-2.1-jbosseap-rpms \ --enable=jb-eap-6-for-rhel-6-server-rpms * Step 2. yum install -y openshift-enterprise-release * Step 3. oo-admin-yum-validator -o 2.1 -r broker -r client -r node -r node-eap --fix-all * Step 4. Followed by deployment guide from Chan 7.3 * Step 5 Chap 7.8.10, I got following message. [root@broker ~]# service openshift-broker start Starting openshift-broker: Unable to open /etc/scl/prefixes/v8314! chown: cannot access `Gemfile.lock': No such file or directory Bundle failed Run 'bundle install --local' in /var/www/openshift/broker/ to see the problem. * Step 6 I installed v8314.x86_64 and fixed it. ~~~ OK, I might make mistake, I will do it again. And update this bugzilla. Thanks, Kenjiro
Hm, could be a packaging bug, yeah. [root@vm ~]# rpm -q --whatrequires v8314-v8 nodejs010-nodejs-0.10.25-1.el6.x86_64 nodejs010-nodejs-0.10.25-1.el6.x86_64 v8314-v8-devel-3.14.5.10-3.6.el6.x86_64 mongodb24-mongodb-2.4.9-8.el6.x86_64 mongodb24-mongodb-server-2.4.9-8.el6.x86_64 There could be an indirect way the package is required but I'm not immediately seeing that anything on the broker would require it. That's odd...
Let's treat this as a packaging bug.
I think I understand. v8314-v8 is required (as "libv8.so.v8314-3.14.5()(64bit)") by ruby193-rubygem-therubyracer. That in turn is required by rubygem-openshift-origin-admin-console and openshift-origin-console, but not directly by the broker (which, to be fair, doesn't use it). If you were following along in the manual, you would install the broker first without those and it wouldn't work. Since our install scripts always install the admin console and mgmt console along with the broker, we never noticed the broker chokes without v8314 installed. I'm frankly not sure how best to address this.
After some consideration, the plan is to add the requirement to the broker packaging and upstream the changes.
https://github.com/openshift/origin-server/pull/5799
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/0ee0ff1948779d1b343a79b24938a830d03229b9 broker: require v8 (SCLized in RHEL 6) Bug 1108762 - Need to install v8314 package to start openshift-broker service https://bugzilla.redhat.com/show_bug.cgi?id=1108762 openshift-broker requires v8 at startup, but the packaging did not express this requirement. Modified so it does.
Check on puddle [2.1.z/2014-09-10.1] #rpm -qR openshift-origin-broker-1.16.1.13-1.el6op <--snip--> v8314-v8 rpmlib(PayloadIsXz) <= 5.2-1 The package 'v8314-v8' is required by package 'openshift-origin-broker'.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1353.html