Foreman_smartproxy fails to evalute with "couldn't find HOME environment"
When runnign Puppet agent manually, everything works fine. However, when running Puppet as a service, the Foreman_smartproxy type fails with:
puppet-agent: (/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[smart-proxy.fqdn]) Could not evaluate: couldn't find HOME environment -- expanding `~'
I'm running on Ubuntu 14.04.
Drilling down, it seems the issue is that foreman-cli requires the distro-packaged version of apipie-bindings, which is 0.0.8, the required version should be 0.0.9, as per issue #7063.
#1 Updated by Xavier L over 4 years ago
Actually the puppet foreman_proxy module requires the ruby-apipie-bindings package as well (https://github.com/theforeman/puppet-foreman_proxy/blob/master/manifests/install.pp).
#2 Updated by Xavier L over 4 years ago
Looking at http://deb.theforeman.org/pool/trusty/1.7/r/ruby-apipie-bindings/, it seems that the foreman packaged version (for foreman 1.7) is 0.0.8. Removing the module and installing the library from gem (gem install apipie-bindings) seems to clear the error, but the packaged version is installed on the next run, so the errors start again when the puppet agent is restarted.
#4 Updated by Xavier L over 4 years ago
I manually installed ruby-apipie-bindings from 1.8 (wget http://deb.theforeman.org/pool/trusty/1.8/r/ruby-apipie-bindings/ruby-apipie-bindings_0.0.11-1_all.deb && dpkg -i ruby-apipie-bindings_0.0.11-1_all.deb). The errors cleaned-up and puppet is not trying to downgrade ruby-apipie-bindings to 0.0.8. So I guess that it's a valid workaround, but a real solution would be to release 0.0.8-2 (patched with https://github.com/Apipie/apipie-bindings/pull/14) or 0.0.9 to all the supported versions with 0.0.8.
#6 Updated by Dominic Cleal over 4 years ago
- Project changed from Foreman to Packaging
- Category set to Debian/Ubuntu
Hm, seems to have been an oversight that we have apipie-bindings 0.0.8 in the deb repos and 0.0.10 in the RPMs, which it should be. I think the Hammer version are all the same, so updating it in 1.7 shouldn't cause an issue.