Bug #22950
closed
Ensure Ansible callback variables are available in systemd context
Description
/etc/sysconfig/foreman-proxy should contain the FOREMAN_URL, FOREMAN_SSL_CERT, FOREMAN_SSL_KEY and FOREMAN_SSL_VERIFY variables.
These variables should be set by the installer so the callback is usable without manual configuration, the defaults wont work (it would be a good idea to change them to more sensible ones anyway).
Updated by Daniel Lobato Garcia almost 7 years ago
- Blocks Tracker #22841: Installer should set up the Ansible proxy added
Updated by Daniel Lobato Garcia almost 7 years ago
- Project changed from Ansible to Installer
- Subject changed from Ensure callback variables are available in systemd context to Ensure Ansible callback variables are available in systemd context
Updated by Ewoud Kohl van Wijngaarden almost 7 years ago
I think this is the wrong solution. /etc/sysconfig/foreman-proxy is deprecated and not present on Debian. It's also duplication of configuration since settings.yml already contains all these variables. Instead I think it's better if foreman-proxy (or rather smart_proxy_ansible) sets the environment variables when calling ansible.
Updated by Ewoud Kohl van Wijngaarden over 6 years ago
- Status changed from New to Rejected
Since ansible 2.5 the env variables are no longer supported. In https://github.com/theforeman/puppet-foreman_proxy/commit/7ee913c68d9a35b35db72758c960b5a1605cdcc3 we started to configure the foreman-proxy user in the correct way.