Open Stack

On 14/10/16 18:07, Yu Watanabe wrote:
> At the same time , I see connection errors in the proxy server.
>
> Oct 14 14:05:08 opstack-controller proxy-server: Deferring reject 
> downstream
> Oct 14 14:05:08 opstack-controller proxy-server: - - 
> 14/Oct/2016/05/05/08 HEAD /v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004 
> HTTP/1.0 204 - Swift - - - - tx60f54bfed6d94357a10c0-0058006784 - 
> 0.0268 RL - 1476421508.123720884 1476421508.150515079 -
> Oct 14 14:05:08 opstack-controller keystoneauth.identity.base: Failed 
> to contact the endpoint at http://opstack-cont-manage:5000/v3 for 
> discovery. Fallback to using that endpoint as the base url.
> Oct 14 14:05:08 opstack-controller keystoneauth.identity.base: Failed 
> to contact the endpoint at http://opstack-cont-manage:5000/v3 for 
> discovery. Fallback to using that endpoint as the base url.
> Oct 14 14:05:08 opstack-controller keystoneauth.session: Failure: 
> Unable to establish connection to 
> http://opstack-cont-manage:5000/v3/auth/tokens. Retrying in 0.5s.
> Oct 14 14:05:08 opstack-controller keystoneauth.session: Failure: 
> Unable to establish connection to 
> http://opstack-cont-manage:5000/v3/auth/tokens. Retrying in 1.0s.
> Oct 14 14:05:09 opstack-controller keystoneauth.session: Failure: 
> Unable to establish connection to 
> http://opstack-cont-manage:5000/v3/auth/tokens. Retrying in 2.0s.
>
> Does this mean that problem lies on proxy server side?
>

Looks like the swift proxy - keystone connection is not happy. Have a 
look at what your keystone logs are saying.

Cheers

Mark