© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Looking at stein, the SchedulerReport
https:/
The _get_providers_
https:/
and that should reconstruct the client adapter if we hit EndpointNotFound:
https:/
Ah but we don't hit that, we get a response from placement and log that here:
https:/
Which is this:
2019-04-25 09:58:12.175 31793 ERROR nova.scheduler.
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
</p>
<hr>
<address>
</body></html>
But is placement returning that or keystoneauth1? If it were KSA, I'd think it should raise an exception rather than a 400 so we could handle it.
I'm not sure how we can easily detect that and recreate the client adapter object.
And since you're not using https:/
We could potentially just reset the client adapter upon a SIGHUP:
https:/
But SIGHUP is performing a full restart of the service (see bug 1715374), so that's not very helpful (plus having to SIGHUP all of your computes when the placement endpoint changes kind of sucks even if HUP worked properly).
One option is we could write a decorator for the get/post/put/delete methods:
https:/
That if the response is 400 with that text we'd reconstruct the client adapter and retry the request. I'm not sure if that's too heavy weight though.