[Fri Apr 28 12:46:47.763965 2017] [proxy_http:error] [pid 30068:tid 140271090042624] (20014)Internal error (specific information not available): [client 104.130.119.120:50002] [frontend 104.130.119.120:443] AH01102: error reading status line from remote server 104.130.119.120:80
[Fri Apr 28 12:46:47.764003 2017] [proxy:error] [pid 30068:tid 140271090042624] [client 104.130.119.120:50002] [frontend 104.130.119.120:443] AH00898: Error reading from remote server returned by /identity_admin/v3/auth/tokens
The request that triggered the failure doesn't seem to show up in keystone log.
I am seeing that still happening with keystone token fetch. It just hit this Ocata patch: https:/ /review. openstack. org/#/c/ 460909/
In http:// logs.openstack. org/09/ 460909/ 2/check/ gate-tempest- dsvm-neutron- linuxbridge- ubuntu- xenial/ 67904c9/ logs/apache/ tls-proxy_ error.txt. gz we see:
[Fri Apr 28 12:46:47.763965 2017] [proxy_http:error] [pid 30068:tid 140271090042624] (20014)Internal error (specific information not available): [client 104.130. 119.120: 50002] [frontend 104.130. 119.120: 443] AH01102: error reading status line from remote server 104.130.119.120:80 119.120: 50002] [frontend 104.130. 119.120: 443] AH00898: Error reading from remote server returned by /identity_ admin/v3/ auth/tokens
[Fri Apr 28 12:46:47.764003 2017] [proxy:error] [pid 30068:tid 140271090042624] [client 104.130.
The request that triggered the failure doesn't seem to show up in keystone log.