Bug #1490
closed
false warning when puppet master proxy is blank appears to break provisioning
Description
If I set a host as follows:
Puppet Master Proxy: blank
Puppet Master FQDN: puppet.example.com
Then provisioning fails (when getting the debian preseed file) with:
provisioning fails "Managing Puppet CA without a smart-proxy will not be supported in the next release" (but we are managing puppet CA, it's puppet we weren't - and even if I then change the smart-proxy to managing puppet I still get this error).
However if I set a host with:
Puppet Master Proxy: Foreman proxy
then although the preseed part of provisioning works, puppet.conf and finish.sh fail as they use foreman-proxy.example.com as the puppetmaster rather than puppet.example.com.
this is all on foreman v0.4.1-1
(originally tacked onto #1482, raised separately here at Ohad's request)
Updated by Benjamin Papillon almost 11 years ago
- Status changed from New to Closed
I close this ticket as it contains on issue that is not valid anymore and one issue that are defined elsewhere.
1/ the issue with empty puppet master proxy does not exist anymore as Foreman forces the use of Smart Proxy with puppet capability
2/ the issue with puppet master fqdn starting with puppet. has been reported
Thanks for reporting!