Bug #12136
closed
foreman-proxy fails to start if ruby-rgen is missing
Added by Adam Cécile about 9 years ago.
Updated over 6 years ago.
Description
Oct 12 07:46:38 hostname foreman-proxy[12730]: Starting foreman-proxy : foreman-proxy/usr/share/foreman-proxy/lib/smart_proxy.rb:101:in `instance_eval': cannot load such file -- rgen/ecore/ecore (LoadError)
foreman-proxy fails to start because of missing **
Installing Debian's package ruby-rgen resolved the issue.
- Category changed from Packaging to Puppet
- Difficulty changed from trivial to easy
The smart proxy loads puppet/pops from the eparser scanner code when it detects Puppet 3.2+, but this depends on rgen. If ruby-rgen isn't installed (it's optional in Debian packages) then the smart proxy fails to start.
It should probably catch load errors from puppet/pops, or better, skip loading the scanner's dependency if it's not needed?
Nightly behaviour is slightly different from 1.9, due to #11599, it now logs and starts without the Puppet functionality:
E, [2015-10-12T08:06:11.677900 #20277] ERROR -- : Couldn't enable plugin puppet: cannot load such file -- rgen/ecore/ecore
- Difficulty deleted (
easy)
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/324 added
- Pull request deleted (
On which distribution and version is that happening specifically?
It was Debian 8/Jessie, I think with apt's installation of recommends disabled - since puppet-common only recommends ruby-rgen.
- Assignee set to Anonymous
- Translation missing: en.field_release set to 104
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous