Bug #9990
closed
Foreman_smartproxy fails to evalute with "couldn't find HOME environment"
Added by Xavier L over 9 years ago.
Updated about 6 years ago.
Description
When runnign Puppet agent manually, everything works fine. However, when running Puppet as a service, the Foreman_smartproxy type fails with:
puppet-agent[1747]: (/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.
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.
Could you try it with all packages from the 1.7 repos but apipie-bindings from the 1.8 repo on a clean system?
This issue might need to get moved to a different project.
- 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.
- Assignee set to Anonymous
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-packaging/pull/612 added
- Pull request deleted (
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 40
Package built, will be included in the next 1.7 release.
Also available in: Atom
PDF
Updated by 
Updated by Anonymous 
Updated by 
Updated by