Running knife bootstrap on a new node that needs an HTTP_PROXY set to
get out to the internet, with the --bootstrap-proxy option set, knife
complains that curl doesn’t know the option --proxy=on. This is Centos
6.4, with curl 7.19.7
[…]
111.222.333.444 curl: option --proxy=on: is unknown
111.222.333.444 curl: try ‘curl --help’ or ‘curl --manual’ for more information
10.187.254.188 bash: line 83: chef-client: command not found
Do I not have something set right? Do I need a .curlrc on the new node
with the proxy IP set in there?
Is your bootstrap template corrupted in some way? If you look at the
one that comes with Chef, it looks like this:
if ! exists /usr/bin/chef-client; then
if exists wget; then
bash <(wget <%= "--proxy=on " if knife_config[:bootstrap_proxy] %>
${install_sh} -O -) ${version_string}
elif exists curl; then
bash <(curl -L <%= "--proxy "#{knife_config[:bootstrap_proxy]}"
" if knife_config[:bootstrap_proxy] %> ${install_sh})
${version_string}
else
echo "Neither wget nor curl found. Please install one and try again." >&2
exit 1
fi
fi
So it looks like in your situation, the wget flags are getting passed
to a curl...
Running knife bootstrap on a new node that needs an HTTP_PROXY set to
get out to the internet, with the --bootstrap-proxy option set, knife
complains that curl doesn't know the option --proxy=on. This is Centos
6.4, with curl 7.19.7
[...]
111.222.333.444 curl: option --proxy=on: is unknown
111.222.333.444 curl: try 'curl --help' or 'curl --manual' for more information
10.187.254.188 bash: line 83: chef-client: command not found
Do I not have something set right? Do I need a .curlrc on the new node
with the proxy IP set in there?
On Mon, Sep 23, 2013 at 3:18 PM, Julian C. Dunn jdunn@aquezada.com wrote:
Is your bootstrap template corrupted in some way? If you look at the
one that comes with Chef, it looks like this:
if ! exists /usr/bin/chef-client; then
if exists wget; then
bash <(wget <%= "--proxy=on " if knife_config[:bootstrap_proxy] %>
${install_sh} -O -) ${version_string}
elif exists curl; then
bash <(curl -L <%= "--proxy "#{knife_config[:bootstrap_proxy]}"
" if knife_config[:bootstrap_proxy] %> ${install_sh})
${version_string}
else
echo "Neither wget nor curl found. Please install one and try again." >&2
exit 1
fi
fi
So it looks like in your situation, the wget flags are getting passed
to a curl...
Thanks, seems obvious now, but it took you pointing it out. Thanks!
Running knife bootstrap on a new node that needs an HTTP_PROXY set to
get out to the internet, with the --bootstrap-proxy option set, knife
complains that curl doesn't know the option --proxy=on. This is Centos
6.4, with curl 7.19.7
[...]
111.222.333.444 curl: option --proxy=on: is unknown
111.222.333.444 curl: try 'curl --help' or 'curl --manual' for more information
10.187.254.188 bash: line 83: chef-client: command not found
Do I not have something set right? Do I need a .curlrc on the new node
with the proxy IP set in there?