Bug 1483659

Summary: Running bundle install breaks appliance
Product: Red Hat CloudForms Management Engine Reporter: Ryan Spagnola <rspagnol>
Component: ApplianceAssignee: Gregg Tanzillo <gtanzill>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: medium    
Version: 5.8.0CC: abellott, jhardy, jrafanie, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-27 21:05:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:

Description Ryan Spagnola 2017-08-21 16:06:42 UTC
Description of problem:
Running bundle install breaks an appliance's gems.
Minimal success in re-installing gemset rpm.

Version-Release number of selected component (if applicable):
Any

How reproducible:
Always

Steps to Reproduce:
1. Run bundle install
2. reboot appliance
3. Not able to use appliance_console or UI

Actual results:


Expected results:


Additional info:
Would it be possible to put in place a version blocker for gems to avoid this?

Only fix found so far is to export database and deploy a new appliance and import previous database

Comment 3 Joe Rafaniello 2018-02-27 21:05:06 UTC
Unfortunately, no, you can't run bundle install or bundle or bundle update on downstream appliances due to downstream packaging:

a) scl ruby changes bundler/rubygems (library locations, etc.)
b) downstream packaging of gems puts libraries into multiple locations

Since bundle --frozen option doesn't work as we'd like, the only recourse would be to provide our own bundle command that prevents you from running it.  I don't know if that's better.

We're hoping to no longer use scl ruby in the future and perhaps this would allow us to properly use the --frozen option.

*** This bug has been marked as a duplicate of bug 1414815 ***