Bad response code while validating token: 502
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Expired
|
Undecided
|
Unassigned |
Bug Description
Found this while investigating a gate failure [1].
Tempest logs say "2017-04-11 10:07:02,765 23082 INFO [tempest.
That 503 looks suspicious. So I go to the nova-api logs. Which gives
2017-04-11 10:07:02.762 32191 ERROR keystonemiddlew
2017-04-11 10:07:02.763 32191 WARNING keystonemiddlew
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request <em><a href="/
Reason: <strong>Error reading from remote server<
<hr>
<address>
</body></html>
2017-04-11 10:07:02.763 32191 CRITICAL keystonemiddlew
So Apache is complaining, some network connection issue, related to proxy-ing. So I open "logs/apache/
[Tue Apr 11 10:07:02.761420 2017] [proxy_http:error] [pid 7136:tid 140090189690624] (20014)Internal error (specific information not available): [client 198.72.
[Tue Apr 11 10:07:02.761454 2017] [proxy:error] [pid 7136:tid 140090189690624] [client 198.72.
Interesting. Google says that adding "proxy-
Anyway, a good elasticsearch query for this is
message:"Bad response code while validating token: 502"
8 hits, no worries.
Changed in tempest: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Just hit it in Newton: http:// logs.openstack. org/30/ 470330/ 1/check/ gate-tempest- dsvm-neutron- full-ubuntu- xenial/ 115af9e/ logs/screen- n-api.txt. gz?level= TRACE