ERROR: POST request was redirected from http://127.0.0.1:8889/clients to http://${local?_ipaddress}. Only GET and HEAD support redirects.

[sawanoboly]

Reported by @nhatnguyen26.

Starting first Chef Client run...
172.17.204.110 Starting Chef Client, version 12.3.0
172.17.204.110 Creating a new client identity for 172.17.204.110 using the validator key.
172.17.204.110 
172.17.204.110 ================================================================================
172.17.204.110 Chef encountered an error attempting to create the client "172.17.204.110"
172.17.204.110 ================================================================================
172.17.204.110 
172.17.204.110 Invalid Redirect:
172.17.204.110 -----------------
172.17.204.110 Change your server location in client.rb to the server's FQDN to avoid unwanted redirections.
172.17.204.110 
172.17.204.110 [2015-05-13T23:39:55+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
172.17.204.110 Chef Client failed. 0 resources updated in 1.935715501 seconds
172.17.204.110 [2015-05-13T23:39:55+00:00] ERROR: POST request was redirected from http://127.0.0.1:8889/clients to http://172.17.204.110. Only GET and HEAD support redirects.
172.17.204.110 [2015-05-13T23:39:55+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

i suddenly have this problem
how can I fix this?

---

ENV

• devStack and centos6.
• Chef 12.3.0 , knife-zero 1.5.0

[nhatnguyen26]

@sawanoboly I think I figured it out, accidentally though. The vm need proxy to go to the internet so I have to set proxy so it can install chef-client, however at the bootstrap time, the proxy cause the redirect to happen, and seem like I don't understand how the --bootstrap-no-proxy options work because even if I add it, it will not work. However, after installing chef, I connect to the vm and remove the proxy setting and bootstrap again, everything went fine.

ERROR: POST request was redirected from http://127.0.0.1:8889/clients to http://172.17.204.110. Only GET and HEAD support redirects.

That pretty much pin point the error correctly.