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):
Steps to Reproduce:
1. Run bundle install
2. reboot appliance
3. Not able to use appliance_console or UI
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
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 ***