Comment 3 for bug 1845351

There are two reasons why this bug is happening. The first is that something is changing the proxy environment variables. When rackd starts up, it has http_proxy and no_proxy defined and updating the tags work in our CI environment, since the region IP is in no_proxy. But then at some point, at least the no_proxy variable is gone. From the looks of it http_proxy was also gone, but somehow the API call still went through the proxy, that doesn't allow access to the region.

But still, the best fix is still not to use any proxies for the API communication. It's documented that rackd needs TCP access to the region on port 5240. If we for some reason want to support proxy for rack-region communication, we need to add explicit support for it.