Actions
Bug #20432
closed
Wrong server_foreman_url in answer file on proxy content
Difficulty:
Triaged:
Yes
Description
# rpm -q puppet-agent foreman-installer puppet-agent-1.10.5-1.el7.x86_64 foreman-installer-1.15.2-1.el7.noarch
After running:
foreman-installer --scenario foreman-proxy-content\
--foreman-proxy-content-parent-fqdn "katello.example.com"\
--foreman-proxy-register-in-foreman "true"\
--foreman-proxy-foreman-base-url "https://katello.example.com"\
--foreman-proxy-trusted-hosts "katello.example.com"\
--foreman-proxy-trusted-hosts "myproxy.example.com"\
--foreman-proxy-oauth-consumer-key "UVrAZfMaCfBiiWejoUVLYCZHT2xhzuFV"\
--foreman-proxy-oauth-consumer-secret "ZhH8p7M577ttNU3WmUGWASag3JeXKgUX"\
--foreman-proxy-content-certs-tar "/root/myproxy.example.com-certs.tar"
server_foreman_url in /etc/foreman-installer/scenarios.d/foreman-proxy-content-answers.yaml contains the proxy url (https://myproxy.example.com) not the foreman server.
So the resulting 'url' in /etc/puppetlabs/puppet/foreman.yaml does not refer to the foreman server.
Updated by Eric Helms almost 8 years ago
- Status changed from New to Needs design
- Assignee set to Eric Helms
Updated by Ewoud Kohl van Wijngaarden almost 8 years ago
This is addressed in https://github.com/Katello/puppet-foreman_proxy_content/pull/132 (and included in https://github.com/Katello/puppet-foreman_proxy_content/pull/136). It does need some design with proper naming.
Updated by Justin Sherrill over 7 years ago
- Pull request https://github.com/Katello/puppet-foreman_proxy_content/pull/132 added
Updated by Justin Sherrill over 7 years ago
- Status changed from Needs design to Assigned
Updated by Eric Helms over 7 years ago
- Translation missing: en.field_release set to 284
Updated by John Mitsch over 7 years ago
- Translation missing: en.field_release changed from 284 to 352
Updated by Anthony Chevalet over 5 years ago
Hi, any update here?
I'm still having this issue with a fresh install of Katello 3.14.1.
The proxy content does not upload puppet reports and facts and fails on node.rb.
Updated by Ewoud Kohl van Wijngaarden almost 2 years ago
- Related to Feature #36573: Reuse foreman_proxy::foreman_base_url value for puppet::server_foreman_url added
Updated by Ewoud Kohl van Wijngaarden almost 2 years ago
- Status changed from Assigned to Closed
Via #36573 the option is no longer needed.
Actions