When Puppet gem is not installed, foreman-proxy does not start.
This does not look like any problem for Satellite 6 itself but this is blocker for Foreman Discovery Image which is used in both Satellite 6 and OpenStack Installer.
Please make sure other modules will work without their dependencies, the discovery PXE boot image has very limited environment with minimum deps.
merged in at ed3332a.
Commented on upstream issue as well:
E, [2014-08-13T17:26:31.882793 #44503] ERROR -- : Couldn't enable plugin puppet: undefined method `<=>' for :puppetdir:Symbol:/usr/share/foreman-proxy/lib/proxy/plugin.rb:139:in `<=>'/n/usr/share/foreman-proxy/lib/proxy/plugin.rb:139:in `sort'/n/usr/share/foreman-proxy/lib/proxy/plugin.rb:139:in `log_used_default_settings'/n/usr/share/foreman-proxy/lib/proxy/plugin.rb:149:in `configure_plugin'/n/usr/share/foreman-proxy/lib/proxy/plugin.rb:22:in `configure_loaded_plugins'/n/usr/share/foreman-proxy/lib/proxy/plugin.rb:22:in `each'/n/usr/share/foreman-proxy/lib/proxy/plugin.rb:22:in `configure_loaded_plugins'/n/usr/share/foreman-proxy/lib/smart_proxy.rb:116:in `launch'/n/usr/share/foreman-proxy/bin/smart-proxy:6
<jsherrill> jmontleon: in ruby 1.8.7 it doens't look like you can sort symbols?
<jsherrill> irb(main):002:0> [:a, :b, :c].sort
<jsherrill> NoMethodError: undefined method `<=>' for :a:Symbol
<jsherrill> so i'm guessing its parsing those config files and using symbols
<jsherrill> jmontleo: but the proper fix would be to not rely on sortable symbols IMHO
jsherrill> or else explicitly include the Comparable monkey patch
The upstream fix for this is here:
When merging this one, please merge the one that caused this issue:
We tested this on both RHEL6 (sorry for that) and RHEL7 and it will hit develop soon. I'd like to ask you if you can be so kind and include this in Compose 2. This bug is blocker for OpenStack RHEL7 discovery image and I need this to be fixed in the buildroot so I am able to come up with new ISO build.
please provide verification steps
(In reply to Tazim Kolhar from comment #8)
> please provide verification steps
1. install a capsule or foreman-proxy
2. set :enabled: false in both /etc/foreman-proxy/settings.d/puppet.yml and puppetca.yml
3. service foreman-proxy start
4. check the proxy process is still running, check for error in comment #5 in /var/log/foreman-proxy/proxy.log
Btw, you probably don't want to needinfo yourself...
no error in /var/log/foreman-proxy/proxy.log
after making those settings in /etc/foreman-proxy/settings.d/puppet.yml and puppetca.yml
This was delivered with Satellite 6.0 which was released on 10 September 2014.