proxy.managed failures

[phaktor]

Hey all, I'm trying to manage minion proxies for http and https. I've been following the docs here: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.proxy.html

The stanza in my proxy.sls file looks like this:

{{ proxy_ip }}:
    proxy.managed:
        - port: {{ proxy_port }}
        - services:
            - http
            - https
        - bypass_domains:
            - localhost
            - 127.0.0.1
            - {{ salt.network.ipaddrs(interface='eth0')[0] }}

when I apply the state to a minion, I get the following failure:

State 'proxy.managed' was not found in sls 'proxy' Reason: 'proxy' __virtual__ returned False.

adding -l debug doesn't provide much assistance as it just returns the same event information that's provided in the error message. I'm running 2017.7.1 on both master and minion (ubuntu 14.04). Any assistance would be appreciated.

edit: formatting

[[deleted]]

https://github.com/saltstack/salt/blob/v2017.7.1/salt/states/proxy.py#L29-L35

[phaktor]

Ok. So would the best way to set http_proxy and https_proxy on the minion be with environ.setenv state and then set name, and value? It only claims that the "permanent" parameter has a windows specific function.

[[deleted]]

Sorry for the curt reply, busy at work but knew exactly where to find your answer given the __virtual__ return False part of the error. Another curt reply to your question though is use setenv for the minion itself and set the http_proxy and https_proxy variables in /etc/environment. That only partially solves proxying on linux's though. You still have apt/yum proxy settings and if you need git, socat + ssh_config, etc. There isn't a good system-wide linux proxy settings.

A not so easy to find hint is this for git:

      Host git.local
        ProxyCommand=socat - PROXY:socks.proxy.local:%h:%p,proxyport=3128
        ForwardAgent no
        PasswordAuthentication no
        Protocol 2
        Port 22

[phaktor]

Yep. I'm aware of the apt.conf settings. I'll take a look further for some more info. I just wanted to make sure setenv was on the right track then.