Bug #12655
closed
Foreman-Proxy not respecting config files in
Description
Changes made to Discovery, TFTP, and Chef config files are not reflected when features are refreshed on non-ssl (HTTP) proxy.
For example setting the discovery.yml to :enabled: http, restarting foreman-proxy, and refreshing the proxy features on an https proxy leaves discovery enabled, but keeps it disabled for HTTP.
Updated by Dominic Cleal almost 9 years ago
- Status changed from New to Feedback
The same smart proxy is listening on both HTTP and HTTPS? Are you saying that the features list is different?
At the moment they ought to be identical, so even if you set Discovery to HTTP-only both the HTTPS and HTTP ports will report that Discovery is enabled. This is bug #10939.
If they're not identical you could perhaps try querying /features on both proxy ports to check it's working this way.
Updated by Aaron Krzywicki almost 9 years ago
- Related to Bug #10939: Features list doesn't reflect availability per protocol added
Updated by Aaron Krzywicki almost 9 years ago
I was able to resolve this by rebooting the hosts system. I'm sure this will be a recurring issue as we spin up new Smart Proxies though.
Updated by Anonymous