Description of problem: The /opt/rh/cfme-gemset/vmdb/Gemfile is missing, therefore preventing of running `bin/rake task` from /var/www/miq/vmdb Version-Release number of selected component (if applicable): 5.4.0.0.8 How reproducible: always Steps to Reproduce: 1. Go to /var/www/miq/vmdb 2. Do bin/rake evm:automate:export DOMAIN=ManageIQ EXPORT_DIR=/tmp/miq PREVIEW=false OVERWRITE=true Actual results: An error message appears: /opt/rh/cfme-gemset/vmdb/Gemfile not found Expected results: The task works Additional info: The workaround for this issue is to use the Gemfile from vmdb. cd /var/www/miq/vmdb BUNDLE_GEMFILE=./Gemfile bin/rake my:awesome:task I just don't know if that will work for all cases.
I have a fix for this issue submitted which the next image build will include. We created a sym link for the bin stubs which resulted in the rake tasks incorrectly resolving the root directory to /opt/rh/cfme-gemset Until the next image is available a better work around would be: rm -rf /var/www/miq/vmdb/bin # remove the sym-link mkdir /var/www/miq/vmdb/bin # create a real directory cp /opt/rh/cfme-gemset/bin/* bin # copy the bin stubs to the real directory
(In reply to Joe Vlcek from comment #2) > I have a fix for this issue submitted which the next image build > will include. > > We created a sym link for the bin stubs which resulted in the > rake tasks incorrectly resolving the root directory to /opt/rh/cfme-gemset > > Until the next image is available a better work around would be: > > rm -rf /var/www/miq/vmdb/bin # remove the sym-link > mkdir /var/www/miq/vmdb/bin # create a real directory > cp /opt/rh/cfme-gemset/bin/* bin # copy the bin stubs to the real directory Sorry, that last line is not fully correct The work around should read: rm -rf /var/www/miq/vmdb/bin # remove the sym-link mkdir /var/www/miq/vmdb/bin # create a real directory # copy the bin stubs to the real directory cp /opt/rh/cfme-gemset/bin/* /var/www/miq/vmdb/bin
Verified in 5.4.0.0.11, it works now.
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. https://rhn.redhat.com/errata/RHBA-2015-1100.html